All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "Kay, Allen M" <allen.m.kay@intel.com>,
	"'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
	"Han, Weidong" <weidong.han@intel.com>,
	"'keir.fraser@eu.citrix.com'" <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH][RFC] pv-ops: fix shared irq device	passthrough
Date: Tue, 10 Nov 2009 10:44:59 -0800	[thread overview]
Message-ID: <4AF9B4AB.9060302@goop.org> (raw)
In-Reply-To: <20091110163058.GB23000@phenom.dumpdata.com>

On 11/10/09 08:30, Konrad Rzeszutek Wilk wrote:
> With this patch you can share the PCI devices on the same IRQ, correct? Will
> this mean that you can assign to a guest a USB controller, while
> Dom0 has controller of the PCI NIC (and assuming that both of those
> share the same interrupt line)? If so, won't the Dom0 start throwing
> a fit b/c there are unhandled IRQs and eventually disable the IRQ line?
>
>
> Or even the guest decide that there are too many IRQs and decided to
> disable the IRQ line?
>   

It would be easy to add a dummy handler which always returns IRQ_HANDLED
for every cross-domain shared interrupt to prevent this.  Of course that
would paper over any real spurious/screaming interrupt problem, but we
could add some extra logic into the dummy handler if necessary.

I merged the patch, and had to add the new parameter to
xen_allocate_pirq() in arch/x86/pci/xen.c.  I just made it 0 which
should have no functional difference from before, but I'll leave it to
you to decide what it really should be.

    J

  parent reply	other threads:[~2009-11-10 18:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23 11:39 [PATCH][RFC] pv-ops: fix shared irq device passthrough Han, Weidong
2009-10-26 20:27 ` Jeremy Fitzhardinge
2009-10-27  1:32   ` Han, Weidong
2009-10-29 22:56     ` Jeremy Fitzhardinge
2009-10-30  9:29       ` Han, Weidong
2009-10-30 21:34         ` Jeremy Fitzhardinge
2009-10-31 13:50           ` Han, Weidong
     [not found]           ` <715D42877B251141A38726ABF5CABF2C055064A406@pdsmsx503.ccr.corp.intel.com>
2009-11-02 10:12             ` Han, Weidong
2009-11-10  6:12               ` Han, Weidong
2009-11-10  6:30                 ` Mr. Teo En Ming (Zhang Enming)
2009-11-10  6:59                   ` Han, Weidong
2009-11-10 16:30                 ` Konrad Rzeszutek Wilk
2009-11-10 17:11                   ` Kay, Allen M
2009-11-10 18:40                     ` Konrad Rzeszutek Wilk
2009-11-10 18:44                   ` Jeremy Fitzhardinge [this message]
2009-11-12  7:15                     ` Han, Weidong
2009-11-10 17:56                 ` Jeremy Fitzhardinge

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=4AF9B4AB.9060302@goop.org \
    --to=jeremy@goop.org \
    --cc=allen.m.kay@intel.com \
    --cc=keir.fraser@eu.citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=weidong.han@intel.com \
    --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.