public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Tejun Heo <tj@kernel.org>, Rusty Russell <rusty@rustcorp.com.au>,
	Christoph Lameter <cl@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: linux-next: manual merge of the percpu tree with the tip tree
Date: Thu, 9 Oct 2014 15:13:31 +0200	[thread overview]
Message-ID: <20141009131328.GB25790@lerouge> (raw)
In-Reply-To: <20141009155018.0b8f26f6@canb.auug.org.au>

On Thu, Oct 09, 2014 at 03:50:18PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the percpu tree got a conflict in
> kernel/irq_work.c between commit 76a33061b932 ("irq_work: Force raised
> irq work to run on irq work interrupt") from the tip tree and commit
> 22127e93c587 ("time: Replace __get_cpu_var uses") from the percpu tree.
> 
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).
> 
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
> 
> diff --cc kernel/irq_work.c
> index 385b85aded19,345d19edcdae..000000000000
> --- a/kernel/irq_work.c
> +++ b/kernel/irq_work.c
> @@@ -113,12 -113,10 +113,12 @@@ bool irq_work_needs_cpu(void
>   {
>   	struct llist_head *raised, *lazy;
>   
> - 	raised = &__get_cpu_var(raised_list);
> - 	lazy = &__get_cpu_var(lazy_list);
> + 	raised = this_cpu_ptr(&raised_list);
> + 	lazy = this_cpu_ptr(&lazy_list);

Ah thanks! The conflict is compile time rather than merge time, thanks
for spotting it!

Should we notify Linus about it? That's certainly something that should
be applied with the percpu tree.

>  -	if (llist_empty(raised) && llist_empty(lazy))
>  -		return false;
>  +
>  +	if (llist_empty(raised) || arch_irq_work_has_interrupt())
>  +		if (llist_empty(lazy))
>  +			return false;
>   
>   	/* All work should have been flushed before going offline */
>   	WARN_ON_ONCE(cpu_is_offline(smp_processor_id()));

  reply	other threads:[~2014-10-09 13:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09  4:50 linux-next: manual merge of the percpu tree with the tip tree Stephen Rothwell
2014-10-09 13:13 ` Frederic Weisbecker [this message]
2014-10-09 13:15   ` Tejun Heo
2014-10-09 13:18     ` Frederic Weisbecker
  -- strict thread matches above, loose matches on Subject: below --
2012-05-16  7:36 Stephen Rothwell
2012-05-16 13:40 ` Alex Shi
2011-04-20  3:50 Stephen Rothwell
2011-02-11  3:58 Stephen Rothwell
2011-02-11  9:52 ` Tejun Heo
2011-01-05  2:54 Stephen Rothwell
2010-12-31  2:55 Stephen Rothwell
2010-12-31 11:17 ` Tejun Heo
2010-12-31  2:55 Stephen Rothwell
2010-12-10  2:32 Stephen Rothwell
2010-02-03  5:38 Stephen Rothwell
2010-02-03 22:26 ` Frederic Weisbecker
2009-12-14  4:30 Stephen Rothwell
2009-11-11  7:59 Stephen Rothwell
2009-09-03  9:11 Stephen Rothwell
2009-07-06  5:06 Stephen Rothwell

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=20141009131328.GB25790@lerouge \
    --to=fweisbec@gmail.com \
    --cc=cl@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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