From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Tommi Airikka <tommi@airikka.net>,
Ian Campbell <ian.campbell@citrix.com>,
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: Mon, 8 Feb 2016 18:39:17 +0100 [thread overview]
Message-ID: <20160208173917.GD24446@mail-itl> (raw)
In-Reply-To: <20160203152657.GE20732@char.us.oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 1384 bytes --]
On Wed, Feb 03, 2016 at 10:26:58AM -0500, Konrad Rzeszutek Wilk wrote:
> On Wed, Feb 03, 2016 at 03:22:30PM +0100, Marek Marczykowski-Górecki wrote:
> > On Mon, Feb 01, 2016 at 09:50:53AM -0500, Konrad Rzeszutek Wilk wrote:
> > > > The second bullet looks at first pretty interesting from this PoV,
> > > > see http://xenbits.xen.org/xsa/advisory-157.html for info on the XSA and
> > > > the various patches. Konrad is on the CC already so hopefully he has some
> > > > ideas.
> > >
> > > Thanks. I will try to reproduce this with the upstream kernel first as
> > > those patches are there.
> >
> > According to one Qubes OS user report[1], the bug was introduced between
> > version, which differs only by XSA-155 patches (including one for
> > pciback), especially not XSA-157.
> > Maybe on some code path, some value is not copied back to pdev->sh_info->op?
>
> I found two bugs (attached the draft not-compiled patches). Upstream
> wise I seem to be tripping over another issue.
>
> There is also some more work required in there to fix the MSI-x enable op.
What exactly do you have in mind here? That four patches in your next
email? Or something not yet fixed?
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-08 17:39 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 [this message]
2016-02-09 4:59 ` Konrad Rzeszutek Wilk
2016-02-03 20:28 ` Konrad Rzeszutek Wilk
2016-02-04 9:37 ` Ian Campbell
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=20160208173917.GD24446@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=810379@bugs.debian.org \
--cc=ian.campbell@citrix.com \
--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).