qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Laszlo Ersek <lersek@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [Qemu-devel] selecting VIRTIO_INPUT and VIRTIO_VGA
Date: Tue, 21 Jul 2015 14:08:08 +0200	[thread overview]
Message-ID: <55AE3628.4010400@suse.de> (raw)
In-Reply-To: <55AD46A3.6060308@redhat.com>

On 07/20/15 21:06, Laszlo Ersek wrote:
> Cc'ing Alex
>
> On 07/13/15 12:15, Paolo Bonzini wrote:
>>
>> On 13/07/2015 09:32, Gerd Hoffmann wrote:
>>>> and virtio-vga is only compiled on 64-bit Intel?
>>> There is virtio-gpu-pci ...
>>>
>>> Any specific reason why we need vga compatibility on !x86?
>> I was actually thinking about 32-bit x86. :)  I agree that !x86 is not
>> necessary.
> I disagree :)
>
> (This is actually my more important followup to this thread; the other
> message I just couldn't resist sending.)
>
> Gerd recently contributed virtio-vga support to OvmfPkg/QemuVideoDxe:
>
> https://github.com/tianocore/edk2/commit/94210dc9
>
> That support depends on vga compat. All fine.
>
> What's probably not obvious is that I had ported
> PcAtChipsetPkg/PciHostBridgeDxe to ArmVirtPkg -- which drives Alex's
> generic PCIe host bridge, exposed on qemu-system-(arm|aarch64) -M virt
> -- and included OvmfPkg/QemuVideoDxe in the ArmVirtQemu.dsc build too.
>
> That means you can currently stick a -device VGA into -M virt, and it
> will work. Since OvmfPkg/QemuVideoDxe recognizes virtio-vga (see edk2

For some definition of work, yes :). It will work perfectly fine with 
TCG, you will run into cache coherency problems with KVM because the 
guest maps MMIO regions (like the vram) as uncached while QEMU accesses 
it as cached.

> 94210dc9 again), and the driver is included by ArmVirtQemu.dsc, I think
> it would be probably useful to build the device model for arm/aarch64
> targets too.
>
> See also QEMU commit 332261de2b (together with its parent commits).

I agree. Also, as far as I understood Marc, his hope was that the fix to 
halfway working VGA emulation would be virtio-gpu.


Alex

  reply	other threads:[~2015-07-21 12:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-11 17:55 [Qemu-devel] selecting VIRTIO_INPUT and VIRTIO_VGA Paolo Bonzini
2015-07-13  7:32 ` Gerd Hoffmann
2015-07-13 10:15   ` Paolo Bonzini
2015-07-13 11:45     ` Gerd Hoffmann
2015-07-13 11:49       ` Paolo Bonzini
2015-07-20 18:52         ` Laszlo Ersek
2015-07-20 19:06     ` Laszlo Ersek
2015-07-21 12:08       ` Alexander Graf [this message]
2015-07-21 12:48         ` Laszlo Ersek
2015-07-21 12:51         ` Marc Zyngier
2015-07-25  9:49           ` Gerd Hoffmann
2015-07-26  9:31             ` Laszlo Ersek
2015-07-26 10:17               ` Peter Maydell
2015-07-26 10:40                 ` Peter Maydell
2015-07-26 11:22                 ` Laszlo Ersek
2015-07-27  7:52             ` Marc Zyngier

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=55AE3628.4010400@suse.de \
    --to=agraf@suse.de \
    --cc=ard.biesheuvel@linaro.org \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=marc.zyngier@arm.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).