From: Ian Campbell <ian.campbell@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Tommi Airikka <tommi@airikka.net>
Cc: 810379@bugs.debian.org, xen-devel@lists.xen.org
Subject: Re: [BUG] pci-passthrough generates "xen:events: Failed to obtain physical IRQ" for some devices
Date: Thu, 4 Feb 2016 09:37:02 +0000 [thread overview]
Message-ID: <1454578622.25207.132.camel@citrix.com> (raw)
In-Reply-To: <20160203202801.GA30532@char.us.oracle.com>
On Wed, 2016-02-03 at 15:28 -0500, Konrad Rzeszutek Wilk wrote:
> > > And I wonder if the XEN_DOMCTL_irq_permission aka,
> > > xc_domain_irq_permission
> > > had been called. I remember that at some point we missed it for
> > > Xend..
> > >
>
> False alarm.
>
> It was all in Linux. Attached are four patches (the first two
> are for your issue you discovered).
> I was wondering if there is a way for you to test them?
Tommy,
Please see the Debian Kernel Handbook and in particular
https://www.debian.org/doc/manuals/debian-kernel-handbook/ch-common-tasks.html#s-common-official
for instructions on rebuilding the Debian kernel with additional patches.
Ian.
next prev parent reply other threads:[~2016-02-04 9:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANQMFx4YULqKctKZqeESesTQjLQun7rQ0ZjGzq96TXTtUw6VWA@mail.gmail.com>
2016-01-27 18:30 ` [BUG] pci-passthrough generates "xen:events: Failed to obtain physical IRQ" for some devices Konrad Rzeszutek Wilk
2016-01-30 2:13 ` Marek Marczykowski-Górecki
2016-01-30 13:18 ` Tommi Airikka
2016-02-01 10:43 ` Ian Campbell
2016-02-01 14:50 ` Konrad Rzeszutek Wilk
2016-02-03 14:22 ` Marek Marczykowski-Górecki
2016-02-03 15:26 ` Konrad Rzeszutek Wilk
2016-02-08 17:39 ` Marek Marczykowski-Górecki
2016-02-09 4:59 ` Konrad Rzeszutek Wilk
2016-02-03 20:28 ` Konrad Rzeszutek Wilk
2016-02-04 9:37 ` Ian Campbell [this message]
2016-02-04 23:35 ` Tommi Airikka
2016-02-12 21:36 ` Konrad Rzeszutek Wilk
2016-02-12 21:53 ` Tommi Airikka
2016-01-23 16:12 Tommi Airikka
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=1454578622.25207.132.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=810379@bugs.debian.org \
--cc=konrad.wilk@oracle.com \
--cc=tommi@airikka.net \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).