qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: jordan.l.justen@intel.com, Anthony Liguori <aliguori@us.ibm.com>,
	lersek@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-1.5] Revert "pc: Kill the "use flash device for BIOS unless KVM" misfeature"
Date: Wed, 15 May 2013 18:24:14 +0200	[thread overview]
Message-ID: <5193B6AE.7010100@redhat.com> (raw)
In-Reply-To: <87zjvw1adc.fsf@blackfin.pond.sub.org>

Il 15/05/2013 18:22, Markus Armbruster ha scritto:
> Paolo Bonzini <pbonzini@redhat.com> writes:
> 
>> Il 15/05/2013 17:09, Markus Armbruster ha scritto:
>>>>>>> @@ -209,7 +209,7 @@ void pc_system_firmware_init(MemoryRegion *rom_memory)
>>>>>>>       * TODO This device exists only so that users can switch between
>>>>>>>       * use of flash and ROM for the BIOS.  The ability to switch was
>>>>>>>       * created because flash doesn't work with KVM.  Once it does, we
>>>>>>> -     * should drop this device for new machine types.
>>>>>>> +     * should drop this device.
>>>>>>>       */
>>>>>>>      sysfw_dev = (PcSysFwDevice*) qdev_create(NULL, "pc-sysfw");
>>>>>>>  
>>>>>
>>>>> Why did you change the comment?
>>>>
>>>> Because we agreed on the way forward for the flash patches, and it will
>>>> remove the need for (a) changes to machine types; (b) pc_sysfw in
>>>> general.  The device will be created iff a -pflash or -drive if=pflash
>>>> option is provided.  Thus in principle you could use -M pc-0.12 with
>>>> -pflash and it will work.
>>>
>>> Yes, that's the way forward, and yes, that means we'll have no use for
>>> the "pc-sysfw" dummy device on new machine types.  But why can we
>>> retroactively delete it from existing machine types?
>>
>> Because it would only affect TCG and people probably don't care much
>> about backwards-compatible machine types with TCG.  I'd rather remove
>> the misfeature completely and start from scratch with a sane design, now
>> that we have it.
> 
> I'm fine with limiting our backward compatibility promise to KVM, I just
> didn't expect it.

I think in general there's no reason to distinguish TCG from KVM, but in
this case we've been doing that all along so...

Paolo

  reply	other threads:[~2013-05-15 16:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 12:38 [Qemu-devel] [PATCH for-1.5] Revert "pc: Kill the "use flash device for BIOS unless KVM" misfeature" Paolo Bonzini
2013-05-10 14:41 ` Anthony Liguori
2013-05-15 14:28   ` Markus Armbruster
2013-05-15 14:37     ` Paolo Bonzini
2013-05-15 15:09       ` Markus Armbruster
2013-05-15 15:52         ` Paolo Bonzini
2013-05-15 16:22           ` Markus Armbruster
2013-05-15 16:24             ` Paolo Bonzini [this message]
2013-05-13 16:46 ` Anthony Liguori

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=5193B6AE.7010100@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@redhat.com \
    --cc=jordan.l.justen@intel.com \
    --cc=lersek@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).