qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] selecting VIRTIO_INPUT and VIRTIO_VGA
Date: Mon, 20 Jul 2015 20:52:15 +0200	[thread overview]
Message-ID: <55AD435F.8040808@redhat.com> (raw)
In-Reply-To: <55A3A5C8.2060201@redhat.com>

On 07/13/15 13:49, Paolo Bonzini wrote:
> 
> 
> On 13/07/2015 13:45, 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.
>> Yea, setting it for i386 makes sense indeed.  Just went out of my focus,
>> last time I used qemu-system-i386 was a few years back ...
>>
>> Any reason why one would use qemu-system-i386 instead of
>> qemu-system-x86_64 btw?  I suspect a 32bit host machine is the only one?
> 
> Yes, I think so.
> 
> Well, for TCG there is a difference of course.  Laszlo was using
> qemu-system-i386 because OVMF doesn't support our x86_64 layout for the
> SMM state save area.

Right, for 64-bit processors, there's one definition from AMD and
another from Intel. They are incompatible.

qemu-system-i386, with TCG, exposes the 32-bit SMM save state area that
the 32-bit SMM drivers -- open sourced by Intel, and being ported to
OVMF by yours truly -- are compatible with.

qemu-system-x86_64, with TCG, exposes the AMD flavor of the 64-bit area.
The code open sourced by Intel thus far is absolutely incompatible with
it. (In the code there are traces of support for the Intel flavor.)

With KVM support now existing (thanks Paolo), this might not be that
important any longer. (Paolo taught me that -lm can disable long mode
under KVM with qemu-system-x86_64, determining the save state aera
layout too.)

Thanks
Laszlo

  reply	other threads:[~2015-07-20 18:52 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 [this message]
2015-07-20 19:06     ` Laszlo Ersek
2015-07-21 12:08       ` Alexander Graf
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=55AD435F.8040808@redhat.com \
    --to=lersek@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --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).