From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Rohit Khanna <rokhanna@nvidia.com>
Cc: "will.deacon@arm.com" <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Thierry Reding <treding@nvidia.com>,
Alexander Van Brunt <avanbrunt@nvidia.com>,
Bo Yan <byan@nvidia.com>, Jason Sequeira <jsequeira@nvidia.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] arm64: skip cpu nodes marked as disabled in DT
Date: Thu, 26 Apr 2018 11:18:02 +0100 [thread overview]
Message-ID: <20180426101802.GA1646@e107981-ln.cambridge.arm.com> (raw)
In-Reply-To: <20180426072514.GA33476@MBP.local>
On Thu, Apr 26, 2018 at 08:25:14AM +0100, Catalin Marinas wrote:
> On Wed, Apr 25, 2018 at 11:36:06PM +0000, Rohit Khanna wrote:
> > Adding few other folks.
>
> It looks fine to me but cc'ing Mark and Lorenzo (and it should have been
> posted on linux-arm-kernel@lists.infradead.org).
>
> > From: Rohit Khanna
> > Sent: Wednesday, April 25, 2018 4:08 PM
> > To: catalin.marinas@arm.com; will.deacon@arm.com
> > Cc: linux-kernel@vger.kernel.org; Rohit Khanna
> > Subject: [PATCH] arm64: skip cpu nodes marked as disabled in DT
> >
> > Skip the CPU nodes that are marked as disabled in DT.
> >
> > Bug 1828570
That's not information that can be used in its current form, which
bug-tracking system ?
> > Signed-off-by: Rohit Khanna <rokhanna@nvidia.com>
> > Reviewed-on: http://git-master/r/1245333
If it is a public mailing list discussion the
Link:
tag and the lkml redirector should be used, I do not know what the
redirector used here is though.
Process is defined here:
https://www.kernel.org/doc/html/latest/process/submitting-patches.html
> > Reviewed-by: Alexander Van Brunt <avanbrunt@nvidia.com>
> > ---
> > arch/arm64/kernel/smp.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/arch/arm64/kernel/smp.c b/arch/arm64/kernel/smp.c
> > index f3e2e3aec0b0..2b4371b0948d 100644
> > --- a/arch/arm64/kernel/smp.c
> > +++ b/arch/arm64/kernel/smp.c
> > @@ -578,6 +578,10 @@ static void __init of_parse_and_init_cpus(void)
> > for_each_node_by_type(dn, "cpu") {
> > u64 hwid = of_get_cpu_mpidr(dn);
> >
> > + /* Check to see if the cpu is disabled */
> > + if (!of_device_is_available(dn))
> > + goto next;
> > +
This was discussed a long time ago and kind of dropped - I digged the
thread out of archives for everyone's information:
http://lists.infradead.org/pipermail/linux-arm-kernel/2013-June/174324.html
Lorenzo
next prev parent reply other threads:[~2018-04-26 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 23:08 [PATCH] arm64: skip cpu nodes marked as disabled in DT Rohit Khanna
2018-04-25 23:36 ` Rohit Khanna
2018-04-26 7:25 ` Catalin Marinas
2018-04-26 10:18 ` Lorenzo Pieralisi [this message]
2018-04-26 19:54 ` Rohit Khanna
2018-04-30 9:54 ` 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=20180426101802.GA1646@e107981-ln.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=avanbrunt@nvidia.com \
--cc=byan@nvidia.com \
--cc=catalin.marinas@arm.com \
--cc=jsequeira@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rokhanna@nvidia.com \
--cc=treding@nvidia.com \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).