From: David Hildenbrand <david@redhat.com>
To: Michal Marek <mmarek@suse.com>,
Richard Henderson <rth@twiddle.net>,
Alexander Graf <agraf@suse.de>, Thomas Huth <thuth@redhat.com>
Cc: Eric Bischoff <ebischoff@suse.com>,
Miroslav Benes <mbenes@suse.cz>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4] target-s390x: Implement stfl and stfle
Date: Thu, 2 Mar 2017 14:12:42 +0100 [thread overview]
Message-ID: <eba82ba0-2edb-834d-3b10-ae9b053c93c3@redhat.com> (raw)
In-Reply-To: <175599de-8f4f-8d22-d36e-6fb250ec49f4@suse.com>
>> As it happens, this reminds me that I wrote a version of this several
>> years ago but never submitted it upstream. I'll dig it out.
>
> So, does it make sense for me to post a v5 again not using
> s390_cpu_virt_mem_write(), or are you going to refresh your stfle
> implementation?
>
> Thanks,
> Michal
>
A new implementation should definitely take care of the CPU model.
--
Thanks,
David
prev parent reply other threads:[~2017-03-02 13:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 13:44 [Qemu-devel] [PATCH] target-s390x: Implement stfl and stfle Michal Marek
2017-02-24 14:51 ` no-reply
2017-02-24 15:22 ` Michal Marek
2017-02-24 16:28 ` David Hildenbrand
2017-02-25 0:05 ` Richard Henderson
2017-02-25 20:39 ` Michal Marek
2017-02-25 23:30 ` Michal Marek
2017-02-25 23:16 ` [Qemu-devel] [PATCH v2] " Michal Marek
2017-02-25 23:38 ` [Qemu-devel] [PATCH v3] " Michal Marek
2017-02-26 11:22 ` Thomas Huth
2017-02-26 18:57 ` Michal Marek
2017-02-27 7:30 ` Thomas Huth
2017-02-27 10:18 ` [Qemu-devel] [PATCH v4] " Michal Marek
2017-02-28 22:11 ` Richard Henderson
2017-03-01 8:00 ` Thomas Huth
2017-03-01 19:30 ` Richard Henderson
2017-03-01 20:20 ` Thomas Huth
2017-03-02 13:09 ` David Hildenbrand
2017-03-02 10:53 ` Michal Marek
2017-03-02 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=eba82ba0-2edb-834d-3b10-ae9b053c93c3@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=ebischoff@suse.com \
--cc=mbenes@suse.cz \
--cc=mmarek@suse.com \
--cc=qemu-devel@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).