From: Thomas Huth <thuth@redhat.com>
To: Farhan Ali <alifm@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-fbdev@vger.kernel.org
Cc: geert@linux-m68k.org, borntraeger@de.ibm.com,
tomi.valkeinen@ti.com, b.zolnierkie@samsung.com
Subject: Re: [PATCH v3 3/3] s390/setup : enable display support for KVM guest
Date: Mon, 19 Feb 2018 20:55:39 +0100 [thread overview]
Message-ID: <b7e118a9-9920-07bc-ccac-f72f451fccea@redhat.com> (raw)
In-Reply-To: <8a6103fcc2b05f4426dcf6573a2175ffe6211403.1519053920.git.alifm@linux.vnet.ibm.com>
On 19.02.2018 16:47, Farhan Ali wrote:
> The S390 architecture does not support any graphics hardware,
> but with the latest support for Virtio GPU in Linux and Virtio
> GPU emulation in QEMU, it's possible to enable graphics for
> S390 using the Virtio GPU device.
>
> To enable display we need to enable the Linux Virtual Terminal (VT)
> layer for S390. But the VT subsystem initializes quite early
> at boot so we need a dummy console driver till the Virtio GPU
> driver is initialized and we can run the framebuffer console.
>
> The framebuffer console over a Virtio GPU device can be run
> in combination with the serial SCLP console (default on S390).
> The SCLP console can still be accessed by management applications
> (eg: via Libvirt's virsh console).
>
> Signed-off-by: Farhan Ali <alifm@linux.vnet.ibm.com>
> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
> ---
> arch/s390/kernel/setup.c | 2 ++
> drivers/tty/Kconfig | 2 +-
> drivers/video/console/Kconfig | 2 +-
> 3 files changed, 4 insertions(+), 2 deletions(-)
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2018-02-19 19:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 15:47 [PATCH v3 0/3] Enable CONFIG_VT support for S390 Farhan Ali
2018-02-19 15:47 ` [PATCH v3 1/3] Kconfig : Remove HAS_IOMEM dependency for Graphics support Farhan Ali
2018-02-19 16:25 ` Thomas Huth
2018-02-19 16:38 ` Farhan Ali
2018-02-21 10:05 ` Christian Borntraeger
2018-02-21 10:22 ` Christian Borntraeger
2018-02-21 10:32 ` Cornelia Huck
2018-02-21 11:09 ` Christian Borntraeger
2018-02-21 11:14 ` Thomas Huth
2018-02-21 11:22 ` Christian Borntraeger
2018-02-21 11:29 ` Thomas Huth
2018-02-21 11:49 ` Christian Borntraeger
2018-02-21 12:07 ` Cornelia Huck
2018-02-21 12:11 ` Christian Borntraeger
2018-02-21 16:39 ` Farhan Ali
2018-02-22 7:34 ` Christian Borntraeger
2018-02-21 11:23 ` Cornelia Huck
2018-02-21 8:44 ` Christian Borntraeger
2018-02-21 11:50 ` Bartlomiej Zolnierkiewicz
2018-02-19 15:47 ` [PATCH v3 2/3] s390/char : Rename EBCDIC keymap variables Farhan Ali
2018-02-19 19:52 ` Thomas Huth
2018-02-19 15:47 ` [PATCH v3 3/3] s390/setup : enable display support for KVM guest Farhan Ali
2018-02-19 19:55 ` Thomas Huth [this message]
2018-02-20 9:43 ` [PATCH v3 0/3] Enable CONFIG_VT support for S390 Christian Borntraeger
2018-02-20 13:45 ` Farhan Ali
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=b7e118a9-9920-07bc-ccac-f72f451fccea@redhat.com \
--to=thuth@redhat.com \
--cc=alifm@linux.vnet.ibm.com \
--cc=b.zolnierkie@samsung.com \
--cc=borntraeger@de.ibm.com \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=tomi.valkeinen@ti.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).