public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
	Venkatesh Pallipadi <venki@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] generic-ipi: fix deadlock in __smp_call_function_single
Date: Sat, 18 Sep 2010 17:18:47 +0200	[thread overview]
Message-ID: <1284823127.2275.604.camel@laptop> (raw)
In-Reply-To: <1284761553.2676.21.camel@sbsiddha-MOBL3.sc.intel.com>

On Fri, 2010-09-17 at 15:12 -0700, Suresh Siddha wrote:
> On Tue, 2010-09-14 at 04:19 -0700, Heiko Carstens wrote:
> > > 
> > > So what patches are we going to merge?
> > > 
> > > I share Heiko's opinion on that its somewhat surprising to have
> > > __smp_call_function_single() differ in this detail from
> > > smp_call_function_single() and think that merging his patch would be
> > > good in that respect. But Andrew seemed to have reservations.
> > > 
> > > We can also merge either my or Suresh's patch (which I think makes
> > > sense, but is kinda subtle) to avoid the needless self kick.
> 
> Peter, Can you please merge my patch instead of yours, as mine is more
> appropriate here. And also I would like Heiko's patch also to be merged
> as that brings smp_call_function_single() and
> __smp_call_function_single() to similar behavior.

Sure can do. Thanks!

  reply	other threads:[~2010-09-18 15:19 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 13:50 [PATCH] generic-ipi: fix deadlock in __smp_call_function_single Heiko Carstens
2010-09-10 11:06 ` Peter Zijlstra
2010-09-10 11:23   ` Jens Axboe
2010-09-10 11:47     ` Heiko Carstens
2010-09-10 15:47       ` [tip:core/urgent] generic-ipi: Fix " tip-bot for Heiko Carstens
2010-09-11  0:28   ` [PATCH] generic-ipi: fix " Andrew Morton
2010-09-11  9:20     ` Peter Zijlstra
2010-09-11 16:42       ` Venkatesh Pallipadi
2010-09-13  8:08         ` Heiko Carstens
2010-09-13 18:02         ` Suresh Siddha
2010-09-14  8:03           ` Peter Zijlstra
2010-09-14 11:19             ` Heiko Carstens
2010-09-17 22:12               ` Suresh Siddha
2010-09-18 15:18                 ` Peter Zijlstra [this message]
2010-09-21 14:13           ` [tip:sched/urgent] sched: Fix nohz balance kick tip-bot for Suresh Siddha
2010-09-26  8:42     ` [PATCH] generic-ipi: fix deadlock in __smp_call_function_single Ingo Molnar
2010-09-26 12:59       ` Heiko Carstens
2010-09-26 16:23         ` Ingo Molnar

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=1284823127.2275.604.camel@laptop \
    --to=peterz@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=venki@google.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