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

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


  • To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Wed, 7 Jan 2009 21:05:55 +1100
  • Cc:
  • Delivery-date: Wed, 07 Jan 2009 02:06:44 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AclwbQESFc81qMn2SR2vAjv2yU5MgQABpemAAAyUQdEAAFfuQAAAdgGuAAA1Q7AAAPb/BAAAN9Og
  • Thread-topic: [Xen-devel] TPR write optimization (even improves 2003 sp2)

> > I am probably showing a lack of understanding about how the APIC
works
> > here, but from a very brief look at what writing to the TPR register
> > does, all I can see is that it sets a value in vlapic->regs->data.
Could
> > I just map a page from the DomU into xen and assign a byte in there
as
> > the TPR register (one byte per CPU). I would need a new hypercall to
> > turn this on but that's no big deal. Or is there more to a TPR write
> > than just setting vlapic->regs->data?
> 
> Sometimes it triggers an interrupt to be delivered. So you'd need a
TPR
> threshold too to cause a VMEXIT sometimes. Or perhaps map the whole
APIC
> page and work it out yourself (possibly the Citrix drivers do this,
but
> I'm not really familiar with them).

I can't see anything that would trigger an interrupt beyond
vlapic_write(). Is it just the act of invoking a VMEXIT that triggers
the interrupt delivery?

>From memory, there is a register somewhere that says what the highest
interrupt level that is currently blocked is... I'll look at that. This
doesn't actually sound that hard...

James

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