[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] RE: [PATCH] Patch to make latest hg multi-domainback to work


  • To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Byrne, John (HP Labs)" <john.l.byrne@xxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Thu, 8 Sep 2005 17:45:20 -0700
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 09 Sep 2005 00:42:49 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcWvySFLppJ+ILkHRKOQH/MX6thvfgEH6v3wABtDOHAAAcMDgAAeqRQA
  • Thread-topic: [Xen-ia64-devel] RE: [PATCH] Patch to make latest hg multi-domainback to work

>       Could you elaborate more how your latest patch works 
> differently and fix the potential issue?
> 
> -               *pteval = vcpu->arch.dtlb_pte;
> +               if (vcpu->domain==dom0 && !in_tpa) *pteval = 
> trp->page_flags;
> +               else *pteval = vcpu->arch.dtlb_pte;
> +               printf("DTLB MATCH... NEW, DOM%s, %s\n", 
> vcpu->domain==dom0?
> +                       "0":"U", 
> in_tpa?"vcpu_tpa":"ia64_do_page_fault");
> 
>       The new limitation seems only for dom0, while dom0 has 
> exactly same guest physical address as machine address. Based 
> upon this assumption, trp->page_flags actually equals to 
> guest pte (vcpu->arch.dtlb_pte)? So I'm not sure about the 
> trick here behind.

Using more printfs, it appears that the problem is that
one of the "page flags" has PL2 and the other has PL0.

Dan

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.