From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] pc: rename machine types
Date: Tue, 08 Jan 2013 10:16:25 -0600 [thread overview]
Message-ID: <87obgzzm3q.fsf@codemonkey.ws> (raw)
In-Reply-To: <50EC38FF.7010801@redhat.com>
Gerd Hoffmann <kraxel@redhat.com> writes:
> On 01/08/13 14:57, Anthony Liguori wrote:
>> Gerd Hoffmann <kraxel@redhat.com> writes:
>>
>>> Starting with release 1.4 we have a fully functional q35 machine type,
>>> i.e. "qemu -M q35" JustWorks[tm]. Update machine type names to reflect
>>> that:
>>>
>>> * pc-1.4 becomes piix-1.4
>>
>> PIIX is the southbridge. A more appropriate (and google-able) name
>> would be i440fx-1.4.
>
> Fine with me.
>
>>> * q35-next becomes q35-1.4
>>
>> I can't help but bikeshed a little here. I dislike that we are going
>> from something that's reasonable understandable (pc) to something
>> completely obscure (piix and q35).
>
> 'pc' is pretty generic. I want discontinue it, except for aliasing 'pc'
> to the default machine type, for compatibility reasons.
>
> I don't care that much what the actual names are. Using piix + q35 is
> inconsistent, so it isn't that a good choice indeed. So what now?
>
> (1) We could go for the host bridge and use 'i440fx' + 'q35'.
> (2) We could go for the south bridge and use 'piix' + 'ich9'.
> (3) Something different?
The issue I have with 'i440fx' and 'q35' is that it's basically
gibberish to a non-QEMU developer.
What about 'qemupc-legacy' and 'qemupc'? 'pc' can still be an alias for
'qemupc-legacy'.
I very much like the legacy distinction as it steers users toward q35
which I think is what we want.
Regards,
Anthony Liguori
>
> (1) has the advantage that we keep the established name 'q35' for the
> new machine type.
> (2) has the advantage that it matches the naming convention of
> several devices in the tree (piix/ich9 prefix).
>
>> I would be in favor of the i440fx machine being called "legacy-pc" and
>> q35 gaining the title of "pc".
>
> No way. Assigning 'pc' to q35 is asking for serious trouble. That way
> 'qemu -M pc' silently switches the chipset underneath the guest when
> upgrading from 1.3 to 1.4.
>
> cheers,
> Gerd
next prev parent reply other threads:[~2013-01-08 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 7:59 [Qemu-devel] [PATCH] pc: rename machine types Gerd Hoffmann
2013-01-08 13:57 ` Anthony Liguori
2013-01-08 15:19 ` Gerd Hoffmann
2013-01-08 16:16 ` Anthony Liguori [this message]
2013-01-09 10:09 ` Daniel P. Berrange
2013-01-09 10:32 ` Gerd Hoffmann
2013-01-09 14:47 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2013-01-09 15:30 Gerd Hoffmann
2013-01-10 8:21 ` Markus Armbruster
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=87obgzzm3q.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kraxel@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).