From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Julien Grall <julien.grall@linaro.org>, stefano.stabellini@eu.citrix.com
Cc: ian.campbell@citrix.com, patches@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, xen-devel@lists.xen.org
Subject: Re: [PATCH v4] xen/arm: enable PV control for ARM
Date: Mon, 22 Jul 2013 20:32:06 -0400 [thread overview]
Message-ID: <5228e08a-1cdb-4240-b10f-9ad690c94ac4@email.android.com> (raw)
In-Reply-To: <1374529321-12955-1-git-send-email-julien.grall@linaro.org>
Julien Grall <julien.grall@linaro.org> wrote:
>Enable power management from the toolstack for ARM guest.
>
>Signed-off-by: Julien Grall <julien.grall@linaro.org>
>
>---
> Changes in v4:
> - Divide the patch in 2 distinct parts
> Changes in v3:
> - Fix condition to compile cpu_hotplug.o
> Changes in v2:
> - Don't compile xen/cpu_hotplug.o with ARM64
>---
> drivers/xen/Makefile | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
>diff --git a/drivers/xen/Makefile b/drivers/xen/Makefile
>index a609353..f185e8d 100644
>--- a/drivers/xen/Makefile
>+++ b/drivers/xen/Makefile
>@@ -1,9 +1,8 @@
> ifeq ($(filter y, $(CONFIG_ARM) $(CONFIG_ARM64)),)
>-obj-y += manage.o
> obj-$(CONFIG_HOTPLUG_CPU) += cpu_hotplug.o
> endif
> obj-$(CONFIG_X86) += fallback.o
>-obj-y += grant-table.o features.o events.o balloon.o time.o
>+obj-y += grant-table.o features.o events.o balloon.o time.o manage.o
> obj-y += xenbus/
>
> nostackp := $(call cc-option, -fno-stack-protector)
The patch looks Ok but the description is off. Power management is the term used for cpu freq, C states and P states. While this patch touches none of that.
next prev parent reply other threads:[~2013-07-23 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 21:42 Julien Grall
2013-07-23 0:32 ` Konrad Rzeszutek Wilk [this message]
2013-07-23 10:52 ` Julien Grall
2013-07-23 11:37 ` 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=5228e08a-1cdb-4240-b10f-9ad690c94ac4@email.android.com \
--to=konrad.wilk@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--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®