From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Ilya Leoshkevich <iii@linux.ibm.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH] s390: support EDAT-2 in mmu_translate_region
Date: Tue, 16 Jul 2019 15:12:23 +0200 [thread overview]
Message-ID: <9a5361b5-651d-1bcf-f31b-e666517b8a6d@redhat.com> (raw)
In-Reply-To: <712b5e21-80f1-8623-e23b-a41f2d5aff12@de.ibm.com>
On 16.07.19 15:11, Christian Borntraeger wrote:
>
> On 16.07.19 15:04, Cornelia Huck wrote:
>> On Tue, 16 Jul 2019 14:52:03 +0200
>> Ilya Leoshkevich <iii@linux.ibm.com> wrote:
>>
>>>> Am 16.07.2019 um 14:41 schrieb David Hildenbrand <david@redhat.com>:
>>>>
>>>> How urgent is this? If this can wait, I can polish and send my series I have here
>>>> instead, which also implents
>>>> - IEP support
>>>> - access-exception-fetch/store-indication facility
>>>> - ESOP-1, ESOP-2
>>>
>>> This is not urgent, I can live with my patch for now.
>>> It’s good to know that proper EDAT-2 support is being worked on.
>>>
>>> Thanks!
>>> Ilya
>>
>> Ok, so I will not queue this patch right now (I assume you're fine with
>> keeping this locally for now?), but wait for David's series for 4.2.
>>
>> Sounds reasonable?
>
> While not complete, Ilyas patch clearly improves the situation (and it is pretty
> similar to the EDAT-1 support).
> I think the question is: are there other instruction that we emulate in qemu via the
> page table walker even for KVM? I believe we always go via the kvm memory ioctl for
> page table access via instructions so the patch is not critical for KVM. So unless
> we have something I think Connys proposal is reasonable.
Yes, I remember we always go via the ioctl. Only debug memory accesses
take this path for KVM.
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2019-07-16 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 12:34 [Qemu-devel] [PATCH] s390: support EDAT-2 in mmu_translate_region Ilya Leoshkevich
2019-07-16 12:41 ` David Hildenbrand
2019-07-16 12:52 ` Ilya Leoshkevich
2019-07-16 13:04 ` Cornelia Huck
2019-07-16 13:07 ` Ilya Leoshkevich
2019-07-16 13:11 ` Christian Borntraeger
2019-07-16 13:12 ` David Hildenbrand [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=9a5361b5-651d-1bcf-f31b-e666517b8a6d@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=iii@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
/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).