linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] xen/arm: enable PV control for ARM
Date: Mon, 22 Jul 2013 15:39:20 +0100	[thread overview]
Message-ID: <20130722143920.GC32221@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1307221459200.4893@kaball.uk.xensource.com>

On Mon, Jul 22, 2013 at 03:09:35PM +0100, Stefano Stabellini wrote:
> On Mon, 22 Jul 2013, Mark Rutland wrote:
> > Hi,
> > 
> > [Adding Catalin to Cc]
> > 
> > On Mon, Jul 22, 2013 at 11:57:34AM +0100, Julien Grall wrote:
> > > Enable power management from the toolstack for ARM guest.
> > > 
> > > Signed-off-by: Julien Grall <julien.grall@linaro.org>
> > > 
> > > ---
> > >     Changes in v3:
> > >         - Fix condition to compile cpu_hotplug.o
> > >     Changes in v2:
> > >         - Don't compile xen/cpu_hotplug.o with ARM64
> > 
> > My arm64 cpu hotplug series is going to be dependent on not compiling
> > xen/cpu_hotplug.o. Currently I'm not able to compile an arm64 kernel
> > with my patches and Xen support.
> > 
> > How do you intend to push this? I'd like to ensure my cpu hotplug series
> > is able to go in for the next merge window.
> 
> This patch does exactly that: it makes sure cpu_hotplug is not compiled
> on ARM64.

Sorry, what I meant was that my series is going to be entirely dependent
on this patch or it'll break bisection. That'll make merging things a
little painful as I'll need a stable branch with this patch to base my
series upon.

Another option would be to split this patch into two parts, one enabling
power management and one fixing things up for HOTPLUG_CPU on arm64. That
way I could take the arm64 HOTPLUG_CPU fix in my series adding arm64
HOTPLUG_CPU support.

Would that be acceptable? Have I missed something?

> Given that this patch is for drivers/xen/Makefile, normally it goes via
> Konrad's tree.
> 
> 
> > > ---
> > >  drivers/xen/Makefile |    5 ++---
> > >  1 file changed, 2 insertions(+), 3 deletions(-)
> > > 
> > > diff --git a/drivers/xen/Makefile b/drivers/xen/Makefile
> > > index 2bf461a..f185e8d 100644
> > > --- a/drivers/xen/Makefile
> > > +++ b/drivers/xen/Makefile
> > > @@ -1,9 +1,8 @@
> > > -ifneq ($(CONFIG_ARM),y)
> > > -obj-y	+= manage.o
> > > +ifeq ($(filter y, $(CONFIG_ARM) $(CONFIG_ARM64)),)
> > >  obj-$(CONFIG_HOTPLUG_CPU)		+= cpu_hotplug.o
> > >  endif
> > 
> > Might it make sense to enable this based on a list the architectures
> > that actually need this, rather than disabling it based on the list of
> > architectures that don't?
> 
> This is more philosophical than practical, but I would expect this
> limitation to go away soon, and be able to compile cpu_hotplug without
> issues on ARM and ARM64 too.
> 

Ok, that's fine then.

Thanks,
Mark.

  reply	other threads:[~2013-07-22 14:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 10:57 [PATCH v3] xen/arm: enable PV control for ARM Julien Grall
2013-07-22 13:49 ` Mark Rutland
2013-07-22 14:09   ` Stefano Stabellini
2013-07-22 14:39     ` Mark Rutland [this message]
2013-07-22 14:46       ` Stefano Stabellini
2013-07-22 20:00         ` Konrad Rzeszutek Wilk
2013-07-22 14:09 ` Stefano Stabellini

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=20130722143920.GC32221@e106331-lin.cambridge.arm.com \
    --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;
as well as URLs for NNTP newsgroup(s).