public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Anthony PERARD" <anthony.perard@citrix.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Igor Druzhinin <igor.druzhinin@citrix.com>,
	<devel@edk2.groups.io>, <jordan.l.justen@intel.com>,
	<ard.biesheuvel@linaro.org>, <julien.grall@arm.com>,
	<xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v3 3/3] OvmfPkg/XenSupport: turn off address decoding before BAR sizing
Date: Tue, 30 Apr 2019 17:35:51 +0100	[thread overview]
Message-ID: <20190430163551.GA1264@perard.uk.xensource.com> (raw)
In-Reply-To: <b999513b-b843-e440-d1f2-c49589506a65@redhat.com>

On Fri, Apr 26, 2019 at 08:15:07PM +0200, Laszlo Ersek wrote:
> On 04/25/19 22:23, Igor Druzhinin wrote:
> > On Xen, hvmloader firmware leaves address decoding enabled for
> > enumerated PCI device before jumping into OVMF. OVMF seems to
> > expect it to be disabled and tries to size PCI BARs in several places
> > without disabling it which causes BAR64, for example, being
> > incorrectly placed by QEMU.
> > 
> > Fix it by disabling PCI address decoding explicitly before the
> > first attempt to size BARs on Xen.
> > 
> > Signed-off-by: Igor Druzhinin <igor.druzhinin@citrix.com>
> > ---
> > Changes in v3:
> > - dropped unused arguments and rename PcatPciRootBridgeDecoding function
> > - make mask application more clear as suggested
> > ---
> >  OvmfPkg/Library/PciHostBridgeLib/XenSupport.c | 21 +++++++++++++++++++++
> >  1 file changed, 21 insertions(+)
> > 
> > diff --git a/OvmfPkg/Library/PciHostBridgeLib/XenSupport.c b/OvmfPkg/Library/PciHostBridgeLib/XenSupport.c
> > index 76fca53..b41bd6b 100644
> > --- a/OvmfPkg/Library/PciHostBridgeLib/XenSupport.c
> > +++ b/OvmfPkg/Library/PciHostBridgeLib/XenSupport.c
> > @@ -49,6 +49,22 @@ PcatPciRootBridgeBarExisted (
> >    EnableInterrupts ();
> >  }
> >  
> > +#define PCI_COMMAND_DECODE ((UINT16)(EFI_PCI_COMMAND_IO_SPACE | \
> > +                                     EFI_PCI_COMMAND_MEMORY_SPACE))
> > +STATIC
> > +VOID
> > +PcatPciRootBridgeDecodingDisable (
> > +  IN  UINTN                          Address
> > +  )
> > +{
> > +  UINT16                             Value;
> > +
> > +  Value = PciRead16 (Address);
> > +  if (Value & PCI_COMMAND_DECODE) {
> > +    PciWrite16 (Address, Value & ~(UINT32)PCI_COMMAND_DECODE);
> > +  }
> > +}
> > +
> >  STATIC
> >  VOID
> >  PcatPciRootBridgeParseBars (
> > @@ -75,6 +91,11 @@ PcatPciRootBridgeParseBars (
> >    UINT64                            Limit;
> >    PCI_ROOT_BRIDGE_APERTURE          *MemAperture;
> >  
> > +  // Disable address decoding for every device before OVMF starts sizing it
> > +  PcatPciRootBridgeDecodingDisable (
> > +    PCI_LIB_ADDRESS (Bus, Device, Function, PCI_COMMAND_OFFSET)
> > +  );
> > +
> >    for (Offset = BarOffsetBase; Offset < BarOffsetEnd; Offset += sizeof (UINT32)) {
> >      PcatPciRootBridgeBarExisted (
> >        PCI_LIB_ADDRESS (Bus, Device, Function, Offset),
> > 
> 
> Acked-by: Laszlo Ersek <lersek@redhat.com>
> 
> Someone from the Xen community please ACK this too, and then we can push
> the series.

Acked-by: Anthony PERARD <anthony.perard@citrix.com>

Thanks,

-- 
Anthony PERARD

  reply	other threads:[~2019-04-30 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25 20:23 [PATCH 0/3] Xen PCI passthrough fixes Igor Druzhinin
2019-04-25 20:23 ` [PATCH v3 1/3] OvmfPkg/XenSupport: remove usage of prefetchable PCI host bridge aperture Igor Druzhinin
2019-04-25 20:23 ` [PATCH v3 2/3] OvmfPkg/XenSupport: use a correct PCI host bridge aperture for BAR64 Igor Druzhinin
2019-04-25 20:23 ` [PATCH v3 3/3] OvmfPkg/XenSupport: turn off address decoding before BAR sizing Igor Druzhinin
2019-04-26 18:15   ` Laszlo Ersek
2019-04-30 16:35     ` Anthony PERARD [this message]
2019-04-30 16:48       ` [edk2-devel] " Laszlo Ersek

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-list 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=20190430163551.GA1264@perard.uk.xensource.com \
    --to=devel@edk2.groups.io \
    /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