qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Farhan Ali <alifm@linux.vnet.ibm.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: borntraeger@de.ibm.com, cohuck@redhat.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v1 0/2] Virtio GPU for S390
Date: Wed, 13 Sep 2017 15:11:06 -0400	[thread overview]
Message-ID: <f321fb90-cd47-0b63-dbd5-87d825bc3288@linux.vnet.ibm.com> (raw)
In-Reply-To: <edda99a2-37b3-7428-027c-18f27a315056@redhat.com>



On 09/13/2017 03:00 PM, Thomas Huth wrote:
> On 12.09.2017 16:26, Farhan Ali wrote:
>> These patches wire up the virtio-gpu device for CCW bus for S390.
>>
>> For the S390 architecture which does not natively support any
>> graphics device, virtio gpu in 2D mode could be used to emulate a
>> simple graphics card and use VNC as the display.
>>
>> eg: qemu-system-s390x ... -device virtio-gpu-ccw,devno=fe.0.0101
>> -vnc host_ip_addr:5900
>>
>> Note, to actually see any display content the guest kernel needs to
>> support DRM layer, Virtio GPU driver, the Virtual Terminal layer
>> etc.
>
> Do you have a list of CONFIG options that need to be enabled there?
> Are there also any patches to the guest kernel driver required? Or
> did that work out of the box once you've enabled the right CONFIG
> options?
>
It required some kernel hacking. You need to enable the VT layer for
S390 to get any kind of graphics displayed.

I experimented on the guest side to enable the VT layer and run a
framebuffer console and also the Xfce desktop :)

Anyway the CONFIG options I used are:

The DRM configs to enable the DRM layer and virtio-gpu. I went with the 
default options for DRM layer.

CONFIG_DRM

CONFIG_DRM_VIRTIO_GPU

We also need to enable configs for the VT layer

CONFIG_VT

CONFIG_DUMMY_CONSOLE

And to display a framebuffer console for the guest

CONFIG_FRAMEBUFFER_CONSOLE



>> I would appreciate any feedback on these patches, specially the
>> first patch.
>
> Patches look good to me, but I'm not at all familiar with the
> virtio-gpu code, so that likely does not count...
>
> Anyway, thanks a lot for tackling this! It's pretty cool to finally
> have a graphics card on s390x, too :-)
>
> Thomas
>

  reply	other threads:[~2017-09-13 19:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-12 14:26 [Qemu-devel] [PATCH v1 0/2] Virtio GPU for S390 Farhan Ali
2017-09-12 14:26 ` [Qemu-devel] [PATCH v1 1/2] virtio_gpu: Handle endian conversion Farhan Ali
2017-09-13  8:13   ` Gerd Hoffmann
2017-09-13 15:53     ` Farhan Ali
2017-09-14  8:44       ` Gerd Hoffmann
2017-09-12 14:26 ` [Qemu-devel] [PATCH v1 2/2] virtio-gpu-ccw: Create a virtio gpu device for the ccw bus Farhan Ali
2017-09-13 12:09   ` David Hildenbrand
2017-09-13 14:53     ` Gerd Hoffmann
2017-09-13 18:22     ` Thomas Huth
2017-09-13 14:31   ` Halil Pasic
2017-09-13 19:00 ` [Qemu-devel] [PATCH v1 0/2] Virtio GPU for S390 Thomas Huth
2017-09-13 19:11   ` Farhan Ali [this message]
2017-09-14  8:46   ` Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f321fb90-cd47-0b63-dbd5-87d825bc3288@linux.vnet.ibm.com \
    --to=alifm@linux.vnet.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).