search for: terminal_0

...tected virt guest with a > > 3270 console? I realize that the console is unlikely to work, but that > > should 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...

...tected virt guest with a > > 3270 console? I realize that the console is unlikely to work, but that > > should 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...

...ion work if you start a protected virt guest with a > 3270 console? I realize that the console is unlikely to work, but that > should 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/...

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

...uest with a >>> 3270 console? I realize that the console is unlikely to work, but that >>> should 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...

Hi, I''ve tried several different approaches to debootstrap a working rootfs for with a Cortex A15 model ( FastModels ) and Xen but still face some issues. Some information on my setup. For a Dom0 kernel I''m using the latest version from git://github.com/torvalds/linux.git, I attached my config as it might be of some use for others. I''m using the latest Xen unstable