qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: borntraeger@de.ibm.com, qemu-s390x@nongnu.org, rth@twiddle.net,
	qemu-devel@nongnu.org, David Hildenbrand <david@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] s390: support EDAT-2 in mmu_translate_region
Date: Tue, 16 Jul 2019 15:04:19 +0200	[thread overview]
Message-ID: <20190716150419.6452ab9c.cohuck@redhat.com> (raw)
In-Reply-To: <20598EE9-577B-4C96-A106-4CFA2DB5D914@linux.ibm.com>

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?


  reply	other threads:[~2019-07-16 13:04 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 [this message]
2019-07-16 13:07       ` Ilya Leoshkevich
2019-07-16 13:11       ` Christian Borntraeger
2019-07-16 13:12         ` David Hildenbrand

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=20190716150419.6452ab9c.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=david@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).