From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Liu Yu <yu.liu@freescale.com>
Cc: <agraf@suse.de>, <kvm-ppc@vger.kernel.org>, <kvm@vger.kernel.org>,
<linuxppc-dev@ozlabs.org>, <B07421@freescale.com>
Subject: Re: [PATCH v5 3/4] KVM: PPC: epapr: install ev_idle hcall for e500 guest
Date: Tue, 21 Feb 2012 18:53:33 +0800 [thread overview]
Message-ID: <4F4377AD.4000501@windriver.com> (raw)
In-Reply-To: <1329799573-8820-3-git-send-email-yu.liu@freescale.com>
Liu Yu wrote:
> If the guest hypervisor node contains "has-idle" property.
>
> Signed-off-by: Liu Yu <yu.liu@freescale.com>
> ---
> v5: no change
>
> arch/powerpc/kernel/epapr_hcalls.S | 29 +++++++++++++++++++++++++++++
> arch/powerpc/kernel/epapr_paravirt.c | 11 ++++++++++-
> 2 files changed, 39 insertions(+), 1 deletions(-)
>
> diff --git a/arch/powerpc/kernel/epapr_hcalls.S b/arch/powerpc/kernel/epapr_hcalls.S
> index 697b390..72fa234 100644
> --- a/arch/powerpc/kernel/epapr_hcalls.S
> +++ b/arch/powerpc/kernel/epapr_hcalls.S
> @@ -15,6 +15,35 @@
> #include <asm/ppc_asm.h>
> #include <asm/asm-offsets.h>
>
> +#define HC_VENDOR_EPAPR (1 << 16)
> +#define HC_EV_IDLE 16
Why not use 'EV_IDLE' directly?
> +
> +_GLOBAL(epapr_ev_idle)
> +epapr_ev_idle:
> + rlwinm r3,r1,0,0,31-THREAD_SHIFT /* current thread_info */
> + lwz r4,TI_LOCAL_FLAGS(r3) /* set napping bit */
> + ori r4,r4,_TLF_NAPPING /* so when we take an exception */
> + stw r4,TI_LOCAL_FLAGS(r3) /* it will return to our caller */
> +
> + wrteei 1
> +
> +idle_loop:
> + LOAD_REG_IMMEDIATE(r11, HC_VENDOR_EPAPR | HC_EV_IDLE)
And could this line be simplified as something like this:
LOAD_REG_IMMEDIATE(r11, EV_HCALL_TOKEN(EV_IDLE))
If so, even we can remove the previous HC_VENDOR_EPAPR definition as well.
Tiejun
> +
> +.global epapr_ev_idle_start
> +epapr_ev_idle_start:
> + li r3, -1
> + nop
> + nop
> + nop
> +
> + /*
> + * Guard against spurious wakeups from a hypervisor --
> + * only interrupt will cause us to return to LR due to
> + * _TLF_NAPPING.
> + */
> + b idle_loop
> +
> /* Hypercall entry point. Will be patched with device tree instructions. */
> .global epapr_hypercall_start
> epapr_hypercall_start:
> diff --git a/arch/powerpc/kernel/epapr_paravirt.c b/arch/powerpc/kernel/epapr_paravirt.c
> index e601da7..43d875e 100644
> --- a/arch/powerpc/kernel/epapr_paravirt.c
> +++ b/arch/powerpc/kernel/epapr_paravirt.c
> @@ -21,6 +21,10 @@
> #include <asm/epapr_hcalls.h>
> #include <asm/cacheflush.h>
> #include <asm/code-patching.h>
> +#include <asm/machdep.h>
> +
> +extern void epapr_ev_idle(void);
> +extern u32 epapr_ev_idle_start[];
>
> bool epapr_para_enabled = false;
>
> @@ -39,8 +43,13 @@ static int __init epapr_para_init(void)
>
> insts = of_get_property(hyper_node, "hcall-instructions", &len);
> if (insts && !(len % 4) && len <= (4 * 4)) {
> - for (i = 0; i < (len / 4); i++)
> + for (i = 0; i < (len / 4); i++) {
> patch_instruction(epapr_hypercall_start + i, insts[i]);
> + patch_instruction(epapr_ev_idle_start + i, insts[i]);
> + }
> +
> + if (of_get_property(hyper_node, "has-idle", NULL))
> + ppc_md.power_save = epapr_ev_idle;
>
> epapr_para_enabled = true;
> } else {
next prev parent reply other threads:[~2012-02-21 10:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 4:46 [PATCH v5 1/4] KVM: PPC: epapr: Factor out the epapr init Liu Yu
2012-02-21 4:46 ` [PATCH v5 2/4] KVM: PPC: epapr: Add idle hcall support for host Liu Yu
2012-02-21 4:46 ` [PATCH v5 3/4] KVM: PPC: epapr: install ev_idle hcall for e500 guest Liu Yu
2012-02-21 4:46 ` [PATCH v5 4/4] KVM: PPC: epapr: Update other hypercall invoking Liu Yu
2012-02-21 21:57 ` Scott Wood
2012-02-22 2:34 ` Liu Yu-B13201
2012-02-21 10:53 ` tiejun.chen [this message]
2012-02-22 2:29 ` [PATCH v5 3/4] KVM: PPC: epapr: install ev_idle hcall for e500 guest Liu Yu-B13201
2012-02-22 2:51 ` tiejun.chen
2012-02-22 2:59 ` Liu Yu-B13201
2012-02-21 21:56 ` [PATCH v5 1/4] KVM: PPC: epapr: Factor out the epapr init Scott Wood
2012-02-22 2:33 ` Liu Yu-B13201
2012-02-22 18:28 ` Scott Wood
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=4F4377AD.4000501@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=B07421@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=yu.liu@freescale.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