From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Dwayne Litzenberger" <dlitz@dlitz.net>
Subject: [PATCH 0/2] xen-paciback: Fixes for PCI passthrough of AMD GPU.
Date: Sun, 2 Dec 2018 18:47:31 +0100 [thread overview]
Message-ID: <cover.55c0e31b75e2fbdf4206cc39c2fd7581793ae7ae.1543772656.git-series.marmarek@invisiblethingslab.com> (raw)
I've got this patch series from Dwayne Litzenberger, as a fix for AMD GPU
passthrough. I don't have this hardware myself, so I can't test this, but he
claims it works. I'm not sure if allowing guest to enable/disable expansion ROM
is safe thing to do, but the comment in rom_write for me suggests it is but
wasn't considered necessary. Other than this uncertainty, the patches looks
good for me.
Originally posted here:
https://github.com/marmarek/qubes-linux-kernel/pulls/1
Cc: Dwayne Litzenberger <dlitz@dlitz.net>
Dwayne Litzenberger (2):
xen-pciback: Fix error return in bar_write() and rom_write()
xen-pciback: Allow enabling/disabling expansion ROM
drivers/xen/xen-pciback/conf_space_header.c | 34 ++++++++++++++--------
1 file changed, 23 insertions(+), 11 deletions(-)
base-commit: 2e6e902d185027f8e3cb8b7305238f7e35d6a436
--
git-series 0.9.1
next reply other threads:[~2018-12-02 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 17:47 Marek Marczykowski-Górecki [this message]
2018-12-02 17:47 ` [PATCH 1/2] xen-pciback: Fix error return in bar_write() and rom_write() Marek Marczykowski-Górecki
2018-12-03 10:55 ` [Xen-devel] " Jan Beulich
2018-12-03 12:35 ` Roger Pau Monné
2018-12-02 17:47 ` [PATCH 2/2] xen-pciback: Allow enabling/disabling expansion ROM Marek Marczykowski-Górecki
2018-12-03 11:01 ` [Xen-devel] " Jan Beulich
2018-12-03 14:47 ` Marek Marczykowski
2018-12-03 15:04 ` Jan Beulich
2018-12-03 12:53 ` Roger Pau Monné
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=cover.55c0e31b75e2fbdf4206cc39c2fd7581793ae7ae.1543772656.git-series.marmarek@invisiblethingslab.com \
--to=marmarek@invisiblethingslab.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dlitz@dlitz.net \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®