From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Steven Haigh <netwiz@crc.id.au>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: xsa46-4.2.patch breaks PCI passthrough?
Date: Wed, 1 May 2013 12:09:03 +0100 [thread overview]
Message-ID: <5180F7CF.1050609@citrix.com> (raw)
In-Reply-To: <5180A825.4050108@crc.id.au>
On 01/05/13 06:29, Steven Haigh wrote:
> Hi all,
>
> I've had a report lodged against my packages that the patch provided for
> XSA46 against Xen 4.2.1 causes PCI passthru to break.
>
> It seems that 4.2.1 *without* the XSA46 patch works perfectly. 4.2.2
> does not work.
>
> I added this patch in xen-4.2.1-6 of my RPMs (http://xen.crc.id.au) and
> the reporter has built the same SRPM with xsa46 patch removed and PCI
> passthrough works as intended.
>
> Reapplying the XSA46 patch causes it to break again.
>
> The bug report and logs can be found here:
> http://xen.crc.id.au/bugs/view.php?id=5
>
> Has anyone come across this?
>
XSA-46 was to do with PCI passthrough of PV domains, and in particular
changing some of the rules regarding interrupts.
One thing which is not clear from the bug report so far is what exactly
is failing with an EINVAL. The implication is that it is the toolstack
which is bailing before the VM is created.
I will take a closer look at the two log files.
~Andrew
next prev parent reply other threads:[~2013-05-01 11:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 5:29 xsa46-4.2.patch breaks PCI passthrough? Steven Haigh
2013-05-01 11:09 ` Andrew Cooper [this message]
2013-05-01 11:28 ` Andrew Cooper
2013-05-02 8:49 ` Jan Beulich
2013-05-02 10:43 ` Ian Campbell
2013-05-02 11:54 ` Jan Beulich
2013-05-01 15:18 ` George Dunlap
2013-05-01 15:26 ` Steven Haigh
2013-05-01 16:07 ` Andrew Cooper
2013-05-03 22:15 ` Steven Haigh
2013-05-04 17:23 ` Andrew Cooper
2013-05-05 10:53 ` Steven Haigh
2013-05-06 7:15 ` Jan Beulich
2013-05-08 10:18 ` Steven Haigh
2013-05-08 11:45 ` Jan Beulich
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=5180F7CF.1050609@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=netwiz@crc.id.au \
--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 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.