From: "Derrick, Jonathan" <jonathan.derrick@intel.com>
To: "lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>
Cc: "Kalakota, SushmaX" <sushmax.kalakota@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"helgaas@kernel.org" <helgaas@kernel.org>
Subject: Re: [PATCH] PCI: vmd: Filter resource type bits from shadow register
Date: Mon, 13 Apr 2020 16:55:19 +0000 [thread overview]
Message-ID: <9f2e64822b8d9578133be73f47d3ae6091335c58.camel@intel.com> (raw)
In-Reply-To: <1f3bc6cb57988f052cb94c325fb0af84bd76b980.camel@intel.com>
Sorry I just noticed this never hit the ML.
I'm guessing it was rejected at the mailserver due to the bad stable address.
I'll resubmit for 5.8 in a while.
On Wed, 2020-04-08 at 11:36 -0600, Jonathan Derrick wrote:
> Anything wrong with this, Lorenzo?
>
> Thanks
>
> On Fri, 2020-03-20 at 12:58 -0600, Jon Derrick wrote:
> > Versions of VMD with the Host Physical Address shadow register use this
> > register to calculate the bus address offset needed to do guest
> > passthrough of the domain. This register shadows the Host Physical
> > Address registers directly, including the resource type bits. After
> > calculating the offset, the extra bits lead to the VMD resources being
> > over-provisioned at the front and under-provisioned at the back.
> >
> > Example:
> > pci 10000:80:02.0: reg 0x10: [mem 0xf801fffc-0xf803fffb 64bit]
> >
> > Expected:
> > pci 10000:80:02.0: reg 0x10: [mem 0xf8020000-0xf803ffff 64bit]
> >
> > If other devices are mapped in the over-provisioned front, it could lead
> > to resource conflict issues with VMD or those devices.
> >
> > Fixes: a1a30170138c9 ("PCI: vmd: Fix shadow offsets to reflect spec changes")
> > Cc: stable@vger.kernel.org # v4.19+
> > Signed-off-by: Jon Derrick <jonathan.derrick@intel.com>
> > ---
> > drivers/pci/controller/vmd.c | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/pci/controller/vmd.c b/drivers/pci/controller/vmd.c
> > index dac91d6..e386d4e 100644
> > --- a/drivers/pci/controller/vmd.c
> > +++ b/drivers/pci/controller/vmd.c
> > @@ -445,9 +445,11 @@ static int vmd_enable_domain(struct vmd_dev *vmd, unsigned long features)
> > if (!membar2)
> > return -ENOMEM;
> > offset[0] = vmd->dev->resource[VMD_MEMBAR1].start -
> > - readq(membar2 + MB2_SHADOW_OFFSET);
> > + (readq(membar2 + MB2_SHADOW_OFFSET) &
> > + PCI_BASE_ADDRESS_MEM_MASK);
> > offset[1] = vmd->dev->resource[VMD_MEMBAR2].start -
> > - readq(membar2 + MB2_SHADOW_OFFSET + 8);
> > + (readq(membar2 + MB2_SHADOW_OFFSET + 8) &
> > + PCI_BASE_ADDRESS_MEM_MASK);
> > pci_iounmap(vmd->dev, membar2);
> > }
> > }
prev parent reply other threads:[~2020-04-13 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1584730690-57253-1-git-send-email-jonathan.derrick@intel.com>
2020-04-08 17:36 ` [PATCH] PCI: vmd: Filter resource type bits from shadow register Derrick, Jonathan
2020-04-13 16:55 ` Derrick, Jonathan [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=9f2e64822b8d9578133be73f47d3ae6091335c58.camel@intel.com \
--to=jonathan.derrick@intel.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=sushmax.kalakota@intel.com \
/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).