From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Gary R Hook <gary.hook@amd.com>
Cc: "Hook, Gary" <ghook@amd.com>,
linux-crypto@vger.kernel.org,
Tom Lendacky <thomas.lendacky@amd.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Can a driver->probe be called for two devices at the same time (WAS: Re: [PATCH] crypto/ccp: don't disable interrupts while setting up debugfs)
Date: Tue, 27 Feb 2018 18:33:14 +0100 [thread overview]
Message-ID: <20180227173314.uko5xpf4od2fn74g@linutronix.de> (raw)
In-Reply-To: <372b353d-017d-a72c-b750-9417f6265874@amd.com>
On 2018-02-27 11:08:56 [-0600], Gary R Hook wrote:
> That issue remains unclear to me: Are probes of PCI devices guaranteed to be
> serialized? Observations on my CCPs says that they occur in order, but I
> don't know for certain that serialization is guaranteed.
>
> Is there a definitive statement on this somewhere that I just don't know
> about?
So the question if a driver can probe two devices simultaneously. I'm
not sure. We have PROBE_PREFER_ASYNCHRONOUS which defers the probe to
worker. However I have no idea if two of those worker can run at the
same time.
> I think a mutex would be just fine; I got this wrong, clearly. Let me work
> up a patch using a mutex.
I've sent one. Why not just ack it and be done with it?
> Gary
Sebastian
next parent reply other threads:[~2018-02-27 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180223223307.18882-1-bigeasy@linutronix.de>
[not found] ` <3f0e1a62-a7ea-6d0c-d305-67080803aefd@amd.com>
[not found] ` <20180226083508.th2m3xssp36lx3zh@linutronix.de>
[not found] ` <372b353d-017d-a72c-b750-9417f6265874@amd.com>
2018-02-27 17:33 ` Sebastian Andrzej Siewior [this message]
2018-02-27 17:45 ` Can a driver->probe be called for two devices at the same time (WAS: Re: [PATCH] crypto/ccp: don't disable interrupts while setting up debugfs) Gary R Hook
2018-02-27 18:40 ` Greg Kroah-Hartman
2018-02-27 19:36 ` Sebastian Andrzej Siewior
2018-02-27 20:11 ` Gary R Hook
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=20180227173314.uko5xpf4od2fn74g@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=gary.hook@amd.com \
--cc=ghook@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.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