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

[Xen-devel] query on interrupts in Xen

  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "pradeep singh rautela" <rautelap@xxxxxxxxx>
  • Date: Mon, 19 Mar 2007 19:01:42 +0530
  • Delivery-date: Mon, 19 Mar 2007 06:30:40 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=b5+jffM6PnQTSb/pG8yurgb4eh172fQWu8NjDaTBORLw2BNx5LqLhH4zox3amBuPIKi1hkF5Mq9f7W9/+1y4CC3miSt7vEQy9BR4u2v0dxvs8fmC3xAJFJyqeURoQWvCzg+wauOzQ9uON/m9XBtdXKAPGMInCzJOFvA2sl/Fsos=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi All,

IRQ line status in include/xen/irq.h  has a #define macro as -
#define IRQ_LEVEL   64  /*IRQ level triggered*/

I hope this means the irq line is shared ?

struct hw_interrupt_type {...} is the descriptor which represents the actual physical hardware interrupt, am i right?

Another question what is difference between VIRQS and struct dynirq_type{...}?
As i make out of them, virqs are virtual interrupts when we talk from within the domUs while dynirq_type represents the virtual interrupts in context of the Xen dom0 which are responsible for mapping actual physical irqs available to the domains (domUs).

Is my understanding correct or am i missing something here?

Help along with any pointers in the code will be appreciated.

Thank you

pradeep singh rautela
"proud to be a TUXedo, BSDemons you are a little late" - me
Xen-devel mailing list



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