From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, markver@us.ibm.com,
"Michael S. Tsirkin" <mst@redhat.com>,
Xie Yongji <xieyongji@bytedance.com>,
qemu-devel@nongnu.org, linux-kernel@vger.kernel.org,
Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Raphael Norwitz <raphael.norwitz@nutanix.com>,
stefanha@redhat.com, virtualization@lists.linux-foundation.org
Subject: Re: [RFC PATCH 1/1] virtio: write back features before verify
Date: Tue, 05 Oct 2021 17:25:32 +0200 [thread overview]
Message-ID: <87czoj1ok3.fsf@redhat.com> (raw)
In-Reply-To: <20211005135909.2b8ab021.pasic@linux.ibm.com>
On Tue, Oct 05 2021, Halil Pasic <pasic@linux.ibm.com> wrote:
> On Tue, 05 Oct 2021 13:13:31 +0200
> Cornelia Huck <cohuck@redhat.com> wrote:
>> Or am I misunderstanding what you're getting at?
>>
>
> Probably. I'm talking about pre- "do transport specific legacy detection
> in the device instead of looking at VERSION_1" you are probably talking
> about the post-state. If we had this new behavior for all relevant
> hypervisors then we wouldn't need to do a thing in the guest. The current
> code would work like charm.
Yeah, I was thinking more about the desired state. We need to both fix
QEMU (and other VMMs or devices should check whether they are doing the
right thing) and add a workaround on the driver side to make it work
with existing QEMUs.
next prev parent reply other threads:[~2021-10-05 15:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210930012049.3780865-1-pasic@linux.ibm.com>
[not found] ` <87r1d64dl4.fsf@redhat.com>
[not found] ` <20210930130350.0cdc7c65.pasic@linux.ibm.com>
[not found] ` <87ilyi47wn.fsf@redhat.com>
[not found] ` <20211001162213.18d7375e.pasic@linux.ibm.com>
[not found] ` <87v92g3h9l.fsf@redhat.com>
[not found] ` <20211002082128-mutt-send-email-mst@kernel.org>
[not found] ` <20211004042323.730c6a5e.pasic@linux.ibm.com>
2021-10-04 9:07 ` [RFC PATCH 1/1] virtio: write back features before verify Michael S. Tsirkin
2021-10-05 10:06 ` Cornelia Huck
2021-10-05 10:43 ` Halil Pasic
2021-10-05 11:11 ` Michael S. Tsirkin
2021-10-05 11:13 ` Cornelia Huck
2021-10-05 11:20 ` Michael S. Tsirkin
2021-10-05 11:59 ` Halil Pasic
2021-10-05 15:25 ` Cornelia Huck [this message]
[not found] ` <20210930070444-mutt-send-email-mst@kernel.org>
[not found] ` <20211001092125.64fef348.pasic@linux.ibm.com>
[not found] ` <20211002055605-mutt-send-email-mst@kernel.org>
2021-10-04 12:19 ` Cornelia Huck
2021-10-04 13:11 ` Michael S. Tsirkin
2021-10-04 14:33 ` Cornelia Huck
2021-10-04 15:07 ` Michael S. Tsirkin
2021-10-04 15:50 ` Cornelia Huck
2021-10-04 19:17 ` Michael S. Tsirkin
2021-10-06 10:13 ` Cornelia Huck
2021-10-06 12:15 ` Michael S. Tsirkin
2021-10-05 7:25 ` Halil Pasic
2021-10-05 7:53 ` Michael S. Tsirkin
2021-10-05 10:46 ` Halil Pasic
2021-10-05 11:11 ` Michael S. Tsirkin
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=87czoj1ok3.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=markver@us.ibm.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=raphael.norwitz@nutanix.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xieyongji@bytedance.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).