From: Andi Kleen <andi@firstfloor.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andi Kleen <ak@linux.intel.com>, 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 19:24:14 -0700 [thread overview]
Message-ID: <20170315022414.GC14380@two.firstfloor.org> (raw)
In-Reply-To: <20170314194720.GD26264@bhelgaas-glaptop.roam.corp.google.com>
> I agree that it should be fairly safe to do ECAM/MMCONFIG without
> locking. Can we handle the decision part by adding a "lockless" bit
> to struct pci_ops? Old ops don't mention that bit, so it will be
> initialized to zero and we'll do locking as today. ECAM/MMCONFIG ops
> can set it and we can skip the locking.
That's what my other patch already did.
-Andi
next prev parent reply other threads:[~2017-03-15 2:24 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
2017-03-14 19:47 ` Bjorn Helgaas
2017-03-15 2:24 ` Andi Kleen [this message]
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=20170315022414.GC14380@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=eranian@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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).