All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel@lists.xensource.com
Subject: RE: Dynamic-irq's in HVM domains
Date: Fri, 30 Nov 2007 09:33:44 +0000	[thread overview]
Message-ID: <1196415224.21533.24.camel@localhost.localdomain> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D0131A2DF@trantor>


I can't help with the Windows side I'm afraid, perhaps there is a
windows dev newsgroup or something that might be useful?

On Fri, 2007-11-30 at 20:02 +1100, James Harper wrote:
> I made the assumption that 'Dynamic-irq' is the same as virq... if
> not, what is a virq? It appears to be something that the hypervisor is
> aware of as there is a hypercall to bind to one.

They are IRQ sources from the hypervisor (as opposed to from a virtual
or physical device or another domain). From xen/include/public/xen.h:
        #define VIRQ_TIMER      0  /* V. Timebase update, and/or requested timeout.  */
        #define VIRQ_DEBUG      1  /* V. Request guest to dump debug info.           */
        #define VIRQ_CONSOLE    2  /* G. (DOM0) Bytes received on emergency console. */
        #define VIRQ_DOM_EXC    3  /* G. (DOM0) Exceptional event for some domain.   */
        #define VIRQ_TBUF       4  /* G. (DOM0) Trace buffer has records available.  */
        #define VIRQ_DEBUGGER   6  /* G. (DOM0) A domain has paused for debugging.   */
        #define VIRQ_XENOPROF   7  /* V. XenOprofile interrupt: new sample available */
        #define VIRQ_CON_RING   8  /* G. (DOM0) Bytes received on console            */
plus a handful of VIRQ_ARCH<n>

They are used by binding them to an event channel using
EVTCHNOP_bind_virq, as you've probably noticed.

Ian.

  parent reply	other threads:[~2007-11-30  9:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-24 11:05 Dynamic-irq's in HVM domains James Harper
2007-11-30  2:29 ` James Harper
2007-11-30  8:19   ` Ian Campbell
2007-11-30  9:02     ` James Harper
2007-11-30  9:10       ` Pasi Kärkkäinen
2007-11-30  9:13         ` James Harper
2007-11-30  9:15           ` Pasi Kärkkäinen
2007-11-30  9:33       ` Ian Campbell [this message]
2007-11-30  9:37         ` James Harper
2007-11-30 18:57           ` Mark Williamson
2007-11-30 22:00             ` James Harper

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1196415224.21533.24.camel@localhost.localdomain \
    --to=ian.campbell@citrix.com \
    --cc=james.harper@bendigoit.com.au \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.