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

Re: [Xen-devel] Re: [PATCH] Handle MSI irq storm


  • To: "Shan, Haitao" <haitao.shan@xxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Thu, 03 Jul 2008 10:24:00 +0100
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 03 Jul 2008 02:24:27 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acjcy8F+D4qxw0AnTb6V8UsSMvI8BwAGIrDfAABHUbAAAdev+QAAb5xs
  • Thread-topic: [Xen-devel] Re: [PATCH] Handle MSI irq storm

On 3/7/08 10:11, "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx> wrote:

>  1. Push your INPROGRESS logic inside of hvm_do_IRQ_dpci() (you'll have to
> create new flag in place of using IRQ_INPROGRESS, obviously). Have
> hvm_do_IRQ_dpci() return one of three statuses: not handled, handled, and
> already pending. Don't bother clearing the flag in the hvm eoi function.
> It's not really a requirement for this scheme to work.

Errm, actually it *is* a requirement to clear the flag in the eoi function.
That's the whole point of how you'll detect spurious interrupts delivered to
HVM guests. Ignore my ridiculous last sentence above. :-)

 -- Keir



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