search for: chpids

Handle the new CCW_CMD_SET_IND_ADAPTER command enabling adapter interrupts on guest request. When active, host->guest notifications will be handled via global_indicator -> queue indicators instead of queue indicators + subchannel I/O interrupt. Indicators for virtqueues may be present at an offset. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/s390x/css.c |

Handle the new CCW_CMD_SET_IND_ADAPTER command enabling adapter interrupts on guest request. When active, host->guest notifications will be handled via global_indicator -> queue indicators instead of queue indicators + subchannel I/O interrupt. Indicators for virtqueues may be present at an offset. Signed-off-by: Cornelia Huck <cornelia.huck at de.ibm.com> --- hw/s390x/css.c |

Hi, here's the qemu patch that implements the new adapter indicators ccw in virtio-ccw and injects adapter interrupts for the devices enabled for it. Cornelia Huck (1): s390/virtio-ccw: Adapter interrupt support. hw/s390x/css.c | 10 ++++++++ hw/s390x/css.h | 2 ++ hw/s390x/virtio-ccw.c | 66 ++++++++++++++++++++++++++++++++++++++++++++++++- hw/s390x/virtio-ccw.h |

Hi, here's the qemu patch that implements the new adapter indicators ccw in virtio-ccw and injects adapter interrupts for the devices enabled for it. Cornelia Huck (1): s390/virtio-ccw: Adapter interrupt support. hw/s390x/css.c | 10 ++++++++ hw/s390x/css.h | 2 ++ hw/s390x/virtio-ccw.c | 66 ++++++++++++++++++++++++++++++++++++++++++++++++- hw/s390x/virtio-ccw.h |

On Fri, 5 Apr 2019 01:16:15 +0200 Halil Pasic <pasic at linux.ibm.com> wrote: > Virtio-ccw relies on cio mechanisms for bootstrapping the ccw device. Well, a ccw device is, by definition, using cio mechanisms ;) Better say: "As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor." Or something like that. > Thus we

Hi, here's the current implementation of virtio-ccw adapter interrupts in qemu. Code is unchanged, only rebased against current master. Cornelia Huck (1): s390/virtio-ccw: Adapter interrupt support. hw/s390x/css.c | 10 ++++++++ hw/s390x/css.h | 2 ++ hw/s390x/virtio-ccw.c | 64 ++++++++++++++++++++++++++++++++++++++++++++++++- hw/s390x/virtio-ccw.h | 4 ++++

Hi, here's the current implementation of virtio-ccw adapter interrupts in qemu. Code is unchanged, only rebased against current master. Cornelia Huck (1): s390/virtio-ccw: Adapter interrupt support. hw/s390x/css.c | 10 ++++++++ hw/s390x/css.h | 2 ++ hw/s390x/virtio-ccw.c | 64 ++++++++++++++++++++++++++++++++++++++++++++++++- hw/s390x/virtio-ccw.h | 4 ++++

...path.] > > I've already had some thoughts along these lines and slapped > -device x-terminal3270,chardev=char_0,devno=fe.0.000a,id=terminal_0 \ > on my qemu command line. The ccw device does show up in the guest... > > Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs > ---------------------------------------------------------------------- > 0.0.0000 0.0.0000 0000/00 3832/01 yes 80 80 ff 00000000 00000000 > 0.0.000a 0.0.0001 0000/00 3270/00 80 80 ff 01000000 00000000 > 0.0.0002 0.0.0002 0000/00 3832/09 yes 80 80 ff 00000000 00...

...path.] > > I've already had some thoughts along these lines and slapped > -device x-terminal3270,chardev=char_0,devno=fe.0.000a,id=terminal_0 \ > on my qemu command line. The ccw device does show up in the guest... > > Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs > ---------------------------------------------------------------------- > 0.0.0000 0.0.0000 0000/00 3832/01 yes 80 80 ff 00000000 00000000 > 0.0.000a 0.0.0001 0000/00 3270/00 80 80 ff 01000000 00000000 > 0.0.0002 0.0.0002 0000/00 3832/09 yes 80 80 ff 00000000 00...

With this patch I can suspend/resume a KVM guest. [root at test ~]# cd /sys/power/ [root at test power]# echo test_resume > disk [root at test power]# lscss Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs ---------------------------------------------------------------------- 0.0.0003 0.0.0000 0000/00 3832/03 yes 80 80 ff 00000000 00000000 0.0.0000 0.0.0001 0000/00 3832/02 yes 80 80 ff 00000000 00000000 0.0.0001 0.0.0002 0000/00 3832/02 yes 80 80 ff 00000000 00000000 0.0....

With this patch I can suspend/resume a KVM guest. [root at test ~]# cd /sys/power/ [root at test power]# echo test_resume > disk [root at test power]# lscss Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs ---------------------------------------------------------------------- 0.0.0003 0.0.0000 0000/00 3832/03 yes 80 80 ff 00000000 00000000 0.0.0000 0.0.0001 0000/00 3832/02 yes 80 80 ff 00000000 00000000 0.0.0001 0.0.0002 0000/00 3832/02 yes 80 80 ff 00000000 00000000 0.0....

...uld at least exercise this code path.] I've already had some thoughts along these lines and slapped -device x-terminal3270,chardev=char_0,devno=fe.0.000a,id=terminal_0 \ on my qemu command line. The ccw device does show up in the guest... Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs ---------------------------------------------------------------------- 0.0.0000 0.0.0000 0000/00 3832/01 yes 80 80 ff 00000000 00000000 0.0.000a 0.0.0001 0000/00 3270/00 80 80 ff 01000000 00000000 0.0.0002 0.0.0002 0000/00 3832/09 yes 80 80 ff 00000000 00000000 0.0.0300 0.0...

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 > stuff (like channel programs

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 > stuff (like channel programs

...t;> I've already had some thoughts along these lines and slapped >> -device x-terminal3270,chardev=char_0,devno=fe.0.000a,id=terminal_0 \ >> on my qemu command line. The ccw device does show up in the guest... >> >> Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs >> ---------------------------------------------------------------------- >> 0.0.0000 0.0.0000 0000/00 3832/01 yes 80 80 ff 00000000 00000000 >> 0.0.000a 0.0.0001 0000/00 3270/00 80 80 ff 01000000 00000000 >> 0.0.0002 0.0.0002 0000/00 3832/09 yes 80 80 ff...

As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor. This patch addresses the most basic stuff (mostly what is required for virtio-ccw), and does take care of QDIO or any devices. An interesting side effect is that virtio structures are now going to get allocated in 31 bit addressable storage. Signed-off-by: Halil Pasic <pasic at

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 stuff (like channel programs constructed by the DASD driver). An interesting side effect is that virtio structures are now going to get allocated in 31 bit

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 stuff (like channel programs constructed by the DASD driver). An interesting side effect is that virtio structures are now going to get allocated in 31 bit

As virtio-ccw devices are channel devices, we need to use the dma area within the common I/O layer for any communication with the hypervisor. Note that we do not need to use that area for control blocks directly referenced by instructions, e.g. the orb. It handles neither QDIO in the common code, nor any device type specific stuff (like channel programs constructed by the DASD driver). An

Enhanced virtualization protection technology may require the use of bounce buffers for I/O. While support for this was built into the virtio core, virtio-ccw wasn't changed accordingly. Some background on technology (not part of this series) and the terminology used. * Protected Virtualization (PV): Protected Virtualization guarantees, that non-shared memory of a guest that operates in PV