From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH] pc: rename machine types
Date: Wed, 09 Jan 2013 11:32:26 +0100 [thread overview]
Message-ID: <50ED473A.7040209@redhat.com> (raw)
In-Reply-To: <20130109100935.GB20716@redhat.com>
On 01/09/13 11:09, Daniel P. Berrange wrote:
>>> 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'.
>
> Either of these sound fine to me, with a slight preference for the
> first option.
>
>>> (3) Something different?
>
> If we really want 'pc' in the name, then
>
> (4) pci440fx & pcq35
> (5) pcpiix & pcich9
A dash would improve readability, also we have isapc which has pc as
postfix, so maybe 'i440fx-pc' + 'q35-pc' ?
>> The issue I have with 'i440fx' and 'q35' is that it's basically
>> gibberish to a non-QEMU developer.
>
> With my users and/or libvirt developers hat on, I don't agree really.
> What Gerd suggests clearly states the hardware type being used by the
> machine. I think 'pc' is pretty much meaningless as a machine name
> because it can mean pretty much anything you want to it. It is akin
> to just calling your network device 'nic' and your disk device 'disk',
> which QEMU doesn't do for obvious reasons.
Fully agree. It also follows the convention of other archs (just look
at the arm machine names).
cheers,
Gerd
next prev parent reply other threads:[~2013-01-09 10:32 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
2013-01-09 10:09 ` Daniel P. Berrange
2013-01-09 10:32 ` Gerd Hoffmann [this message]
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=50ED473A.7040209@redhat.com \
--to=kraxel@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=berrange@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).