From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gavin Shan <gshan@redhat.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Shan Gavin <shan.gavin@gmail.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH v2] drivers/virtio: Enable virtio mem for ARM64
Date: Tue, 18 Jan 2022 11:05:29 -0500 [thread overview]
Message-ID: <20220118110512-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <2f0d1a5f-7e75-04b1-f2a1-f52385dae3b5@redhat.com>
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@redhat.com>
> > Acked-by: David Hildenbrand <david@redhat.com>
> > ---
> > 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@lists.infradead.org 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@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-01-18 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 8:48 [PATCH v2] drivers/virtio: Enable virtio mem for ARM64 Gavin Shan
2022-01-18 9:38 ` Gavin Shan
2022-01-18 16:05 ` Michael S. Tsirkin [this message]
2022-01-19 1:08 ` Gavin Shan
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=20220118110512-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=gshan@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=shan.gavin@gmail.com \
--cc=virtualization@lists.linux-foundation.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).