From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCHv2 for-3.9] pci: avoid work_on_cpu for nested SRIOV probes Date: Sat, 20 Apr 2013 22:05:04 +0300 Message-ID: <20130420190504.GB853@redhat.com> References: <51360D7C.3060209@mellanox.com> <20130418200855.GA24086@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Bjorn Helgaas , Or Gerlitz , Ming Lei , Greg Kroah-Hartman , David Miller , Roland Dreier , netdev , Yan Burman , Jack Morgenstein , "linux-pci@vger.kernel.org" To: Tejun Heo Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-pci-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, Apr 18, 2013 at 08:04:47PM -0700, Tejun Heo wrote: > So, the thing is there is no actual deadlock. If you're okay with releasing w/ > spurious lockdep warning, leaving things alone should be fine. An issue with > mst's patch is that it actually changes the behavior to avoid a spurious > warning. Yes but in fact, isn't it cleaner to avoid work_on if we are going to run on the local CPU, anyway? > An alternative course would be leaving it alone now and remove the > spurious warning during the coming devel cycle and mark it w/ -stable. > > Thanks. Okay. Could you send tested a version of work_on_nested? > -- > tejun