From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Igor Mammedov <imammedo@redhat.com>,
qemu-arm@nongnu.org, Gavin Shan <gshan@redhat.com>
Subject: Re: [PATCH v1 0/5] virtio-mem: Device unplug support
Date: Fri, 23 Jun 2023 01:58:56 -0400 [thread overview]
Message-ID: <20230623015740-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20230613150210.449406-1-david@redhat.com>
On Tue, Jun 13, 2023 at 05:02:05PM +0200, David Hildenbrand wrote:
> One limitation of virtio-mem is that we cannot currently unplug virtio-mem
> devices that have all memory unplugged from the VM.
>
> Let's properly handle forced unplug (as can be triggered by the VM) and
> add support for ordinary unplug (requests) of virtio-mem devices that are
> in a compatible state (no legacy mode, no plugged memory, no plug request).
>
> Briefly tested on both, x86_64 and aarch64.
>
> Cc: Peter Maydell <peter.maydell@linaro.org>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Richard Henderson <richard.henderson@linaro.org>
> Cc: Eduardo Habkost <eduardo@habkost.net>
> Cc: "Michael S. Tsirkin" <mst@redhat.com>
> Cc: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
> Cc: Igor Mammedov <imammedo@redhat.com>
> Cc: qemu-arm@nongnu.org
> Cc: Gavin Shan <gshan@redhat.com>
Lots of duplication pc/arm. Which is not new but do we have to keep
growing this? Can't we put at least the new common code somewhere?
What do ARM maintainers think about it?
> David Hildenbrand (5):
> pc: Properly handle unplug of virtio based memory devices
> arm/virt: Properly handle unplug of virtio based memory devices
> virtio-mem: Prepare for unplug support of virtio-mem-pci devices
> pc: Support unplug of virtio-mem-pci devices
> arm/virt: Support unplug of virtio-mem-pci devices
>
> hw/arm/virt.c | 60 +++++++++++++++++++++++++++++--
> hw/i386/pc.c | 66 ++++++++++++++++++++++++++++++----
> hw/virtio/virtio-mem-pci.c | 42 ++++++++++++++++++++--
> hw/virtio/virtio-mem-pci.h | 2 ++
> hw/virtio/virtio-mem.c | 24 +++++++++++++
> include/hw/virtio/virtio-mem.h | 2 ++
> 6 files changed, 183 insertions(+), 13 deletions(-)
>
> --
> 2.40.1
next prev parent reply other threads:[~2023-06-23 5:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 15:02 [PATCH v1 0/5] virtio-mem: Device unplug support David Hildenbrand
2023-06-13 15:02 ` [PATCH v1 1/5] pc: Properly handle unplug of virtio based memory devices David Hildenbrand
2023-06-13 15:02 ` [PATCH v1 2/5] arm/virt: " David Hildenbrand
2023-06-13 15:02 ` [PATCH v1 3/5] virtio-mem: Prepare for unplug support of virtio-mem-pci devices David Hildenbrand
2023-06-13 15:02 ` [PATCH v1 4/5] pc: Support unplug " David Hildenbrand
2023-06-13 15:02 ` [PATCH v1 5/5] arm/virt: " David Hildenbrand
2023-06-23 5:58 ` Michael S. Tsirkin [this message]
2023-06-23 7:04 ` [PATCH v1 0/5] virtio-mem: Device unplug support David Hildenbrand
2023-06-23 7:09 ` 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=20230623015740-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=david@redhat.com \
--cc=eduardo@habkost.net \
--cc=gshan@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/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).