All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net,
	Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	ian.pratt@cl.cam.ac.uk
Subject: Re: Interrupt forwarding
Date: Sun, 13 Mar 2005 11:49:23 -0500	[thread overview]
Message-ID: <9e473391050313084920740f5c@mail.gmail.com> (raw)
In-Reply-To: <5d91cd530ace01c1b50c26454b435ab1@cl.cam.ac.uk>

On Sun, 13 Mar 2005 16:01:19 +0000, Keir Fraser
<Keir.Fraser@cl.cam.ac.uk> wrote:
> But Xen does support shared IRQs. They're not as good as a separate IRQ
> per device from an isolation pov, but would you really expect
> otherwise?

Does Xen require the IRQ handler to run in the supervisor or domain?
If it is in the domain and the domain dies, what do you do about the
interrupt that keeps interrupting because there is no more code to
acknowledge it? If you shut it off at the PIC you shut off all devices
on that interrupt.

A proposal was recently made on lkml that request_irq would also pass
in a structure that would enable the kernel to acknowledge the IRQ
without the handler being there. Xen could pass info like that from
the domain back to the supervisor. Then in the domain dies the
supervisor has the info needed to shut off the specific interrupt.

On Fri, 11 Mar 2005 19:14:13 +0000, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> I posted a proposal for this sometime ago because X has some uses for
> it. The idea being you'd pass a struct that describes
>
> 1.      What tells you an IRQ occurred on this device
> 2.      How to clear it
> 3.      How to enable/disable it.
>
> Something like
>
>         struct {
>                 u8 type;                /* 8, 16, 32  I/O or MMIO */
>                 u8 bar;                 /* PCI bar to use */
>                 u32 offset;             /* Into bar */
>                 u32 mask;               /* Bits to touch/compare */
>                 u32 value;              /* Value to check against/set */
>         }
>

It might useful to add this to the main kernel API, and then over time
modify all of the drivers to use it. If a driver does this it would be
safe to transparently move it to user space like in UML or xen.  I've
been told that PCI Express and MSI does not have this problem.



> 
>   -- Keir
> 
> 


-- 
Jon Smirl
jonsmirl@gmail.com


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-13 16:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-12 19:59 Interrupt forwarding Ian Pratt
2005-03-12 20:07 ` Jon Smirl
2005-03-13 10:01   ` Keir Fraser
2005-03-13 15:56     ` Jon Smirl
2005-03-13 16:01       ` Keir Fraser
2005-03-13 16:49         ` Jon Smirl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-12 18:11 Ian Pratt
2005-03-12 18:21 ` Keir Fraser
2005-03-12 18:33   ` Jon Smirl
2005-03-12 18:48     ` Keir Fraser
2005-03-12 18:53       ` Jon Smirl
2005-03-12 18:59       ` Jon Smirl
2005-03-12 18:02 Jon Smirl
2005-03-12 18:12 ` Mark Williamson
2005-03-14 15:39   ` Ronald G. Minnich
2005-03-14 15:44     ` Mark Williamson
2005-03-14 16:01       ` Ronald G. Minnich
2005-03-14 16:04         ` Ronald G. Minnich
2005-03-14 21:59       ` Andi Kleen

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=9e473391050313084920740f5c@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=ian.pratt@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.sourceforge.net \
    /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.