From: David Hildenbrand Date: Fri, 10 Jun 2022 09:47:37 +0000 (+0200) Subject: drivers/virtio: Clarify CONFIG_VIRTIO_MEM for unsupported architectures X-Git-Tag: v6.1-rc5~611^2~78 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=0b6fd46ec5f5720b76cbb01300ed9f7b7c6365c4;p=platform%2Fkernel%2Flinux-starfive.git drivers/virtio: Clarify CONFIG_VIRTIO_MEM for unsupported architectures Let's make it clearer that simply unlocking CONFIG_VIRTIO_MEM on an architecture is most probably not sufficient to have it working as expected. Cc: "Michael S. Tsirkin" Cc: Jason Wang Cc: Gavin Shan Signed-off-by: David Hildenbrand Message-Id: <20220610094737.65254-1-david@redhat.com> Signed-off-by: Michael S. Tsirkin --- diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig index afb9051..02bbccd 100644 --- a/drivers/virtio/Kconfig +++ b/drivers/virtio/Kconfig @@ -123,9 +123,11 @@ config VIRTIO_MEM This driver provides access to virtio-mem paravirtualized memory devices, allowing to hotplug and hotunplug memory. - This driver was only tested under x86-64 and arm64, but should - theoretically work on all architectures that support memory hotplug - and hotremove. + This driver currently only supports x86-64 and arm64. Although it + should compile on other architectures that implement memory + hot(un)plug, architecture-specific and/or common + code changes may be required for virtio-mem, kdump and kexec to work as + expected. If unsure, say M.