From: Mark Rutland <mark.rutland@arm.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: "stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>,
"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"patches@linaro.org" <patches@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Catalin Marinas <Catalin.Marinas@arm.com>
Subject: Re: [PATCH] xen/arm64: Don't compile cpu hotplug
Date: Tue, 23 Jul 2013 10:35:13 +0100 [thread overview]
Message-ID: <20130723093513.GC4833@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1374529258-12866-1-git-send-email-julien.grall@linaro.org>
On Mon, Jul 22, 2013 at 10:40:58PM +0100, Julien Grall wrote:
> On ARM64, when CONFIG_XEN=y, the compilation will fail because CPU hotplug is
> not yet supported with XEN. For now, disable it.
>
> Signed-off-by: Julien Grall <julien.grall@linaro.org>
With this applied I'm able to build an arm64 kernel with both
CONFIG_HOTPLUG_CPU (from local patches) and CONFIG_XEN.
Acked-by: Mark Rutland <mark.rutland@arm.com>
Cheers,
Mark.
> ---
> drivers/xen/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/xen/Makefile b/drivers/xen/Makefile
> index 2bf461a..a609353 100644
> --- a/drivers/xen/Makefile
> +++ b/drivers/xen/Makefile
> @@ -1,4 +1,4 @@
> -ifneq ($(CONFIG_ARM),y)
> +ifeq ($(filter y, $(CONFIG_ARM) $(CONFIG_ARM64)),)
> obj-y += manage.o
> obj-$(CONFIG_HOTPLUG_CPU) += cpu_hotplug.o
> endif
> --
> 1.7.10.4
>
>
next prev parent reply other threads:[~2013-07-23 9:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 21:40 Julien Grall
2013-07-23 9:35 ` Mark Rutland [this message]
2013-07-23 11:35 ` 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=20130723093513.GC4833@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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
all inboxes | Powered by JetHome®