From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 02/12] arm64: smp_plat: add get_logical_index
Date: Tue, 19 May 2015 10:10:57 +0100 [thread overview]
Message-ID: <20150519091057.GA32656@leverpostej> (raw)
In-Reply-To: <20150519083154.GU21251@e104818-lin.cambridge.arm.com>
> > > > +/*
> > > > + * Retrieve logical cpu index corresponding to a given MPIDR.Aff*
> > > > + * - mpidr: MPIDR.Aff* bits to be used for the look-up
> > > > + *
> > > > + * Returns the cpu logical index or -EINVAL on look-up error
> > > > + */
> > > > +static inline int get_logical_index(u64 mpidr)
> > > > +{
> > > > + int cpu;
> > > > + for (cpu = 0; cpu < nr_cpu_ids; cpu++)
> > > > + if (cpu_logical_map(cpu) == mpidr)
> > > > + return cpu;
> > > > + return -EINVAL;
> > > > +}
> > >
> > > Do we guarantee that mpidr here only contains the affinity bits (i.e. no
> > > masking)?
> >
> > In the DT and ACPI probe paths we reject IDs with bits other than the
> > aff bits set.
> >
> > I don't currently have a sanity check in the code handling
> > MIGRATE_INFO_UP_CPU, but I should add one.
> >
> > Would you like a warning here too?
>
> Or maybe just the warning if the code paths to this function already
> mask out the non-affinity bits.
Sure; that's what I meant about a sanity check in the code handling
MIGRATE_INFO_UP_CPU (where query a CPU ID from the PSCI implementation).
I'll see about adding a warning there.
In the DT and ACPI parsing cases we already warn if non-affinity bits
are set.
Thanks,
Mark.
next prev parent reply other threads:[~2015-05-19 9:10 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-18 10:38 [PATCHv2 00/12] arm/arm64: Unify PSCI client support Mark Rutland
2015-05-18 10:38 ` [PATCHv2 01/12] arm/arm64: kvm: add missing PSCI include Mark Rutland
2015-05-19 3:37 ` Hanjun Guo
2015-05-18 10:38 ` [PATCHv2 02/12] arm64: smp_plat: add get_logical_index Mark Rutland
2015-05-18 17:09 ` Catalin Marinas
2015-05-18 17:55 ` Mark Rutland
2015-05-19 3:47 ` Hanjun Guo
2015-05-19 8:31 ` Catalin Marinas
2015-05-19 9:10 ` Mark Rutland [this message]
2015-05-18 10:38 ` [PATCHv2 03/12] arm64: smp: consistently use error codes Mark Rutland
2015-05-18 17:21 ` Catalin Marinas
2015-05-19 8:17 ` Hanjun Guo
2015-05-18 10:38 ` [PATCHv2 04/12] arm64: psci: remove unnecessary id indirection Mark Rutland
2015-05-18 17:28 ` Catalin Marinas
2015-05-19 8:21 ` Hanjun Guo
2015-05-18 10:38 ` [PATCHv2 05/12] arm64: psci: support unsigned return values Mark Rutland
2015-05-18 17:29 ` Catalin Marinas
2015-05-19 8:25 ` Hanjun Guo
2015-05-18 10:38 ` [PATCHv2 06/12] arm64: psci: account for Trusted OS instances Mark Rutland
2015-05-18 17:33 ` Catalin Marinas
2015-05-18 10:38 ` [PATCHv2 07/12] arm64: psci: kill psci_power_state Mark Rutland
2015-05-18 17:36 ` Catalin Marinas
2015-05-18 18:11 ` Mark Rutland
2015-05-18 10:38 ` [PATCHv2 08/12] arm64: psci: remove ACPI coupling Mark Rutland
2015-05-18 17:38 ` Catalin Marinas
2015-05-19 8:40 ` Hanjun Guo
2015-05-19 9:18 ` Mark Rutland
2015-05-18 10:38 ` [PATCHv2 09/12] arm64: psci: factor invocation code to drivers Mark Rutland
2015-05-18 17:40 ` Catalin Marinas
2015-05-19 8:46 ` Hanjun Guo
2015-05-18 10:38 ` [PATCHv2 10/12] drivers: psci: support native SMC{32,64} calls Mark Rutland
2015-05-18 17:43 ` Catalin Marinas
2015-05-18 17:49 ` Mark Rutland
2015-05-18 10:38 ` [PATCHv2 11/12] ARM: migrate to common PSCI client code Mark Rutland
2015-05-18 17:45 ` Catalin Marinas
2015-05-18 10:38 ` [PATCHv2 12/12] MAINTAINERS: add PSCI entry Mark Rutland
2015-05-18 17:45 ` Catalin Marinas
2015-05-18 17:49 ` [PATCHv2 00/12] arm/arm64: Unify PSCI client support Catalin Marinas
2015-05-19 9:03 ` Lorenzo Pieralisi
2015-05-19 9:32 ` Mark Rutland
2015-05-19 15:20 ` Catalin Marinas
2015-05-19 8:54 ` Hanjun Guo
2015-05-19 9:33 ` Mark Rutland
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=20150519091057.GA32656@leverpostej \
--to=mark.rutland@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