* [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 @ 2022-01-19 1:05 ` Gavin Shan 0 siblings, 0 replies; 16+ messages in thread From: Gavin Shan @ 2022-01-19 1:05 UTC (permalink / raw) To: virtualization; +Cc: Jonathan.Cameron, mst, shan.gavin, linux-arm-kernel 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> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> Acked-by: Michael S. Tsirkin <mst@redhat.com> --- v3: Pick ack-by tags from Jonathan and Michael --- drivers/virtio/Kconfig | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) 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. -- 2.23.0 _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization ^ permalink raw reply related [flat|nested] 16+ messages in thread
* [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 @ 2022-01-19 1:05 ` Gavin Shan 0 siblings, 0 replies; 16+ messages in thread From: Gavin Shan @ 2022-01-19 1:05 UTC (permalink / raw) To: virtualization; +Cc: linux-arm-kernel, david, Jonathan.Cameron, mst, shan.gavin 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> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> Acked-by: Michael S. Tsirkin <mst@redhat.com> --- v3: Pick ack-by tags from Jonathan and Michael --- drivers/virtio/Kconfig | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) 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. -- 2.23.0 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply related [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 2022-01-19 1:05 ` Gavin Shan @ 2022-01-19 7:39 ` Michael S. Tsirkin -1 siblings, 0 replies; 16+ messages in thread From: Michael S. Tsirkin @ 2022-01-19 7:39 UTC (permalink / raw) To: Gavin Shan; +Cc: Jonathan.Cameron, shan.gavin, linux-arm-kernel, virtualization On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> > Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> > Acked-by: Michael S. Tsirkin <mst@redhat.com> > --- > v3: Pick ack-by tags from Jonathan and Michael > --- > drivers/virtio/Kconfig | 7 ++++--- > 1 file changed, 4 insertions(+), 3 deletions(-) > > 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. > BTW isn't there a symbol saying "memory hotplug" that we can depend on? > If unsure, say M. > > -- > 2.23.0 _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 @ 2022-01-19 7:39 ` Michael S. Tsirkin 0 siblings, 0 replies; 16+ messages in thread From: Michael S. Tsirkin @ 2022-01-19 7:39 UTC (permalink / raw) To: Gavin Shan Cc: virtualization, linux-arm-kernel, david, Jonathan.Cameron, shan.gavin On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> > Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> > Acked-by: Michael S. Tsirkin <mst@redhat.com> > --- > v3: Pick ack-by tags from Jonathan and Michael > --- > drivers/virtio/Kconfig | 7 ++++--- > 1 file changed, 4 insertions(+), 3 deletions(-) > > 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. > BTW isn't there a symbol saying "memory hotplug" that we can depend on? > If unsure, say M. > > -- > 2.23.0 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 2022-01-19 7:39 ` Michael S. Tsirkin @ 2022-01-19 7:46 ` Gavin Shan -1 siblings, 0 replies; 16+ messages in thread From: Gavin Shan @ 2022-01-19 7:46 UTC (permalink / raw) To: Michael S. Tsirkin Cc: Jonathan.Cameron, shan.gavin, linux-arm-kernel, virtualization Hi Michael, On 1/19/22 3:39 PM, Michael S. Tsirkin wrote: > On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> >> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> >> Acked-by: Michael S. Tsirkin <mst@redhat.com> >> --- >> v3: Pick ack-by tags from Jonathan and Michael >> --- >> drivers/virtio/Kconfig | 7 ++++--- >> 1 file changed, 4 insertions(+), 3 deletions(-) >> >> 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. >> > > BTW isn't there a symbol saying "memory hotplug" that we can depend on? > You mean to change it like below? Actually, both looks good to me :) + This driver was only tested under x86-64 and arm64, but should + theoretically work on all architectures. >> If unsure, say M. >> Thanks, Gavin _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 @ 2022-01-19 7:46 ` Gavin Shan 0 siblings, 0 replies; 16+ messages in thread From: Gavin Shan @ 2022-01-19 7:46 UTC (permalink / raw) To: Michael S. Tsirkin Cc: virtualization, linux-arm-kernel, david, Jonathan.Cameron, shan.gavin Hi Michael, On 1/19/22 3:39 PM, Michael S. Tsirkin wrote: > On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> >> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> >> Acked-by: Michael S. Tsirkin <mst@redhat.com> >> --- >> v3: Pick ack-by tags from Jonathan and Michael >> --- >> drivers/virtio/Kconfig | 7 ++++--- >> 1 file changed, 4 insertions(+), 3 deletions(-) >> >> 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. >> > > BTW isn't there a symbol saying "memory hotplug" that we can depend on? > You mean to change it like below? Actually, both looks good to me :) + This driver was only tested under x86-64 and arm64, but should + theoretically work on all architectures. >> If unsure, say M. >> Thanks, Gavin _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 2022-01-19 7:46 ` Gavin Shan @ 2022-01-19 8:35 ` David Hildenbrand -1 siblings, 0 replies; 16+ messages in thread From: David Hildenbrand @ 2022-01-19 8:35 UTC (permalink / raw) To: Gavin Shan, Michael S. Tsirkin Cc: Jonathan.Cameron, shan.gavin, linux-arm-kernel, virtualization On 19.01.22 08:46, Gavin Shan wrote: > Hi Michael, > > On 1/19/22 3:39 PM, Michael S. Tsirkin wrote: >> On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> >>> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> >>> Acked-by: Michael S. Tsirkin <mst@redhat.com> >>> --- >>> v3: Pick ack-by tags from Jonathan and Michael >>> --- >>> drivers/virtio/Kconfig | 7 ++++--- >>> 1 file changed, 4 insertions(+), 3 deletions(-) >>> >>> 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. >>> >> >> BTW isn't there a symbol saying "memory hotplug" that we can depend on? >> You mean depends on MEMORY_HOTPLUG depends on MEMORY_HOTREMOVE We still need a manual opt-in from architectures, because devil's in the detail. (e.g., memblock stuff we had to adjust) -- Thanks, David / dhildenb _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 @ 2022-01-19 8:35 ` David Hildenbrand 0 siblings, 0 replies; 16+ messages in thread From: David Hildenbrand @ 2022-01-19 8:35 UTC (permalink / raw) To: Gavin Shan, Michael S. Tsirkin Cc: virtualization, linux-arm-kernel, Jonathan.Cameron, shan.gavin On 19.01.22 08:46, Gavin Shan wrote: > Hi Michael, > > On 1/19/22 3:39 PM, Michael S. Tsirkin wrote: >> On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> >>> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> >>> Acked-by: Michael S. Tsirkin <mst@redhat.com> >>> --- >>> v3: Pick ack-by tags from Jonathan and Michael >>> --- >>> drivers/virtio/Kconfig | 7 ++++--- >>> 1 file changed, 4 insertions(+), 3 deletions(-) >>> >>> 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. >>> >> >> BTW isn't there a symbol saying "memory hotplug" that we can depend on? >> You mean depends on MEMORY_HOTPLUG depends on MEMORY_HOTREMOVE We still need a manual opt-in from architectures, because devil's in the detail. (e.g., memblock stuff we had to adjust) -- Thanks, David / dhildenb _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 2022-01-19 8:35 ` David Hildenbrand @ 2022-02-04 13:24 ` Michael S. Tsirkin -1 siblings, 0 replies; 16+ messages in thread From: Michael S. Tsirkin @ 2022-02-04 13:24 UTC (permalink / raw) To: David Hildenbrand Cc: Jonathan.Cameron, shan.gavin, linux-arm-kernel, virtualization On Wed, Jan 19, 2022 at 09:35:05AM +0100, David Hildenbrand wrote: > On 19.01.22 08:46, Gavin Shan wrote: > > Hi Michael, > > > > On 1/19/22 3:39 PM, Michael S. Tsirkin wrote: > >> On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> > >>> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> > >>> Acked-by: Michael S. Tsirkin <mst@redhat.com> > >>> --- > >>> v3: Pick ack-by tags from Jonathan and Michael > >>> --- > >>> drivers/virtio/Kconfig | 7 ++++--- > >>> 1 file changed, 4 insertions(+), 3 deletions(-) > >>> > >>> 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. > >>> > >> > >> BTW isn't there a symbol saying "memory hotplug" that we can depend on? > >> > > You mean > > depends on MEMORY_HOTPLUG > depends on MEMORY_HOTREMOVE > > We still need a manual opt-in from architectures, because devil's in the > detail. (e.g., memblock stuff we had to adjust) Is there any chance of documenting some of this here? The current comment makes it look like it's just a question of whitelisting an architecture. > -- > Thanks, > > David / dhildenb _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 @ 2022-02-04 13:24 ` Michael S. Tsirkin 0 siblings, 0 replies; 16+ messages in thread From: Michael S. Tsirkin @ 2022-02-04 13:24 UTC (permalink / raw) To: David Hildenbrand Cc: Gavin Shan, virtualization, linux-arm-kernel, Jonathan.Cameron, shan.gavin On Wed, Jan 19, 2022 at 09:35:05AM +0100, David Hildenbrand wrote: > On 19.01.22 08:46, Gavin Shan wrote: > > Hi Michael, > > > > On 1/19/22 3:39 PM, Michael S. Tsirkin wrote: > >> On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> > >>> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> > >>> Acked-by: Michael S. Tsirkin <mst@redhat.com> > >>> --- > >>> v3: Pick ack-by tags from Jonathan and Michael > >>> --- > >>> drivers/virtio/Kconfig | 7 ++++--- > >>> 1 file changed, 4 insertions(+), 3 deletions(-) > >>> > >>> 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. > >>> > >> > >> BTW isn't there a symbol saying "memory hotplug" that we can depend on? > >> > > You mean > > depends on MEMORY_HOTPLUG > depends on MEMORY_HOTREMOVE > > We still need a manual opt-in from architectures, because devil's in the > detail. (e.g., memblock stuff we had to adjust) Is there any chance of documenting some of this here? The current comment makes it look like it's just a question of whitelisting an architecture. > -- > Thanks, > > David / dhildenb _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 2022-02-04 13:24 ` Michael S. Tsirkin @ 2022-02-04 13:29 ` David Hildenbrand -1 siblings, 0 replies; 16+ messages in thread From: David Hildenbrand @ 2022-02-04 13:29 UTC (permalink / raw) To: Michael S. Tsirkin Cc: Jonathan.Cameron, shan.gavin, linux-arm-kernel, virtualization On 04.02.22 14:24, Michael S. Tsirkin wrote: > On Wed, Jan 19, 2022 at 09:35:05AM +0100, David Hildenbrand wrote: >> On 19.01.22 08:46, Gavin Shan wrote: >>> Hi Michael, >>> >>> On 1/19/22 3:39 PM, Michael S. Tsirkin wrote: >>>> On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> >>>>> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> >>>>> Acked-by: Michael S. Tsirkin <mst@redhat.com> >>>>> --- >>>>> v3: Pick ack-by tags from Jonathan and Michael >>>>> --- >>>>> drivers/virtio/Kconfig | 7 ++++--- >>>>> 1 file changed, 4 insertions(+), 3 deletions(-) >>>>> >>>>> 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. >>>>> >>>> >>>> BTW isn't there a symbol saying "memory hotplug" that we can depend on? >>>> >> >> You mean >> >> depends on MEMORY_HOTPLUG >> depends on MEMORY_HOTREMOVE >> >> We still need a manual opt-in from architectures, because devil's in the >> detail. (e.g., memblock stuff we had to adjust) > > Is there any chance of documenting some of this here? The current comment makes it > look like it's just a question of whitelisting an architecture. I can send a patch to add more details. -- Thanks, David / dhildenb _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 @ 2022-02-04 13:29 ` David Hildenbrand 0 siblings, 0 replies; 16+ messages in thread From: David Hildenbrand @ 2022-02-04 13:29 UTC (permalink / raw) To: Michael S. Tsirkin Cc: Gavin Shan, virtualization, linux-arm-kernel, Jonathan.Cameron, shan.gavin On 04.02.22 14:24, Michael S. Tsirkin wrote: > On Wed, Jan 19, 2022 at 09:35:05AM +0100, David Hildenbrand wrote: >> On 19.01.22 08:46, Gavin Shan wrote: >>> Hi Michael, >>> >>> On 1/19/22 3:39 PM, Michael S. Tsirkin wrote: >>>> On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> >>>>> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> >>>>> Acked-by: Michael S. Tsirkin <mst@redhat.com> >>>>> --- >>>>> v3: Pick ack-by tags from Jonathan and Michael >>>>> --- >>>>> drivers/virtio/Kconfig | 7 ++++--- >>>>> 1 file changed, 4 insertions(+), 3 deletions(-) >>>>> >>>>> 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. >>>>> >>>> >>>> BTW isn't there a symbol saying "memory hotplug" that we can depend on? >>>> >> >> You mean >> >> depends on MEMORY_HOTPLUG >> depends on MEMORY_HOTREMOVE >> >> We still need a manual opt-in from architectures, because devil's in the >> detail. (e.g., memblock stuff we had to adjust) > > Is there any chance of documenting some of this here? The current comment makes it > look like it's just a question of whitelisting an architecture. I can send a patch to add more details. -- Thanks, David / dhildenb _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 2022-02-04 13:29 ` David Hildenbrand @ 2022-02-04 14:04 ` Michael S. Tsirkin -1 siblings, 0 replies; 16+ messages in thread From: Michael S. Tsirkin @ 2022-02-04 14:04 UTC (permalink / raw) To: David Hildenbrand Cc: Jonathan.Cameron, shan.gavin, linux-arm-kernel, virtualization On Fri, Feb 04, 2022 at 02:29:39PM +0100, David Hildenbrand wrote: > On 04.02.22 14:24, Michael S. Tsirkin wrote: > > On Wed, Jan 19, 2022 at 09:35:05AM +0100, David Hildenbrand wrote: > >> On 19.01.22 08:46, Gavin Shan wrote: > >>> Hi Michael, > >>> > >>> On 1/19/22 3:39 PM, Michael S. Tsirkin wrote: > >>>> On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> > >>>>> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> > >>>>> Acked-by: Michael S. Tsirkin <mst@redhat.com> > >>>>> --- > >>>>> v3: Pick ack-by tags from Jonathan and Michael > >>>>> --- > >>>>> drivers/virtio/Kconfig | 7 ++++--- > >>>>> 1 file changed, 4 insertions(+), 3 deletions(-) > >>>>> > >>>>> 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. > >>>>> > >>>> > >>>> BTW isn't there a symbol saying "memory hotplug" that we can depend on? > >>>> > >> > >> You mean > >> > >> depends on MEMORY_HOTPLUG > >> depends on MEMORY_HOTREMOVE > >> > >> We still need a manual opt-in from architectures, because devil's in the > >> detail. (e.g., memblock stuff we had to adjust) > > > > Is there any chance of documenting some of this here? The current comment makes it > > look like it's just a question of whitelisting an architecture. > > I can send a patch to add more details. oks so that will be a patch on top? > -- > Thanks, > > David / dhildenb _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 @ 2022-02-04 14:04 ` Michael S. Tsirkin 0 siblings, 0 replies; 16+ messages in thread From: Michael S. Tsirkin @ 2022-02-04 14:04 UTC (permalink / raw) To: David Hildenbrand Cc: Gavin Shan, virtualization, linux-arm-kernel, Jonathan.Cameron, shan.gavin On Fri, Feb 04, 2022 at 02:29:39PM +0100, David Hildenbrand wrote: > On 04.02.22 14:24, Michael S. Tsirkin wrote: > > On Wed, Jan 19, 2022 at 09:35:05AM +0100, David Hildenbrand wrote: > >> On 19.01.22 08:46, Gavin Shan wrote: > >>> Hi Michael, > >>> > >>> On 1/19/22 3:39 PM, Michael S. Tsirkin wrote: > >>>> On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> > >>>>> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> > >>>>> Acked-by: Michael S. Tsirkin <mst@redhat.com> > >>>>> --- > >>>>> v3: Pick ack-by tags from Jonathan and Michael > >>>>> --- > >>>>> drivers/virtio/Kconfig | 7 ++++--- > >>>>> 1 file changed, 4 insertions(+), 3 deletions(-) > >>>>> > >>>>> 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. > >>>>> > >>>> > >>>> BTW isn't there a symbol saying "memory hotplug" that we can depend on? > >>>> > >> > >> You mean > >> > >> depends on MEMORY_HOTPLUG > >> depends on MEMORY_HOTREMOVE > >> > >> We still need a manual opt-in from architectures, because devil's in the > >> detail. (e.g., memblock stuff we had to adjust) > > > > Is there any chance of documenting some of this here? The current comment makes it > > look like it's just a question of whitelisting an architecture. > > I can send a patch to add more details. oks so that will be a patch on top? > -- > Thanks, > > David / dhildenb _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 2022-02-04 14:04 ` Michael S. Tsirkin @ 2022-02-04 14:25 ` David Hildenbrand -1 siblings, 0 replies; 16+ messages in thread From: David Hildenbrand @ 2022-02-04 14:25 UTC (permalink / raw) To: Michael S. Tsirkin Cc: Jonathan.Cameron, shan.gavin, linux-arm-kernel, virtualization On 04.02.22 15:04, Michael S. Tsirkin wrote: > On Fri, Feb 04, 2022 at 02:29:39PM +0100, David Hildenbrand wrote: >> On 04.02.22 14:24, Michael S. Tsirkin wrote: >>> On Wed, Jan 19, 2022 at 09:35:05AM +0100, David Hildenbrand wrote: >>>> On 19.01.22 08:46, Gavin Shan wrote: >>>>> Hi Michael, >>>>> >>>>> On 1/19/22 3:39 PM, Michael S. Tsirkin wrote: >>>>>> On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> >>>>>>> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> >>>>>>> Acked-by: Michael S. Tsirkin <mst@redhat.com> >>>>>>> --- >>>>>>> v3: Pick ack-by tags from Jonathan and Michael >>>>>>> --- >>>>>>> drivers/virtio/Kconfig | 7 ++++--- >>>>>>> 1 file changed, 4 insertions(+), 3 deletions(-) >>>>>>> >>>>>>> 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. >>>>>>> >>>>>> >>>>>> BTW isn't there a symbol saying "memory hotplug" that we can depend on? >>>>>> >>>> >>>> You mean >>>> >>>> depends on MEMORY_HOTPLUG >>>> depends on MEMORY_HOTREMOVE >>>> >>>> We still need a manual opt-in from architectures, because devil's in the >>>> detail. (e.g., memblock stuff we had to adjust) >>> >>> Is there any chance of documenting some of this here? The current comment makes it >>> look like it's just a question of whitelisting an architecture. >> >> I can send a patch to add more details. > > oks so that will be a patch on top? Yes, it's independent of arm64 support. -- Thanks, David / dhildenb _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 @ 2022-02-04 14:25 ` David Hildenbrand 0 siblings, 0 replies; 16+ messages in thread From: David Hildenbrand @ 2022-02-04 14:25 UTC (permalink / raw) To: Michael S. Tsirkin Cc: Gavin Shan, virtualization, linux-arm-kernel, Jonathan.Cameron, shan.gavin On 04.02.22 15:04, Michael S. Tsirkin wrote: > On Fri, Feb 04, 2022 at 02:29:39PM +0100, David Hildenbrand wrote: >> On 04.02.22 14:24, Michael S. Tsirkin wrote: >>> On Wed, Jan 19, 2022 at 09:35:05AM +0100, David Hildenbrand wrote: >>>> On 19.01.22 08:46, Gavin Shan wrote: >>>>> Hi Michael, >>>>> >>>>> On 1/19/22 3:39 PM, Michael S. Tsirkin wrote: >>>>>> On Wed, Jan 19, 2022 at 09:05:51AM +0800, 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> >>>>>>> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> >>>>>>> Acked-by: Michael S. Tsirkin <mst@redhat.com> >>>>>>> --- >>>>>>> v3: Pick ack-by tags from Jonathan and Michael >>>>>>> --- >>>>>>> drivers/virtio/Kconfig | 7 ++++--- >>>>>>> 1 file changed, 4 insertions(+), 3 deletions(-) >>>>>>> >>>>>>> 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. >>>>>>> >>>>>> >>>>>> BTW isn't there a symbol saying "memory hotplug" that we can depend on? >>>>>> >>>> >>>> You mean >>>> >>>> depends on MEMORY_HOTPLUG >>>> depends on MEMORY_HOTREMOVE >>>> >>>> We still need a manual opt-in from architectures, because devil's in the >>>> detail. (e.g., memblock stuff we had to adjust) >>> >>> Is there any chance of documenting some of this here? The current comment makes it >>> look like it's just a question of whitelisting an architecture. >> >> I can send a patch to add more details. > > oks so that will be a patch on top? Yes, it's independent of arm64 support. -- Thanks, David / dhildenb _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2022-02-04 14:26 UTC | newest] Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-01-19 1:05 [PATCH v3] drivers/virtio: Enable virtio mem for ARM64 Gavin Shan 2022-01-19 1:05 ` Gavin Shan 2022-01-19 7:39 ` Michael S. Tsirkin 2022-01-19 7:39 ` Michael S. Tsirkin 2022-01-19 7:46 ` Gavin Shan 2022-01-19 7:46 ` Gavin Shan 2022-01-19 8:35 ` David Hildenbrand 2022-01-19 8:35 ` David Hildenbrand 2022-02-04 13:24 ` Michael S. Tsirkin 2022-02-04 13:24 ` Michael S. Tsirkin 2022-02-04 13:29 ` David Hildenbrand 2022-02-04 13:29 ` David Hildenbrand 2022-02-04 14:04 ` Michael S. Tsirkin 2022-02-04 14:04 ` Michael S. Tsirkin 2022-02-04 14:25 ` David Hildenbrand 2022-02-04 14:25 ` David Hildenbrand
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.