From: Scott Wood <scottwood@freescale.com>
To: Stuart Yoder <stuart.yoder@freescale.com>
Cc: kvm-ppc@vger.kernel.org, linuxppc-dev@ozlabs.org, agraf@suse.de,
kvm@vger.kernel.org, Stuart Yoder <stuart.yoder@freescale.com>
Subject: Re: [PATCH] KVM: PPC: add paravirt idle loop for 64-bit book E
Date: Wed, 16 Jan 2013 11:44:18 -0600 [thread overview]
Message-ID: <1358358258.18317.3@snotra> (raw)
In-Reply-To: <1358356884-14216-1-git-send-email-stuart.yoder@freescale.com> (from stuart.yoder@freescale.com on Wed Jan 16 11:21:24 2013)
On 01/16/2013 11:21:24 AM, Stuart Yoder wrote:
> From: Stuart Yoder <stuart.yoder@freescale.com>
>=20
> loop was derived from book3e_idle()
>=20
> Signed-off-by: Stuart Yoder <stuart.yoder@freescale.com>
> ---
> arch/powerpc/kernel/epapr_hcalls.S | 63 =20
> ++++++++++++++++++++++++++++++++++++
> 1 file changed, 63 insertions(+)
>=20
> diff --git a/arch/powerpc/kernel/epapr_hcalls.S =20
> b/arch/powerpc/kernel/epapr_hcalls.S
> index 62c0dc2..6a46bfb 100644
> --- a/arch/powerpc/kernel/epapr_hcalls.S
> +++ b/arch/powerpc/kernel/epapr_hcalls.S
> @@ -17,6 +17,68 @@
> #include <asm/asm-compat.h>
> #include <asm/asm-offsets.h>
>=20
> +#ifdef CONFIG_PPC64
> +/* epapr_ev_idle() was derived from book3e_idle() */
> +_GLOBAL(epapr_ev_idle)
> + /* Save LR for later */
> + mflr r0
> + std r0,16(r1)
> +
> + /* Hard disable interrupts */
> + wrteei 0
> +
> + /* Now check if an interrupt came in while we were soft disabled
> + * since we may otherwise lose it (doorbells etc...).
> + */
> + lbz r3,PACAIRQHAPPENED(r13)
> + cmpwi cr0,r3,0
> + bnelr
> +
> + /* Now we are going to mark ourselves as soft and hard enabled =20
> in
> + * order to be able to take interrupts while asleep. We inform =20
> lockdep
> + * of that. We don't actually turn interrupts on just yet tho.
> + */
> +#ifdef CONFIG_TRACE_IRQFLAGS
> + stdu r1,-128(r1)
> + bl .trace_hardirqs_on
> + addi r1,r1,128
> +#endif
> + li r0,1
> + stb r0,PACASOFTIRQEN(r13)
> +=09
> + /* Interrupts will make use return to LR, so get something we =20
> want
> + * in there
> + */
> + bl 1f
> +
> + /* And return (interrupts are on) */
> + ld r0,16(r1)
> + mtlr r0
> + blr
> +
> +1: /* Let's set the _TLF_NAPPING flag so interrupts make us return
> + * to the right spot
> + */
> + CURRENT_THREAD_INFO(r11, r1)
> + ld r10,TI_LOCAL_FLAGS(r11)
> + ori r10,r10,_TLF_NAPPING
> + std r10,TI_LOCAL_FLAGS(r11)
> +
> + /* We can now re-enable hard interrupts and go to sleep */
> + wrteei 1
> +idle_loop:
> + LOAD_REG_IMMEDIATE(r11, EV_HCALL_TOKEN(EV_IDLE))
> +
> +.global epapr_ev_idle_start
> +epapr_ev_idle_start:
> + li r3, -1
> + nop
> + nop
> + nop
> + b idle_loop
> +
We should probably do this as an assembler macro, so we can have one =20
instance of it that gets instantiated for both "wait" and "ev_idle".
-Scott=
prev parent reply other threads:[~2013-01-16 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 17:21 [PATCH] KVM: PPC: add paravirt idle loop for 64-bit book E Stuart Yoder
2013-01-16 17:44 ` Scott Wood [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=1358358258.18317.3@snotra \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=stuart.yoder@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;
as well as URLs for NNTP newsgroup(s).