Displaying 6 results from an estimated 6 matches for "char_0".
Did you mean:
char_
2019 May 27
2
[PATCH v2 3/8] s390/cio: add basic protected virtualization support
...on 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 8...
2019 May 27
2
[PATCH v2 3/8] s390/cio: add basic protected virtualization support
...on 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 8...
2019 May 27
0
[PATCH v2 3/8] s390/cio: add basic protected virtualization support
...> [Does basic recognition 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 0000...
2019 May 27
3
[PATCH v2 3/8] s390/cio: add basic protected virtualization support
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
2019 May 27
3
[PATCH v2 3/8] s390/cio: add basic protected virtualization support
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
2019 May 29
0
[PATCH v2 3/8] s390/cio: add basic protected virtualization support
...u 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 000...