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

Re: [Xen-devel] TPR write optimization (even improves 2003 sp2)


  • To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Thu, 08 Jan 2009 09:08:27 +0000
  • Cc:
  • Delivery-date: Thu, 08 Jan 2009 01:12:36 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AclwbQESFc81qMn2SR2vAjv2yU5MgQABpemAAAyUQdEAAFfuQAAAdgGuAAA1Q7AAAPb/BAAAN9OgAADpQpkAA5LWcAAAj3LQABWGf/AAA+R78AAGzflAAAs5uXg=
  • Thread-topic: [Xen-devel] TPR write optimization (even improves 2003 sp2)

On 08/01/2009 03:53, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

> One (big?) hiccup... how do I make sure that I am accessing the vlapic
> structure for the correct CPU? My current idea of vlapic[current_cpu] is
> flawed because a thread switch could occur between getting the address
> of the vlapic structure for the current cpu and writing a value to the
> mapped register.
> 
> Is it possible to have per-cpu mapping?

No.

> Does disabling interrupts via cli cause a VMEXIT?

No.

 K.



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


 


Rackspace

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