From: Cornelia Huck <cohuck@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Neo Jia <cjia@nvidia.com>, Eric Auger <eric.auger@redhat.com>,
Marc Zyngier <maz@kernel.org>,
qemu-devel@nongnu.org, dgilbert@redhat.com,
Shenming Lu <lushenming@huawei.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
qemu-arm@nongnu.org, yuzenghui@huawei.com,
wanghaibin.wang@huawei.com
Subject: Re: [PATCH RFC] vfio: Move the saving of the config space to the right place in VFIO migration
Date: Mon, 23 Nov 2020 14:52:34 +0100 [thread overview]
Message-ID: <20201123145234.266a7e42.cohuck@redhat.com> (raw)
In-Reply-To: <20201120150146.5e5693e9@w520.home>
On Fri, 20 Nov 2020 15:01:46 -0700
Alex Williamson <alex.williamson@redhat.com> wrote:
> Given our timing relative to QEMU 5.2, the only path I feel comfortable
> with is to move forward with downgrading vfio migration support to be
> enabled via an experimental option. Objections? Thanks,
>
> Alex
Agreed from my side. It seems better to give it one more release to
figure out some issues, and just mark it experimental for now.
prev parent reply other threads:[~2020-11-23 13:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 9:17 [PATCH RFC] vfio: Move the saving of the config space to the right place in VFIO migration Shenming Lu
2020-11-19 8:43 ` Kirti Wankhede
2020-11-19 17:41 ` Alex Williamson
2020-11-20 14:05 ` Shenming Lu
2020-11-20 22:01 ` Alex Williamson
2020-11-23 3:14 ` Shenming Lu
2020-11-23 19:33 ` Neo Jia
2020-11-23 21:46 ` Alex Williamson
2020-11-26 6:56 ` Shenming Lu
2020-11-30 17:03 ` Alex Williamson
2020-12-01 6:37 ` Shenming Lu
2020-12-01 22:21 ` Alex Williamson
2020-12-03 8:34 ` Shenming Lu
2020-12-02 10:55 ` Dr. David Alan Gilbert
2020-12-04 10:45 ` Shenming Lu
2020-11-24 11:01 ` Shenming Lu
2020-11-24 11:02 ` Dr. David Alan Gilbert
2020-11-23 13:52 ` Cornelia Huck [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=20201123145234.266a7e42.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=cjia@nvidia.com \
--cc=dgilbert@redhat.com \
--cc=eric.auger@redhat.com \
--cc=kwankhede@nvidia.com \
--cc=lushenming@huawei.com \
--cc=maz@kernel.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wanghaibin.wang@huawei.com \
--cc=yuzenghui@huawei.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.