From: "Raj, Ashok" <ashok.raj@intel.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Andrew Murray <andrew.murray@arm.com>,
Steffen Liebergeld <steffen.liebergeld@kernkonzept.com>,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Ashok Raj <ashok.raj@intel.com>
Subject: Re: [PATCH] PCI: quirks: Fix register location for UPDCR
Date: Wed, 18 Sep 2019 15:07:43 -0700 [thread overview]
Message-ID: <20190918220743.GA26982@otc-nc-03> (raw)
In-Reply-To: <20190918160454.45857065@x1.home>
Hi Alex
On Wed, Sep 18, 2019 at 04:04:54PM -0600, Alex Williamson wrote:
> > > > >>
> > > > >> Signed-off-by: Steffen Liebergeld <steffen.liebergeld@kernkonzept.com>
> > > > >
> > > > > You may also like to add:
> > > > >
> > > > > Fixes: d99321b63b1f ("PCI: Enable quirks for PCIe ACS on Intel PCH root ports")
> > > > > Reviewed-by: Andrew Murray <andrew.murray@arm.com>
> > > > >
> > > > > As well as CC'ing stable.
> > > >
> > > > Ok. Thank you.
> > > >
> > > > > I guess the side effect of this bug is that we claim to have peer
> > > > > isolation when we do not. This fix ensures that we get the advertised
> > > > > isolation.
> > > > Yes, that is also my understanding. Should I explain that in the commit
> > > > message?
> > >
> > > I think something similar to that would be helpful.
> >
> > This is unfortunate, but my initial impression is that this may have
> > just been a typo that slipped by everyone. It's difficult to actually
> > test for isolation. Maybe someone from Intel could review this. Also,
> > Steffen discussed this with me prior to posting and I believe this is
> > untested, so while trivial from inspection, it would be preferable to
> > know that some sample of hardware doesn't fall over as a result.
>
> I've looked at 4 different systems, two 6-series (desktop + laptop), an
> 8-series desktop, and an X79 workstation. None of the 6/8 series even
> enter the branch where we read the UPDCR register, the value read from
> the BSPR register doesn't require it. In the case of the X79, using
> 0x1014 for UPDCR, the value read from the register is zero so code
> would not proceed into the inner branch to write the register, but
> using the current 0x1114 address, we read a non-zero value and changing
> it does stick on re-read. Neither address is defined in the public
> specs for this chipset, we're basing the information on word of mouth
> and ack from Intel as noted in commit 1a30fd0dba77.
>
> So of these systems, if 0x1014 is the correct UPDCR register address,
> nothing actually changes with respect to isolation other than we're not
> changing the value in mystery register 0x1114. Intel? Thanks,
I have asked the chipset folks if the spec has a typo.. waiting for
an answer..
prev parent reply other threads:[~2019-09-18 22:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 18:07 [PATCH] PCI: quirks: Fix register location for UPDCR Steffen Liebergeld
2019-09-18 10:42 ` Andrew Murray
2019-09-18 12:02 ` Steffen Liebergeld
2019-09-18 12:09 ` Andrew Murray
2019-09-18 16:46 ` Alex Williamson
2019-09-18 22:04 ` Alex Williamson
2019-09-18 22:07 ` Raj, Ashok [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=20190918220743.GA26982@otc-nc-03 \
--to=ashok.raj@intel.com \
--cc=alex.williamson@redhat.com \
--cc=andrew.murray@arm.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=steffen.liebergeld@kernkonzept.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