search for: mimu

...m.com> wrote: > > Are we > > worried that virtio data structures are going to be a burden on the 31-bit address space? > > > > > > That is a good question I can not answer. Since it is currently at least > a page per queue (because we use dma direct, right Mimu?), I am concerned > about this. > > Connie, what is your opinion? Yes, running into problems there was one of my motivations for my question. I guess it depends on the number of devices and how many queues they use. The problem is that it affects not only protected virt guests, but all g...

...m.com> wrote: > > Are we > > worried that virtio data structures are going to be a burden on the 31-bit address space? > > > > > > That is a good question I can not answer. Since it is currently at least > a page per queue (because we use dma direct, right Mimu?), I am concerned > about this. > > Connie, what is your opinion? Yes, running into problems there was one of my motivations for my question. I guess it depends on the number of devices and how many queues they use. The problem is that it affects not only protected virt guests, but all g...

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...

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...

On Wed, 29 May 2019 14:26:57 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > Hypervisor needs to interact with the summary indicators, so these > need to be DMA memory as well (at least for protected virtualization > guests). > > Signed-off-by: Halil Pasic <pasic at...

On Wed, 29 May 2019 14:26:55 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > This will come in handy soon when we pull out the indicators from > virtio_ccw_device to a memory area that is shared with the hypervisor > (in particular for protected virtualization guests). >...

On Wed, 29 May 2019 14:26:52 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > As virtio-ccw devices are channel devices, we need to use the dma area > for any communication with the hypervisor. "we need to use the dma area within the common I/O layer for any communication w...

On Wed, 29 May 2019 14:26:52 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > As virtio-ccw devices are channel devices, we need to use the dma area > for any communication with the hypervisor. "we need to use the dma area within the common I/O layer for any communication w...

On Mon, 3 Jun 2019 14:45:03 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > On 03.06.19 14:06, Cornelia Huck wrote: > > On Wed, 29 May 2019 14:26:52 +0200 > > Michael Mueller <mimu at linux.ibm.com> wrote: > >> @@ -1593,20 +1625,31 @@ struct ccw_device * __init ccw_device_create_console(struct ccw_driver *drv) &...

On Thu, 23 May 2019 18:22:09 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > Hypervisor needs to interact with the summary indicators, so these > need to be DMA memory as well (at least for protected virtualization > guests). > > Signed-off-by: Halil Pasic <pasic at...

On Thu, 23 May 2019 18:22:09 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > Hypervisor needs to interact with the summary indicators, so these > need to be DMA memory as well (at least for protected virtualization > guests). > > Signed-off-by: Halil Pasic <pasic at...

On Mon, 27 May 2019 14:30:14 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On Mon, 27 May 2019 12:38:02 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > On Thu, 23 May 2019 18:22:04 +0200 > > Michael Mueller <mimu at linux.ibm.com> wrote: > > > > > From: Halil Pasic <pasic at linux.ibm.com> > > > > > > As virtio-ccw devices are channel devices, we need to use the dma area > > > for any communication with the hypervisor. > > > > > > It...

On Mon, 27 May 2019 14:30:14 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > On Mon, 27 May 2019 12:38:02 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > > On Thu, 23 May 2019 18:22:04 +0200 > > Michael Mueller <mimu at linux.ibm.com> wrote: > > > > > From: Halil Pasic <pasic at linux.ibm.com> > > > > > > As virtio-ccw devices are channel devices, we need to use the dma area > > > for any communication with the hypervisor. > > > > > > It...

On Wed, 29 May 2019 14:26:53 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > Protected virtualization guests have to use shared pages for airq > notifier bit vectors, because hypervisor needs to write these bits. > > Let us make sure we allocate DMA memory for the notifie...

On Wed, 29 May 2019 14:26:53 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > Protected virtualization guests have to use shared pages for airq > notifier bit vectors, because hypervisor needs to write these bits. > > Let us make sure we allocate DMA memory for the notifie...

On Wed, 29 May 2019 14:26:56 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > Before virtio-ccw could get away with not using DMA API for the pieces of > memory it does ccw I/O with. With protected virtualization this has to > change, since the hypervisor needs to read and som...

On Wed, 29 May 2019 14:26:56 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > Before virtio-ccw could get away with not using DMA API for the pieces of > memory it does ccw I/O with. With protected virtualization this has to > change, since the hypervisor needs to read and som...

On Thu, 23 May 2019 18:22:04 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > As virtio-ccw devices are channel devices, we need to use the dma area > for any communication with the hypervisor. > > It handles neither QDIO in the common code, nor any device type specific &g...

On Thu, 23 May 2019 18:22:04 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > From: Halil Pasic <pasic at linux.ibm.com> > > As virtio-ccw devices are channel devices, we need to use the dma area > for any communication with the hypervisor. > > It handles neither QDIO in the common code, nor any device type specific &g...

On Mon, 3 Jun 2019 14:09:02 +0200 Michael Mueller <mimu at linux.ibm.com> wrote: > >> @@ -224,6 +226,8 @@ 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...