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

RE: [Xen-ia64-devel] RE: [PATCH] Patch to make latesthgmulti-domainback to work


  • To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Fri, 9 Sep 2005 12:35:24 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 09 Sep 2005 04:33:13 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcWvySFLppJ+ILkHRKOQH/MX6thvfgEH6v3wABtDOHAAAcMDgAAeqRQAAAEH+PAAAsa6oAABwX8AAACYQYAAABkFEAAALEbAAAGaVrA=
  • Thread-topic: [Xen-ia64-devel] RE: [PATCH] Patch to make latesthgmulti-domainback to work

>From: Magenheimer, Dan (HP Labs Fort Collins)
[mailto:dan.magenheimer@xxxxxx]
>
>> >>The problem (PL2 vs PL0) still occurs even with
>> >>that code turned off.
>> >
>> >When you disable FAST_PTC_GA, it then goes to vcpu_ptc_ga which
still
>> >only handle vcpu->arch.dtlb, without touching vcpu->arch.dtlb_pte.
In
>> >this case, once match_dtlb begins to return guest pte in my patch,
it
>> >may contain stale value since dtlb_pte is not handled in
vcpu_ptc_ga.
>> >
>>
>> So what I really mean here is that you should purge dtlb_pte/itlb_pte
>> (guest pte entry) in vcpu_ptc_ga and hyper_ptc_ga.
>
>I'm not sure I understand.  arch.dtlb_pte is just some data associated
>with arch.dtlb.  It gets set whenever arch.dtlb gets set and it
>only gets used if arch.dtlb matches and is valid.  IIRC, its only
>use is to save away the metaphysical address so vcpu_tpa (and IIRC,
>indirectly, vcpu_fc?) is guaranteed to be able to find it. So what
>do you mean by "purge dtlb_pte"?

OK, I see it now.

Thanks,
Kevin

_______________________________________________
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®.