From: Thomas Gleixner <tglx@linutronix.de>
To: Andi Kleen <ak@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
bhelgaas@google.com, x86@kernel.org, linux-pci@vger.kernel.org,
eranian@google.com, Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] x86, pci: Add interface to force mmconfig
Date: Tue, 14 Mar 2017 18:56:26 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1703141849170.3619@nanos> (raw)
In-Reply-To: <20170314170255.GH32070@tassilo.jf.intel.com>
On Tue, 14 Mar 2017, Andi Kleen wrote:
> The other option is to simply make it unconditional. That would
> be even simpler, but it is a bit more risky. Hmm, I suppose may
> be worth trying to find out what Windows uses. If they get away
> with MMCONFIG everywhere we should be too.
>From the PCIe spec:
The PCI 3.0 compatible Configuration Space can be accessed using either
the mechanism defined in the PCI Local Bus Specification or the PCI
Express Enhanced Configuration Access Mechanism (ECAM) described later in
this section. Accesses made using either access mechanism are
equivalent. The PCI Express Extended Configuration Space can only be
accessed by using the ECAM.
The 1.0 spec has a similar wording (s/3.0/2.3).
Definitely the best way to go.
Thanks,
tglx
next prev parent reply other threads:[~2017-03-14 17:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 23:21 [PATCH 1/4] pci: Allow lockless access path to PCI mmconfig Andi Kleen
2017-03-02 23:21 ` [PATCH 2/4] pci: Add generic pci_bus_force_mmconfig interface Andi Kleen
2017-03-14 17:34 ` H. Peter Anvin
2017-03-02 23:21 ` [PATCH 3/4] x86, pci: Add interface to force mmconfig Andi Kleen
2017-03-14 13:55 ` Thomas Gleixner
2017-03-14 15:41 ` Andi Kleen
2017-03-14 16:40 ` Thomas Gleixner
2017-03-14 17:02 ` Andi Kleen
2017-03-14 17:56 ` Thomas Gleixner [this message]
2017-03-14 19:47 ` Bjorn Helgaas
2017-03-15 2:24 ` Andi Kleen
2017-03-15 2:55 ` Bjorn Helgaas
2017-03-15 10:00 ` Thomas Gleixner
2017-03-15 14:09 ` Bjorn Helgaas
2017-03-16 0:02 ` Andi Kleen
2017-03-16 22:45 ` Thomas Gleixner
2017-03-02 23:21 ` [PATCH 4/4] perf/x86/intel/uncore: Enable forced mmconfig for Intel uncore Andi Kleen
2017-03-14 13:06 ` [PATCH 1/4] pci: Allow lockless access path to PCI mmconfig Thomas Gleixner
2017-03-14 17:28 ` H. Peter Anvin
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=alpine.DEB.2.20.1703141849170.3619@nanos \
--to=tglx@linutronix.de \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=bhelgaas@google.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.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).