From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
Jason Wang <jasowang@redhat.com>,
Xie Yongji <xieyongji@bytedance.com>,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
markver@us.ibm.com, linux-s390@vger.kernel.org,
stefanha@redhat.com,
Raphael Norwitz <raphael.norwitz@nutanix.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v3 1/1] virtio: write back F_VERSION_1 before validate
Date: Wed, 13 Oct 2021 14:52:38 +0200 [thread overview]
Message-ID: <87zgrdulwp.fsf@redhat.com> (raw)
In-Reply-To: <20211013081836-mutt-send-email-mst@kernel.org>
On Wed, Oct 13 2021, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Wed, Oct 13, 2021 at 01:23:50PM +0200, Christian Borntraeger wrote:
>> Can we get this kernel patch queued for 5.15 and stable without waiting for the QEMU patch
>> as we have a regression with 4.14?
>
> Probably. Still trying to decide between this and plain revert for 5.15
> and back. Maybe both?
Probably better queue this one, in case we have some undiscovered
problems with the config space access in virtio-net?
WARNING: multiple messages have this Message-ID (diff)
From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-s390@vger.kernel.org, markver@us.ibm.com,
qemu-devel@nongnu.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Halil Pasic <pasic@linux.ibm.com>,
Xie Yongji <xieyongji@bytedance.com>,
stefanha@redhat.com,
Raphael Norwitz <raphael.norwitz@nutanix.com>
Subject: Re: [PATCH v3 1/1] virtio: write back F_VERSION_1 before validate
Date: Wed, 13 Oct 2021 14:52:38 +0200 [thread overview]
Message-ID: <87zgrdulwp.fsf@redhat.com> (raw)
In-Reply-To: <20211013081836-mutt-send-email-mst@kernel.org>
On Wed, Oct 13 2021, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Wed, Oct 13, 2021 at 01:23:50PM +0200, Christian Borntraeger wrote:
>> Can we get this kernel patch queued for 5.15 and stable without waiting for the QEMU patch
>> as we have a regression with 4.14?
>
> Probably. Still trying to decide between this and plain revert for 5.15
> and back. Maybe both?
Probably better queue this one, in case we have some undiscovered
problems with the config space access in virtio-net?
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Cc: linux-s390@vger.kernel.org, markver@us.ibm.com,
qemu-devel@nongnu.org, Jason Wang <jasowang@redhat.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Halil Pasic <pasic@linux.ibm.com>,
Xie Yongji <xieyongji@bytedance.com>,
stefanha@redhat.com,
Raphael Norwitz <raphael.norwitz@nutanix.com>
Subject: Re: [PATCH v3 1/1] virtio: write back F_VERSION_1 before validate
Date: Wed, 13 Oct 2021 14:52:38 +0200 [thread overview]
Message-ID: <87zgrdulwp.fsf@redhat.com> (raw)
In-Reply-To: <20211013081836-mutt-send-email-mst@kernel.org>
On Wed, Oct 13 2021, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Wed, Oct 13, 2021 at 01:23:50PM +0200, Christian Borntraeger wrote:
>> Can we get this kernel patch queued for 5.15 and stable without waiting for the QEMU patch
>> as we have a regression with 4.14?
>
> Probably. Still trying to decide between this and plain revert for 5.15
> and back. Maybe both?
Probably better queue this one, in case we have some undiscovered
problems with the config space access in virtio-net?
next prev parent reply other threads:[~2021-10-13 12:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 5:39 [PATCH v3 1/1] virtio: write back F_VERSION_1 before validate Halil Pasic
2021-10-11 5:39 ` Halil Pasic
2021-10-11 5:39 ` Halil Pasic
2021-10-11 9:07 ` Cornelia Huck
2021-10-11 9:07 ` Cornelia Huck
2021-10-11 9:07 ` Cornelia Huck
2021-10-13 10:10 ` Michael S. Tsirkin
2021-10-13 10:10 ` Michael S. Tsirkin
2021-10-13 10:10 ` Michael S. Tsirkin
2021-10-13 11:23 ` Christian Borntraeger
2021-10-13 11:23 ` Christian Borntraeger
2021-10-13 11:23 ` Christian Borntraeger
2021-10-13 12:24 ` Michael S. Tsirkin
2021-10-13 12:24 ` Michael S. Tsirkin
2021-10-13 12:24 ` Michael S. Tsirkin
2021-10-13 12:44 ` Halil Pasic
2021-10-13 12:44 ` Halil Pasic
2021-10-13 12:44 ` Halil Pasic
2021-10-13 12:46 ` Michael S. Tsirkin
2021-10-13 12:46 ` Michael S. Tsirkin
2021-10-13 12:46 ` Michael S. Tsirkin
2021-10-13 12:52 ` Cornelia Huck [this message]
2021-10-13 12:52 ` Cornelia Huck
2021-10-13 12:52 ` Cornelia Huck
2021-10-13 12:55 ` Michael S. Tsirkin
2021-10-13 12:55 ` Michael S. Tsirkin
2021-10-13 12:55 ` 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=87zgrdulwp.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=jasowang@redhat.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=stable@vger.kernel.org \
--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 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.