xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Malcolm Crossley <malcolm.crossley@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH] hw/passthrough: Prevent QEMU from mapping PCI option ROM at address 0
Date: Mon, 12 May 2014 16:48:06 +0100	[thread overview]
Message-ID: <5370ED36.30605@citrix.com> (raw)
In-Reply-To: <21360.58962.995659.57570@mariner.uk.xensource.com>

On 12/05/14 16:18, Ian Jackson wrote:
> Malcolm Crossley writes ("[PATCH] hw/passthrough: Prevent QEMU from mapping PCI option ROM at address 0"):
>> The PCI option ROM BAR uses the LSB to indicate if the BAR is enabled.
>> The AMD graphics driver sets the address bit's of the BAR to 0 but leaves the
>> LSB set to 1. Whilst this is not good practice, QEMU should be ignoring the
>> non address parts of the BAR.
>>
>> This patch adds masking of the non address parts of the BAR before comparing
>> the address to 0.
> 
> Is this just for qemu-xen-traditional ?  Is there a corresponding
> patch to qemu-upstream ?
> 
It is just for qemu-xen-traditional, I've just submitted a v4 patch
which expands the masking of the bottom bits up to 4k.

MMIO regions are handled differently in qemu-upstream and so a
corresponding patch is not required.

Malcolm

> Ian.
> 

  reply	other threads:[~2014-05-12 15:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12 12:42 [PATCH] hw/passthrough: Prevent QEMU from mapping PCI option ROM at address 0 Malcolm Crossley
2014-05-12 13:09 ` Jan Beulich
2014-05-12 13:26   ` Malcolm Crossley
2014-05-12 13:34     ` Jan Beulich
2014-05-12 13:55       ` Malcolm Crossley
2014-05-12 14:00         ` Jan Beulich
2014-05-12 13:17 ` Ian Campbell
2014-05-12 13:31   ` Malcolm Crossley
2014-05-12 13:36     ` Ian Campbell
2014-05-12 13:52 ` Paul Durrant
2014-05-12 15:18 ` Ian Jackson
2014-05-12 15:48   ` Malcolm Crossley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-12 14:31 Malcolm Crossley

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=5370ED36.30605@citrix.com \
    --to=malcolm.crossley@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --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).