From: David Hildenbrand <david@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
Thomas Huth <thuth@redhat.com>, Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v1 0/3] s390x: SIGP + IRQ preparations for TCG vector register support
Date: Fri, 22 Feb 2019 11:26:02 +0100 [thread overview]
Message-ID: <5cdeb740-a50e-f2bf-b8c5-5e6c70abf70c@redhat.com> (raw)
In-Reply-To: <20190222111626.5a09c4d8.cohuck@redhat.com>
On 22.02.19 11:16, Cornelia Huck wrote:
> On Fri, 22 Feb 2019 09:11:50 +0100
> David Hildenbrand <david@redhat.com> wrote:
>
>> These are minor preparations for vector instruction support for TCG, also
>> touching KVM code.
>>
>> During SIGP STORE ADDITIONAL STATUS we have to properly convert the
>> endianess. On machine checks, we have to also store the vector registers
>> into the extended save area.
>>
>> Both changes are not used by TCG code before we implement + enable
>> vector instructions. KVM code shares the SIGP STORE ADDITIONAL STATUS
>> implementation.
>>
>> Note: Vector registers (128 bit) are modeled as two 64 bit values. Low and
>> high 64 bit values correspond on big/little systems, however the values
>> themself need conversion. Documentation for that will be added along with
>> the actual vector instruction support.
>>
>> David Hildenbrand (3):
>> s390x: Use cpu_to_be64 in SIGP STORE ADDITIONAL STATUS
>> s390x: use a QEMU-style typedef + name for SIGP save area struct
>> s390x/tcg: Save vregs to extended mchk save area
>>
>> target/s390x/excp_helper.c | 46 ++++++++++++++++++++++++++++++++++++--
>> target/s390x/helper.c | 39 ++++++++++++++++++++------------
>> target/s390x/internal.h | 4 +++-
>> 3 files changed, 72 insertions(+), 17 deletions(-)
>>
>
> Quick question: Unlike your floating-point patch series, this does not
> depend on anything not going through the s390x tree, right?
>
While these patches are based on the others, they should apply and work
just nicely without the floating-point patches.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-02-22 10:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 8:11 [Qemu-devel] [PATCH v1 0/3] s390x: SIGP + IRQ preparations for TCG vector register support David Hildenbrand
2019-02-22 8:11 ` [Qemu-devel] [PATCH v1 1/3] s390x: Use cpu_to_be64 in SIGP STORE ADDITIONAL STATUS David Hildenbrand
2019-02-22 8:55 ` Thomas Huth
2019-02-22 11:23 ` Christian Borntraeger
2019-02-22 8:11 ` [Qemu-devel] [PATCH v1 2/3] s390x: use a QEMU-style typedef + name for SIGP save area struct David Hildenbrand
2019-02-22 8:36 ` Thomas Huth
2019-02-22 11:24 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2019-02-22 8:11 ` [Qemu-devel] [PATCH v1 3/3] s390x/tcg: Save vregs to extended mchk save area David Hildenbrand
2019-02-22 9:09 ` Thomas Huth
2019-02-22 10:20 ` Cornelia Huck
2019-02-22 10:16 ` [Qemu-devel] [PATCH v1 0/3] s390x: SIGP + IRQ preparations for TCG vector register support Cornelia Huck
2019-02-22 10:26 ` David Hildenbrand [this message]
2019-02-25 11:21 ` Cornelia Huck
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=5cdeb740-a50e-f2bf-b8c5-5e6c70abf70c@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@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).