From: Alexander Duyck <alexander.duyck@gmail.com>
To: Or Gerlitz <or.gerlitz@gmail.com>
Cc: Alexander Duyck <alexander.h.duyck@intel.com>,
bhelgaas@google.com, yinghai@kernel.org, guz.fnst@cn.fujitsu.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] pci: Avoid reentrant calls to work_on_cpu
Date: Tue, 14 May 2013 18:58:03 -0700 [thread overview]
Message-ID: <5192EBAB.7030203@gmail.com> (raw)
In-Reply-To: <CAJZOPZL06sG__MdTzp6FF6BuB+Tv+CC_US35eHY0EDP6vQVzMw@mail.gmail.com>
On 05/14/2013 05:32 PM, Or Gerlitz wrote:
> On Tue, May 14, 2013 at 6:26 PM, Alexander Duyck
> <alexander.h.duyck@intel.com> wrote:
>>
>> This change is meant to fix a deadlock seen when pci_enable_sriov was
>> called from within a driver's probe routine. The issue was that
>> work_on_cpu calls flush_work which attempts to flush a work queue for a
>> cpu that we are currently working in. In order to avoid the reentrant
>> path we just skip the call to work_on_cpu in the case that the device
>> node matches our current node.
>>
>> Reported-by: Yinghai Lu <yinghai@kernel.org>
>> Signed-off-by: Alexander Duyck <alexander.h.duyck@intel.com>
>> ---
>>
>> This patch is meant to address the issue pointed out in an earlier patch
>> sent by Yinghai Lu titled:
>> [PATCH 6/7] PCI: Make sure VF's driver get attached after PF's
>>
>> drivers/pci/pci-driver.c | 14 +++++++++-----
>> 1 files changed, 9 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/pci/pci-driver.c b/drivers/pci/pci-driver.c
>> index 79277fb..caeb1c0 100644
>> --- a/drivers/pci/pci-driver.c
>> +++ b/drivers/pci/pci-driver.c
>> @@ -277,12 +277,16 @@ static int pci_call_probe(struct pci_driver *drv,
>> struct pci_dev *dev,
>> int error, node;
>> struct drv_dev_and_id ddi = { drv, dev, id };
>>
>> - /* Execute driver initialization on node where the device's
>> - bus is attached to. This way the driver likely allocates
>> - its local memory on the right node without any need to
>> - change it. */
>> + /*
>> + * Execute driver initialization on the node where the device's
>> + * bus is attached. This way the driver likely allocates
>> + * its local memory on the right node without any need to
>> + * change it. If the node is the current node just call
>> + * local_pci_probe and avoid the possibility of reentrant
>> + * calls to work_on_cpu.
>> + */
>> node = dev_to_node(&dev->dev);
>> - if (node >= 0) {
>> + if ((node >= 0) && (node != numa_node_id())) {
>> int cpu;
>>
>> get_online_cpus();
>
>
> Alex, FWIW a similar patch was posted by Michael during the last rc
> cycles of 3.9 see
> http://marc.info/?l=linux-netdev&m=136569426119644&w=2
Did his patch ever get applied anywhere? I don't see it in any of the
trees.
The advantage this approach has over the one in the similar patch is
that this covers a broader set of CPUs since anything on the same node
is local versus just the first CPU in a given NUMA node.
Thanks,
Alex
next prev parent reply other threads:[~2013-05-15 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 22:26 [PATCH] pci: Avoid reentrant calls to work_on_cpu Alexander Duyck
2013-05-15 0:32 ` Or Gerlitz
2013-05-15 1:58 ` Alexander Duyck [this message]
2013-05-15 2:50 ` Yinghai Lu
2013-06-12 17:58 ` Alexander Duyck
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=5192EBAB.7030203@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=bhelgaas@google.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=or.gerlitz@gmail.com \
--cc=yinghai@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).