On Tue, Jan 18, 2022 at 05:38:20PM +0800, Gavin Shan wrote: > On 1/18/22 4:48 PM, Gavin Shan wrote: > > This enables virtio-mem device support by allowing to enable the > > corresponding kernel config option (CONFIG_VIRTIO_MEM) on the > > architecture. > > > > Signed-off-by: Gavin Shan <gshan@xxxxxxxxxx> > > Acked-by: David Hildenbrand <david@xxxxxxxxxx> > > --- > > v2: Improved the comments about the kernel config option (David) > > --- > > drivers/virtio/Kconfig | 7 ++++--- > > 1 file changed, 4 insertions(+), 3 deletions(-) > > My git-sendemail should have been broken. A list of receivers are > dropped automatically though they were explicitly specified, but > linux-arm-kernel@xxxxxxxxxxxxxxxxxxx was missed to be copied. > Fixing all of them through thunderbird :) > > Thanks, > Gavin Pls bounce the original patch to me so I can queue it. > > diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig > > index 34f80b7a8a64..74c8b0c7bc33 100644 > > --- a/drivers/virtio/Kconfig > > +++ b/drivers/virtio/Kconfig > > @@ -106,7 +106,7 @@ config VIRTIO_BALLOON > > config VIRTIO_MEM > > tristate "Virtio mem driver" > > default m > > - depends on X86_64 > > + depends on X86_64 || ARM64 > > depends on VIRTIO > > depends on MEMORY_HOTPLUG > > depends on MEMORY_HOTREMOVE > > @@ -116,8 +116,9 @@ 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, but should theoretically > > - work on all architectures that support memory hotplug and hotremove. > > + This driver was only tested under x86-64 and arm64, but should > > + theoretically work on all architectures that support memory hotplug > > + and hotremove. > > If unsure, say M. > > _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
