linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/5] ARM: kernel: smp_setup_processor_id() updates
Date: Thu, 15 Nov 2012 14:18:09 +0000	[thread overview]
Message-ID: <20121115141808.GA23513@e102568-lin.cambridge.arm.com> (raw)
In-Reply-To: <20121115134951.GF5570@mudshark.cambridge.arm.com>

[CC'ed Vincent following MPIDR mask query]

On Thu, Nov 15, 2012 at 01:49:51PM +0000, Will Deacon wrote:
> On Thu, Nov 15, 2012 at 12:46:50PM +0000, Lorenzo Pieralisi wrote:
> > This patch applies some basic changes to the smp_setup_processor_id()
> > ARM implementation to make the code that builds cpu_logical_map more
> > uniform across the kernel.
> > 
> > The function now prints the full extent of the boot CPU MPIDR[23:0] and
> > initializes the cpu_logical_map for CPUs up to nr_cpu_ids.
> > 
> > Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > ---
> >  arch/arm/kernel/setup.c | 7 ++++---
> >  1 file changed, 4 insertions(+), 3 deletions(-)
> > 
> > diff --git a/arch/arm/kernel/setup.c b/arch/arm/kernel/setup.c
> > index da1d1aa..d0df6c8 100644
> > --- a/arch/arm/kernel/setup.c
> > +++ b/arch/arm/kernel/setup.c
> > @@ -426,13 +426,14 @@ int __cpu_logical_map[NR_CPUS];
> >  void __init smp_setup_processor_id(void)
> >  {
> >  	int i;
> > -	u32 cpu = is_smp() ? read_cpuid_mpidr() & 0xff : 0;
> > +	u32 mpidr = is_smp() ? read_cpuid_mpidr() & 0xffffff : 0;
> > +	u32 cpu = mpidr & 0xff;
> 
> Can we move the #defines out of topology.c and use those instead of magic
> masks please? You could use MPIDR_HWID_BITMASK, although the LEVEL mask
> definitions over there don't look right to me (MPIDR_LEVEL0_MASK is 0x3?)

Yes, I should have done that, you are right. LEVEL0 and LEVEL1 masks look
wrong to me.

#define MPIDR_LEVEL0_MASK 0x3
#define MPIDR_LEVEL1_MASK 0xF

Vincent, why are they defined with those values ? They should all be
defined as 0xFF.

I will fix them and move them to a header file.

Thanks,
Lorenzo

  reply	other threads:[~2012-11-15 14:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-15 12:46 [PATCH v3 0/5] ARM: multi-cluster aware boot protocol Lorenzo Pieralisi
2012-11-15 12:46 ` [PATCH v3 1/5] ARM: kernel: smp_setup_processor_id() updates Lorenzo Pieralisi
2012-11-15 13:49   ` Will Deacon
2012-11-15 14:18     ` Lorenzo Pieralisi [this message]
2012-11-16 10:17       ` Vincent Guittot
2012-11-19  3:08   ` Nicolas Pitre
2012-11-15 12:46 ` [PATCH v3 2/5] ARM: kernel: add device tree init map function Lorenzo Pieralisi
2012-11-19  3:12   ` Nicolas Pitre
2012-11-19 11:02   ` Mark Rutland
2012-11-15 12:46 ` [PATCH v3 3/5] ARM: kernel: add cpu logical map DT init in setup_arch Lorenzo Pieralisi
2012-11-19  3:14   ` Nicolas Pitre
2012-11-15 12:46 ` [PATCH v3 4/5] ARM: kernel: add logical mappings look-up Lorenzo Pieralisi
2012-11-19  3:14   ` Nicolas Pitre
2012-11-15 12:46 ` [PATCH v3 5/5] ARM: gic: use a private mapping for CPU target interfaces Lorenzo Pieralisi

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=20121115141808.GA23513@e102568-lin.cambridge.arm.com \
    --to=lorenzo.pieralisi@arm.com \
    --cc=linux-arm-kernel@lists.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 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).