All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Que <qwejohn@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen-devel@lists.xensource.com
Subject: Re: Interrupts in Xen: Dynamic-irq and Phys-irq
Date: Mon, 18 Jul 2005 08:52:15 -0400	[thread overview]
Message-ID: <ada605fb0507180552e152828@mail.gmail.com> (raw)
In-Reply-To: <e56d6228e705e67cce8e0976b9917d4b@cl.cam.ac.uk>

Hello, 

Thanks!
Your answer makes things more understandable.

Regards,
John 

On 7/18/05, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
> 
> On 18 Jul 2005, at 13:07, John Que wrote:
> 
> > The "Dynamic-irq" also appears in Dom0 (for example, when you run
> > "cat /proc/interrupts" and look at the  line containing "ctrl-if" or
> > "console").
> >
> > Besides it, In dom0 there is also "Phys-irq" ; for examples,after
> > running "cat /proc/interruupts" in line containing "eth0" or "ide0" or
> > "ide1".
> >
> > what is the difference between these 2 types of interrupts ?
> 
> Phys-irq's relate directly to hardware IRQ lines (e.g., eth0, your disc
> controller, etc). Dynamic-irq's are perhaps better described as
> 'virtual IRQs'. They have no direct relation to physical IRQ lines, but
> originate from things like timer events in Xen, or from the other half
> of a 'split' virtual block or network driver. We call them 'dynamic
> IRQs' because the IRQ numbers are dynamically allocated. :-)
> 
>   -- Keir
> 
>

      reply	other threads:[~2005-07-18 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-18 12:07 Interrupts in Xen: Dynamic-irq and Phys-irq John Que
2005-07-18 12:40 ` Keir Fraser
2005-07-18 12:52   ` John Que [this message]

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=ada605fb0507180552e152828@mail.gmail.com \
    --to=qwejohn@gmail.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --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.