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

RE: [Xen-ia64-devel] [PATCH] per vcpu vhpt


  • To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Tue, 10 Oct 2006 09:31:26 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 09 Oct 2006 18:32:07 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcbrlIDCd1HAh1SsR7+vz3LYFH9DAwAdujog
  • Thread-topic: [Xen-ia64-devel] [PATCH] per vcpu vhpt

>> >non-current vcpu's case must be handled.
>> I don't see any issue here, if we use option1, we use identity
mapping
>> for VHPT, and so we can use 16 MB TR mapping, of cause, 64KB VHPT is
>> covered by this 16M TR.
>
>In fact I had such a patch for the very early version of
>the pervcpu vhpt patch.
>But I discarded it for some reason. I don't remember clearly why.
>Probably I wanted to avoid introducing an implicit dependency
>and increasing vcpu context switch overhead.

As I know, IA64/LINUX is using this mechanism, the task_struct is 32k,
but it uses 16M TR mapping if it is not covered 64M kernel TR.

Anthony


>
>--
>yamahata

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