From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Dwayne Litzenberger <dlitz@dlitz.net>,
<xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH 2/2] xen-pciback: Allow enabling/disabling expansion ROM
Date: Mon, 3 Dec 2018 13:53:46 +0100 [thread overview]
Message-ID: <20181203125346.qjxhuepu3nhnc7wp@mac> (raw)
In-Reply-To: <a05e3cf451d692dc4b1c81c8b5d66fc75d1fa325.1543772656.git-series.marmarek@invisiblethingslab.com>
On Sun, Dec 02, 2018 at 06:47:33PM +0100, Marek Marczykowski-Górecki wrote:
> From: Dwayne Litzenberger <dlitz@dlitz.net>
>
> Newer AMD GPUs store their initialization routines as bytecode on the
> ROM. This fixes the following initialization error inside the VM when
> doing PCI passthrough:
>
> radeon 0000:00:05.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
> radeon 0000:00:05.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
> [drm:radeon_get_bios [radeon]] *ERROR* Unable to locate a BIOS ROM
> radeon 0000:00:05.0: Fatal error during GPU init
>
> Signed-off-by: Dwayne Litzenberger <dlitz@dlitz.net>
> ---
> drivers/xen/xen-pciback/conf_space_header.c | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/xen/xen-pciback/conf_space_header.c b/drivers/xen/xen-pciback/conf_space_header.c
> index 697d0a8..bc145d3 100644
> --- a/drivers/xen/xen-pciback/conf_space_header.c
> +++ b/drivers/xen/xen-pciback/conf_space_header.c
> @@ -150,21 +150,21 @@ static int rom_write(struct pci_dev *dev, int offset, u32 value, void *data)
> if ((value | ~PCI_ROM_ADDRESS_MASK) == ~0U)
> bar->which = 1;
> else {
> - u32 tmpval;
> - err = pci_read_config_dword(dev, offset, &tmpval);
> + u32 newval = bar->val;
Naming this newval is quite confusing IMO, since at this point it's
actually the old value.
> +
> + /* Allow enabling/disabling rom, if present */
> + if (newval & PCI_ROM_ADDRESS_MASK) {
> + newval &= ~PCI_ROM_ADDRESS_ENABLE;
> + newval |= value & PCI_ROM_ADDRESS_ENABLE;
> + }
> + err = pci_write_config_dword(dev, offset, newval);
> if (err)
> goto out;
> - if (tmpval != bar->val && value == bar->val) {
> - /* Allow restoration of bar value. */
> - err = pci_write_config_dword(dev, offset, bar->val);
> - if (err)
> - goto out;
> - }
> + bar->val = newval;
I'm not sure there's much value in storing this, the only difference
is the setting of the enable bit, which is ignored anyway.
Thanks, Roger.
prev parent reply other threads:[~2018-12-03 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 17:47 [PATCH 0/2] xen-paciback: Fixes for PCI passthrough of AMD GPU Marek Marczykowski-Górecki
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é [this message]
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=20181203125346.qjxhuepu3nhnc7wp@mac \
--to=roger.pau@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dlitz@dlitz.net \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--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