All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <dgibson@redhat.com>
To: Laurent Vivier <laurent@vivier.eu>
Cc: Richard Henderson <richard.henderson@linaro.org>,
	Shivaprasad G Bhat <sbhat@linux.vnet.ibm.com>,
	riku.voipio@iki.fi, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] linux-user: ppc64: don't use volatile register during safe_syscall
Date: Tue, 31 Jul 2018 10:42:25 +1000	[thread overview]
Message-ID: <20180731104225.30522b28@umbus.fritz.box> (raw)
In-Reply-To: <f20a1874-bcdf-34cf-3c87-e3bc4d386eed@vivier.eu>

[-- Attachment #1: Type: text/plain, Size: 693 bytes --]

On Mon, 30 Jul 2018 21:16:35 +0200
Laurent Vivier <laurent@vivier.eu> wrote:

> Le 30/07/2018 à 14:44, Richard Henderson a écrit :
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
>  [...]  
> 
> Tested-by: Laurent Vivier <laurent@vivier.eu>
> Reviewed-by: Laurent Vivier <laurent@vivier.eu>
> 
> I think this patch should go into the next -rc because it fixes a lot of
> failures in the LTP on ppc64 host (hundreds of failure...).
> 
> David, if you want, I can take it through the linux-user tree.

That'd be great, thanks.

> 
> Thanks,
> Laurent


-- 
David Gibson <dgibson@redhat.com>
Principal Software Engineer, Virtualization, Red Hat

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-07-31  0:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-30 10:09 [Qemu-devel] [PATCH v3] linux-user: ppc64: don't use volatile register during safe_syscall Shivaprasad G Bhat
2018-07-30 12:44 ` Richard Henderson
2018-07-30 19:16   ` Laurent Vivier
2018-07-31  0:42     ` David Gibson [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=20180731104225.30522b28@umbus.fritz.box \
    --to=dgibson@redhat.com \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=riku.voipio@iki.fi \
    --cc=sbhat@linux.vnet.ibm.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.