From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Li Yang <leoli@freescale.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Chenhui Zhao <chenhui.zhao@freescale.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Zhuoyu.Zhang@freescale.com" <Zhuoyu.Zhang@freescale.com>,
"Jason.Jin@freescale.com" <Jason.Jin@freescale.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH 1/3] arm: ls1: add CPU hotplug platform support
Date: Sun, 28 Sep 2014 15:27:26 +0100 [thread overview]
Message-ID: <20140928142726.GH5182@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CADRPPNQULzPhHt3Kk1EUnPRkfFOPGsWY4AqWEv=AdBc5y-Gg+Q@mail.gmail.com>
On Sun, Sep 28, 2014 at 06:57:18PM +0800, Li Yang wrote:
> On Fri, Sep 26, 2014 at 9:20 PM, Mark Rutland <mark.rutland@arm.com> wrote:
> >> > This looks to be a carbon copy of the vexpress pseudo-hotplug in
> >> > arch/arm/mach-vexpress/hotplug.c, which is obviously broken in the way
> >> > you describe above. Perhaps we should go about ripping that out?
> >>
> >> The Versatile Express does not support suspend so the only problem case
> >> is kexec. However, isn't this support needed for big.LITTLE, and as
> >> the Versatile Express is the platform which these features get developed
> >> on, having working CPU hotplug seems rather fundamental for ARM kernel
> >> feature development.
> >>
> >> In that regard, Versatile Express is something of a special case.
> >
> > It is admittedly helpful during development to perform pseudo-hotplug on
> > Versatile Express. I have a local patch adding vexpress_cpu_disable so I
> > can test for bugs that only trigger if CPU0 is hotplugged.
> >
> > Given that, perhaps we should make it clearer that Versatile Express is
> > not a reference implementation for CPU hotplug; add some Kconfig (e.g.
> > VEXPRESS_PSEUDO_HOTPLUG) that depends on !KEXEC && !SUSPEND, and putting
> > a note in hotplug.c stating it's not suitable as a reference
> > implementation.
> >
> > ...but perhaps that's overkill.
>
> I agree that the pseudo-hotplug is breaking the kexec. However, I
> don't think it breaks the system suspend case as tasks and interrupts
> have been moved out of the non-booting CPU. The pseudo-hotplug would
> be even better than real hotplug as it introduces less latency.
Sorry, that's not an acceptable reason to use it.
NAK.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2014-09-28 14:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1411730703-25836-1-git-send-email-chenhui.zhao@freescale.com>
[not found] ` <1411730703-25836-2-git-send-email-chenhui.zhao@freescale.com>
[not found] ` <20140926122003.GP5182@n2100.arm.linux.org.uk>
[not found] ` <20140926124614.GD7422@leverpostej>
[not found] ` <20140926130311.GQ5182@n2100.arm.linux.org.uk>
[not found] ` <20140926132038.GF7422@leverpostej>
2014-09-28 10:57 ` [PATCH 1/3] arm: ls1: add CPU hotplug platform support Li Yang
2014-09-28 14:27 ` Russell King - ARM Linux [this message]
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=20140928142726.GH5182@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=Jason.Jin@freescale.com \
--cc=Zhuoyu.Zhang@freescale.com \
--cc=chenhui.zhao@freescale.com \
--cc=kernel@pengutronix.de \
--cc=leoli@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@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).