All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
	kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, drjones@redhat.com
Cc: dgibson@redhat.com, lvivier@redhat.com
Subject: Re: [kvm-unit-tests PATCH] powerpc/spapr_hcall: Fix assembler constraints of the h_random h-call
Date: Thu, 03 Mar 2016 12:58:48 +0000	[thread overview]
Message-ID: <56D83508.1000900@redhat.com> (raw)
In-Reply-To: <1457004188-17186-1-git-send-email-thuth@redhat.com>



On 03/03/2016 12:23, Thomas Huth wrote:
> As noted by Laurent Vivier, a register that is marked with "+r" as
> input and output is not required to be listed in the set of input
> registers anymore.
> And as noted by David Gibson, the sPAPR hypercall is also allowed to
> clobber a bunch of other registers. According to the LoPAPR spec,
> r0 and r3-r12, CTR, XER and CC registers are volatile, so we should
> mark them in the clobber list.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  powerpc/spapr_hcall.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/powerpc/spapr_hcall.c b/powerpc/spapr_hcall.c
> index 46731e1..dbff630 100644
> --- a/powerpc/spapr_hcall.c
> +++ b/powerpc/spapr_hcall.c
> @@ -96,7 +96,9 @@ static int h_random(uint64_t *val)
>  	register uint64_t r3 asm("r3") = H_RANDOM;
>  	register uint64_t r4 asm("r4");
>  
> -	asm volatile (" sc 1 " : "+r"(r3), "=r"(r4) : "r"(r3));
> +	asm volatile (" sc 1 "	: "+r"(r3), "=r"(r4) :
> +				: "r0", "r5", "r6", "r7", "r8", "r9", "r10",
> +				  "r11", "r12", "xer", "ctr", "cc");
>  	*val = r4;
>  
>  	return r3;
> 

Applied, thanks.

Paolo

WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>,
	kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, drjones@redhat.com
Cc: dgibson@redhat.com, lvivier@redhat.com
Subject: Re: [kvm-unit-tests PATCH] powerpc/spapr_hcall: Fix assembler constraints of the h_random h-call
Date: Thu, 3 Mar 2016 13:58:48 +0100	[thread overview]
Message-ID: <56D83508.1000900@redhat.com> (raw)
In-Reply-To: <1457004188-17186-1-git-send-email-thuth@redhat.com>



On 03/03/2016 12:23, Thomas Huth wrote:
> As noted by Laurent Vivier, a register that is marked with "+r" as
> input and output is not required to be listed in the set of input
> registers anymore.
> And as noted by David Gibson, the sPAPR hypercall is also allowed to
> clobber a bunch of other registers. According to the LoPAPR spec,
> r0 and r3-r12, CTR, XER and CC registers are volatile, so we should
> mark them in the clobber list.
> 
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  powerpc/spapr_hcall.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/powerpc/spapr_hcall.c b/powerpc/spapr_hcall.c
> index 46731e1..dbff630 100644
> --- a/powerpc/spapr_hcall.c
> +++ b/powerpc/spapr_hcall.c
> @@ -96,7 +96,9 @@ static int h_random(uint64_t *val)
>  	register uint64_t r3 asm("r3") = H_RANDOM;
>  	register uint64_t r4 asm("r4");
>  
> -	asm volatile (" sc 1 " : "+r"(r3), "=r"(r4) : "r"(r3));
> +	asm volatile (" sc 1 "	: "+r"(r3), "=r"(r4) :
> +				: "r0", "r5", "r6", "r7", "r8", "r9", "r10",
> +				  "r11", "r12", "xer", "ctr", "cc");
>  	*val = r4;
>  
>  	return r3;
> 

Applied, thanks.

Paolo

  reply	other threads:[~2016-03-03 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-03 11:23 [kvm-unit-tests PATCH] powerpc/spapr_hcall: Fix assembler constraints of the h_random h-call Thomas Huth
2016-03-03 11:23 ` Thomas Huth
2016-03-03 12:58 ` Paolo Bonzini [this message]
2016-03-03 12:58   ` Paolo Bonzini

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=56D83508.1000900@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dgibson@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=lvivier@redhat.com \
    --cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.