From: "Daniel P. Berrange" <berrange@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] pc: rename machine types
Date: Wed, 9 Jan 2013 10:09:35 +0000 [thread overview]
Message-ID: <20130109100935.GB20716@redhat.com> (raw)
In-Reply-To: <87obgzzm3q.fsf@codemonkey.ws>
On Tue, Jan 08, 2013 at 10:16:25AM -0600, Anthony Liguori wrote:
> 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'.
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
> 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.
What if someone can along and implemented a bunch more machine types
for x86 ? Any name based soly on 'pc' would be even more meaningless
than it already is. IMHO including the actual hardware name in some
form is the right way to distinguish this.
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2013-01-09 10:09 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 [this message]
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=20130109100935.GB20716@redhat.com \
--to=berrange@redhat.com \
--cc=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).