Re: [Xen-devel] [PATCH v2] xen/blkfront: fix ring info addressing

2020-03-05 Thread Sander Eikelenboom
On 05/03/2020 14:40, Jürgen Groß wrote: > On 05.03.20 13:42, Roger Pau Monné wrote: >> On Thu, Mar 05, 2020 at 12:40:44PM +0100, Juergen Gross wrote: >>> Commit 0265d6e8ddb890 ("xen/blkfront: limit allocated memory size to >>> actual use case") made struct blkfront_ring_info size dynamic. This is >

Re: [Xen-devel] [PATCH v2] xen/blkfront: fix ring info addressing

2020-03-05 Thread Jürgen Groß
On 05.03.20 13:42, Roger Pau Monné wrote: On Thu, Mar 05, 2020 at 12:40:44PM +0100, Juergen Gross wrote: Commit 0265d6e8ddb890 ("xen/blkfront: limit allocated memory size to actual use case") made struct blkfront_ring_info size dynamic. This is fine when running with only one queue, but with mul

Re: [Xen-devel] [PATCH v2] xen/blkfront: fix ring info addressing

2020-03-05 Thread Roger Pau Monné
On Thu, Mar 05, 2020 at 12:40:44PM +0100, Juergen Gross wrote: > Commit 0265d6e8ddb890 ("xen/blkfront: limit allocated memory size to > actual use case") made struct blkfront_ring_info size dynamic. This is > fine when running with only one queue, but with multiple queues the > addressing of the si

[Xen-devel] [PATCH v2] xen/blkfront: fix ring info addressing

2020-03-05 Thread Juergen Gross
Commit 0265d6e8ddb890 ("xen/blkfront: limit allocated memory size to actual use case") made struct blkfront_ring_info size dynamic. This is fine when running with only one queue, but with multiple queues the addressing of the single queues has to be adapted as the structs are allocated in an array.