All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH] sched/x86: Calculate booted cores after construction of sibling_mask
Date: Fri, 1 Jun 2012 12:18:15 +0530	[thread overview]
Message-ID: <20120601064815.GJ7511@linux.vnet.ibm.com> (raw)
In-Reply-To: <1338496257.28384.121.camel@twins>

* Peter Zijlstra <peterz@infradead.org> [2012-05-31 22:30:57]:

(snip)
> > 
> > sched/x86: Calculate booted cores after construction of sibling_mask
> 
> Why repeat this subject again?
> 
Will take care of it from next posting.

(snip)
> > diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
> > index fd019d7..a8d78f3 100644
> > --- a/arch/x86/kernel/smpboot.c
> > +++ b/arch/x86/kernel/smpboot.c
> > @@ -382,7 +382,12 @@ void __cpuinit set_cpu_sibling_map(int cpu)
> >  		if ((i == cpu) || (has_mc && match_llc(c, o)))
> >  			link_mask(llc_shared, cpu, i);
> > 
> > -		if ((i == cpu) || (has_mc && match_mc(c, o))) {
> > +	}
> > +
> > +	for_each_cpu(i, cpu_sibling_setup_mask) {
> > +		o = &cpu_data(i);
> > +
> > +	if ((i == cpu) || (has_mc && match_mc(c, o))) {
> >  			link_mask(core, cpu, i);
> > 
> >  			/*
> 
> This patch actually horribly mangles the indenting. I did the below to
> it:

Sorry about the indentation. Thanks for fixing it.



  reply	other threads:[~2012-06-01  6:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31  7:37 [PATCH] sched/x86: Calculate booted cores after construction of sibling_mask Kamalesh Babulal
2012-05-31 20:30 ` Peter Zijlstra
2012-06-01  6:48   ` Kamalesh Babulal [this message]
2012-06-01 10:08     ` Peter Zijlstra
2012-06-06 15:52 ` [tip:sched/urgent] " tip-bot for Kamalesh Babulal

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=20120601064815.GJ7511@linux.vnet.ibm.com \
    --to=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.