From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>,
qemu-s390x@nongnu.org
Cc: Alexander Graf <agraf@suse.de>, Cornelia Huck <cohuck@redhat.com>,
qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH RFC] s390x/kvm: call cpu_synchronize_state() on every kvm_arch_handle_exit()
Date: Thu, 5 Apr 2018 10:47:11 +0200 [thread overview]
Message-ID: <ce5e370a-3f39-71c2-3615-d7e9573a7cab@de.ibm.com> (raw)
In-Reply-To: <01b7db2f-d3a7-f9b1-2e76-9f33107cff4c@redhat.com>
On 04/05/2018 10:19 AM, Thomas Huth wrote:
> On 05.04.2018 09:53, Christian Borntraeger wrote:
>> So currently we only handle the case with base reg == 0 correctly.
>> So
>> diag x,y,0x500(0)
>> works
>>
>>
>> but things like
>> lghi 1,0x500
>> diag x,y,0(1)
>>
>> not unless I miss something.
>
> FWIW: Sounds like a good idea for a new kvm-unit-test... any volunteers?
It will require some special handling in the test as eventfd will handle diag
in the kvm kernel module most of the time. So such a test must have 2 pathes
with and without eventfd. As a virtio device we could simply use null-co or
something like that.
prev parent reply other threads:[~2018-04-05 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 9:20 [Qemu-devel] [PATCH RFC] s390x/kvm: call cpu_synchronize_state() on every kvm_arch_handle_exit() David Hildenbrand
2018-03-26 9:36 ` David Hildenbrand
2018-04-05 7:53 ` Christian Borntraeger
2018-04-05 8:03 ` David Hildenbrand
2018-04-05 8:03 ` Cornelia Huck
2018-04-05 8:19 ` Thomas Huth
2018-04-05 8:47 ` Christian Borntraeger [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=ce5e370a-3f39-71c2-3615-d7e9573a7cab@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=agraf@suse.de \
--cc=cohuck@redhat.com \
--cc=david@redhat.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 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.