Re: [PATCH v1 00/14] s390x: virtio-mem support

2024-10-07 Thread David Hildenbrand
On 02.10.24 11:04, Janosch Frank wrote: On 10/1/24 10:54 AM, David Hildenbrand wrote: On 30.09.24 23:49, Halil Pasic wrote: On Fri, 27 Sep 2024 20:29:19 +0200 David Hildenbrand wrote: On 27.09.24 20:20, Halil Pasic wrote: On Wed, 11 Sep 2024 21:09:27 +0200 David Hildenbrand wrote: [...]

Re: [PATCH v1 00/14] s390x: virtio-mem support

2024-10-02 Thread Janosch Frank
On 10/1/24 10:54 AM, David Hildenbrand wrote: On 30.09.24 23:49, Halil Pasic wrote: On Fri, 27 Sep 2024 20:29:19 +0200 David Hildenbrand wrote: On 27.09.24 20:20, Halil Pasic wrote: On Wed, 11 Sep 2024 21:09:27 +0200 David Hildenbrand wrote: [...] That is a valid point. But IMHO the ben

Re: [PATCH v1 00/14] s390x: virtio-mem support

2024-10-01 Thread David Hildenbrand
On 30.09.24 23:49, Halil Pasic wrote: On Fri, 27 Sep 2024 20:29:19 +0200 David Hildenbrand wrote: On 27.09.24 20:20, Halil Pasic wrote: On Wed, 11 Sep 2024 21:09:27 +0200 David Hildenbrand wrote: Anyway, if we want to proceed with the gitlab project, would it make sense to create an org

Re: [PATCH v1 00/14] s390x: virtio-mem support

2024-09-30 Thread Halil Pasic
On Fri, 27 Sep 2024 20:29:19 +0200 David Hildenbrand wrote: > On 27.09.24 20:20, Halil Pasic wrote: > > On Wed, 11 Sep 2024 21:09:27 +0200 > > David Hildenbrand wrote: > > > >>> Anyway, if we want to proceed with the gitlab project, would it make > >>> sense to create an org for it, so that i

Re: [PATCH v1 00/14] s390x: virtio-mem support

2024-09-27 Thread David Hildenbrand
On 27.09.24 20:20, Halil Pasic wrote: On Wed, 11 Sep 2024 21:09:27 +0200 David Hildenbrand wrote: Anyway, if we want to proceed with the gitlab project, would it make sense to create an org for it, so that it doesn't look like David's personal project? Frankly, I would prefer making Document

Re: [PATCH v1 00/14] s390x: virtio-mem support

2024-09-27 Thread Halil Pasic
On Wed, 11 Sep 2024 21:09:27 +0200 David Hildenbrand wrote: > > Anyway, if we want to proceed with the gitlab project, would it make > > sense to create an org for it, so that it doesn't look like David's > > personal project? Frankly, I would prefer making Documentation/virt/kvm/s390/s390-diag.

Re: [PATCH v1 00/14] s390x: virtio-mem support

2024-09-11 Thread David Hildenbrand
On 11.09.24 17:38, Cornelia Huck wrote: On Wed, Sep 11 2024, "Michael S. Tsirkin" wrote: I'd rather have it in a shared and bigger repo than in your personal gitlab one. Maybe there's a space somewhere in QEMU or the Virtio team's repos that would be a good fit if the kernel's docu isn't the

Re: [PATCH v1 00/14] s390x: virtio-mem support

2024-09-11 Thread Cornelia Huck
On Wed, Sep 11 2024, "Michael S. Tsirkin" wrote: >> > >> > I'd rather have it in a shared and bigger repo than in your personal >> > gitlab one. Maybe there's a space somewhere in QEMU or the Virtio team's >> > repos that would be a good fit if the kernel's docu isn't the right place? >> >> At

Re: [PATCH v1 00/14] s390x: virtio-mem support

2024-09-11 Thread Michael S. Tsirkin
> > > > I'd rather have it in a shared and bigger repo than in your personal > > gitlab one. Maybe there's a space somewhere in QEMU or the Virtio team's > > repos that would be a good fit if the kernel's docu isn't the right place? > > At this point, outside of kernel/QEMU feels like the right t

Re: [PATCH v1 00/14] s390x: virtio-mem support

2024-09-11 Thread David Hildenbrand
On 11.09.24 13:49, Janosch Frank wrote: On 9/10/24 7:57 PM, David Hildenbrand wrote: This series introduces a new diag(500) "STORAGE LIMIT" subcode that will be documented at [2] once this+kernel part go upstream. Why not in Documentation/virt/kvm/s390/? s390-diag.rst is very similar already.

Re: [PATCH v1 00/14] s390x: virtio-mem support

2024-09-11 Thread Janosch Frank
On 9/10/24 7:57 PM, David Hildenbrand wrote: This series introduces a new diag(500) "STORAGE LIMIT" subcode that will be documented at [2] once this+kernel part go upstream. Why not in Documentation/virt/kvm/s390/? s390-diag.rst is very similar already. I'd rather have it in a shared and bigge

Re: [PATCH v1 00/14] s390x: virtio-mem support

2024-09-10 Thread David Hildenbrand
On 10.09.24 20:33, Michael S. Tsirkin wrote: On Tue, Sep 10, 2024 at 07:57:55PM +0200, David Hildenbrand wrote: This series is based on: [PATCH v2] virtio: kconfig: memory devices are PCI only [1] I finally found the time (IOW forced myself) to finish virtio-mem support on s390x. The last

Re: [PATCH v1 00/14] s390x: virtio-mem support

2024-09-10 Thread Michael S. Tsirkin
On Tue, Sep 10, 2024 at 07:57:55PM +0200, David Hildenbrand wrote: > This series is based on: > [PATCH v2] virtio: kconfig: memory devices are PCI only [1] > > I finally found the time (IOW forced myself) to finish virtio-mem > support on s390x. The last RFC was from 2020, so I won't talk abou

[PATCH v1 00/14] s390x: virtio-mem support

2024-09-10 Thread David Hildenbrand
This series is based on: [PATCH v2] virtio: kconfig: memory devices are PCI only [1] I finally found the time (IOW forced myself) to finish virtio-mem support on s390x. The last RFC was from 2020, so I won't talk about what changed -- a lot changed in the meantime :) There is really not much