similar to: [RFC PATCH 04/12] s390/cio: introduce cio DMA pool

On Fri, 12 Apr 2019, Halil Pasic wrote: > On Thu, 11 Apr 2019 20:25:01 +0200 (CEST) > Sebastian Ott <sebott at linux.ibm.com> wrote: > > I don't think we should use this global DMA pool. I guess it's OK for > > stuff like airq (where we don't have a struct device at hand) but for > > CCW we should use the device we have. Yes, this way we waste some memory

On Fri, 10 May 2019 16:10:13 +0200 Cornelia Huck <cohuck at redhat.com> wrote: > On Fri, 10 May 2019 00:11:12 +0200 > Halil Pasic <pasic at linux.ibm.com> wrote: > > > On Thu, 9 May 2019 12:11:06 +0200 > > Cornelia Huck <cohuck at redhat.com> wrote: > > > > > On Wed, 8 May 2019 23:22:10 +0200 > > > Halil Pasic <pasic at

On Mon, 13 May 2019 15:29:24 +0200 Cornelia Huck <cohuck at redhat.com> wrote: > On Sun, 12 May 2019 20:22:56 +0200 > Halil Pasic <pasic at linux.ibm.com> wrote: > > > On Fri, 10 May 2019 16:10:13 +0200 > > Cornelia Huck <cohuck at redhat.com> wrote: > > > > > On Fri, 10 May 2019 00:11:12 +0200 > > > Halil Pasic <pasic at

On Fri, 12 Apr 2019, Halil Pasic wrote: > On Fri, 12 Apr 2019 14:12:31 +0200 (CEST) > Sebastian Ott <sebott at linux.ibm.com> wrote: > > On Fri, 12 Apr 2019, Halil Pasic wrote: > > > On Thu, 11 Apr 2019 20:25:01 +0200 (CEST) > > > Sebastian Ott <sebott at linux.ibm.com> wrote: > > > > I don't think we should use this global DMA pool. I

On Sun, 12 May 2019 20:22:56 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On Fri, 10 May 2019 16:10:13 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > On Fri, 10 May 2019 00:11:12 +0200 > > Halil Pasic <pasic at linux.ibm.com> wrote: > > > > > On Thu, 9 May 2019 12:11:06 +0200 > > > Cornelia Huck <cohuck at

On Sun, 12 May 2019 20:22:56 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On Fri, 10 May 2019 16:10:13 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > On Fri, 10 May 2019 00:11:12 +0200 > > Halil Pasic <pasic at linux.ibm.com> wrote: > > > > > On Thu, 9 May 2019 12:11:06 +0200 > > > Cornelia Huck <cohuck at

On Fri, 5 Apr 2019 01:16:14 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > To support protected virtualization cio will need to make sure the > memory used for communication with the hypervisor is DMA memory. > > Let us introduce a DMA pool to cio that will help us in allocating missing 'and' > deallocating those chunks of memory. > > We use a gen_pool

On 03.06.19 13:37, Cornelia Huck wrote: > On Wed, 29 May 2019 14:26:51 +0200 > Michael Mueller <mimu at linux.ibm.com> wrote: > >> From: Halil Pasic <pasic at linux.ibm.com> >> >> To support protected virtualization cio will need to make sure the >> memory used for communication with the hypervisor is DMA memory. >> >> Let us introduce one

From: Halil Pasic <pasic at linux.ibm.com> To support protected virtualization cio will need to make sure the memory used for communication with the hypervisor is DMA memory. Let us introduce one global pool for cio. Our DMA pools are implemented as a gen_pool backed with DMA pages. The idea is to avoid each allocation effectively wasting a page, as we typically allocate much less than

On Fri, 26 Apr 2019, Halil Pasic wrote: > @@ -224,6 +228,9 @@ struct subchannel *css_alloc_subchannel(struct subchannel_id schid, > INIT_WORK(&sch->todo_work, css_sch_todo); > sch->dev.release = &css_subchannel_release; > device_initialize(&sch->dev); > + sch->dma_mask = css_dev_dma_mask; > + sch->dev.dma_mask = &sch->dma_mask; > +

On Fri, 26 Apr 2019, Halil Pasic wrote: > @@ -224,6 +228,9 @@ struct subchannel *css_alloc_subchannel(struct subchannel_id schid, > INIT_WORK(&sch->todo_work, css_sch_todo); > sch->dev.release = &css_subchannel_release; > device_initialize(&sch->dev); > + sch->dma_mask = css_dev_dma_mask; > + sch->dev.dma_mask = &sch->dma_mask; > +

On Mon, 3 Jun 2019 13:37:45 +0200 Cornelia Huck <cohuck at redhat.com> wrote: > On Wed, 29 May 2019 14:26:51 +0200 > Michael Mueller <mimu at linux.ibm.com> wrote: > > > From: Halil Pasic <pasic at linux.ibm.com> > > > > To support protected virtualization cio will need to make sure the > > memory used for communication with the hypervisor is

On Tue, 11 Jun 2019 18:19:44 +0200 Cornelia Huck <cohuck at redhat.com> wrote: > On Tue, 11 Jun 2019 16:27:21 +0200 > Halil Pasic <pasic at linux.ibm.com> wrote: > > > On Tue, 11 Jun 2019 12:17:21 +0200 > > Cornelia Huck <cohuck at redhat.com> wrote: > > > > > On Thu, 6 Jun 2019 13:51:23 +0200 > > > Halil Pasic <pasic at

On Mon, 20 May 2019, Halil Pasic wrote: > On Thu, 16 May 2019 15:59:22 +0200 (CEST) > Sebastian Ott <sebott at linux.ibm.com> wrote: > > We only have a couple of users for airq_iv: > > > > virtio_ccw.c: 2K bits > > You mean a single allocation is 2k bits (VIRTIO_IV_BITS = 256 * 8)? My > understanding is that the upper bound is more like: > MAX_AIRQ_AREAS

To support protected virtualization cio will need to make sure the memory used for communication with the hypervisor is DMA memory. Let us introduce one global pool for cio. Our DMA pools are implemented as a gen_pool backed with DMA pages. The idea is to avoid each allocation effectively wasting a page, as we typically allocate much less than PAGE_SIZE. Signed-off-by: Halil Pasic <pasic at

To support protected virtualization cio will need to make sure the memory used for communication with the hypervisor is DMA memory. Let us introduce one global pool for cio. Our DMA pools are implemented as a gen_pool backed with DMA pages. The idea is to avoid each allocation effectively wasting a page, as we typically allocate much less than PAGE_SIZE. Signed-off-by: Halil Pasic <pasic at

On Wed, 29 May 2019 14:26:51 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > To support protected virtualization cio will need to make sure the > memory used for communication with the hypervisor is DMA memory. > > Let us introduce one global pool for cio. > > Our DMA pools are implemented as a gen_pool

On Wed, 29 May 2019 14:26:51 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > To support protected virtualization cio will need to make sure the > memory used for communication with the hypervisor is DMA memory. > > Let us introduce one global pool for cio. > > Our DMA pools are implemented as a gen_pool

From: Halil Pasic <pasic at linux.ibm.com> To support protected virtualization cio will need to make sure the memory used for communication with the hypervisor is DMA memory. Let us introduce one global cio, and some tools for pools seated at individual devices. Our DMA pools are implemented as a gen_pool backed with DMA pages. The idea is to avoid each allocation effectively wasting a

On Mon, 27 May 2019 08:57:18 +0200 Cornelia Huck <cohuck at redhat.com> wrote: > On Thu, 23 May 2019 18:22:03 +0200 > Michael Mueller <mimu at linux.ibm.com> wrote: > > > From: Halil Pasic <pasic at linux.ibm.com> > > > > To support protected virtualization cio will need to make sure the > > memory used for communication with the hypervisor is