From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
qemu-devel@nongnu.org, Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v1 2/2] s390x: Use uint64_t for vector registers
Date: Wed, 29 May 2019 12:08:17 +0200 [thread overview]
Message-ID: <20190529120817.54ce2441.cohuck@redhat.com> (raw)
In-Reply-To: <20190529072726.7875-3-david@redhat.com>
On Wed, 29 May 2019 09:27:26 +0200
David Hildenbrand <david@redhat.com> wrote:
> CPU_DoubleU is primarily used to reinterpret between integer and floats.
> We don't really need this functionality. So let's just keep it simple
> and use an uint64_t.
>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> linux-user/s390x/signal.c | 4 +-
> target/s390x/arch_dump.c | 8 +--
> target/s390x/cpu.h | 4 +-
> target/s390x/excp_helper.c | 6 +-
> target/s390x/gdbstub.c | 16 ++---
> target/s390x/helper.c | 10 +--
> target/s390x/kvm.c | 16 ++---
> target/s390x/machine.c | 128 ++++++++++++++++++-------------------
> target/s390x/translate.c | 2 +-
> 9 files changed, 97 insertions(+), 97 deletions(-)
Indeed, we only ever accessed them via ->ll anyway.
(Migration looks unaffected as well.)
next prev parent reply other threads:[~2019-05-29 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 7:27 [Qemu-devel] [PATCH v1 0/2] s390x: Fix vector register alignment David Hildenbrand
2019-05-29 7:27 ` [Qemu-devel] [PATCH v1 1/2] s390x: Align vector registers to 16 bytes David Hildenbrand
2019-05-29 11:18 ` Richard Henderson
2019-05-29 7:27 ` [Qemu-devel] [PATCH v1 2/2] s390x: Use uint64_t for vector registers David Hildenbrand
2019-05-29 10:08 ` Cornelia Huck [this message]
2019-05-29 11:18 ` Richard Henderson
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=20190529120817.54ce2441.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--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 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).