From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org, "Anthony Liguori" <anthony@codemonkey.ws>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Laszlo Ersek" <lersek@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] pc: reduce duplication, fix PIIX descriptions
Date: Tue, 27 Aug 2013 19:13:49 +0300 [thread overview]
Message-ID: <20130827161349.GA29285@redhat.com> (raw)
In-Reply-To: <20130827160923.GY2631@otherpad.lan.raisama.net>
On Tue, Aug 27, 2013 at 01:09:23PM -0300, Eduardo Habkost wrote:
> On Tue, Aug 27, 2013 at 09:51:22AM +0200, Markus Armbruster wrote:
> > "Michael S. Tsirkin" <mst@redhat.com> writes:
> >
> > > We have a lot of code duplication between machine types,
> > > this increases with each new machine type
> > > and each new field.
> > >
> > > This has already introduced a minor bug: description
> > > for pc-1.3 says "Standard PC" while description for
> > > pc-1.4 is "Standard PC (i440FX + PIIX, 1996)"
> > > which makes you think 1.3 is somehow more standard,
> > > or newer, while in fact it's a revision of the same PC.
> >
> > I wouldn't call it a bug. We're in the habit of never changing old
> > machine types, so when we created pc-i440fx-1.4 and pc-q35-1.4 with a
> > .desc that clearly explains the difference, we didn't change the older
> > versions the PC machine types as well.
> >
> > That may have been overly cautious. As long as .desc is not exposed to
> > the guest, it's not ABI, thus can be changed.
>
> I just confirmed that on qemu-system-x86_64 the only place where .desc
> is used is on the machine_parse() help/error code at vl.c. I don't know
> about other architectures.
Generally, one would hope we won't expose random
internal stuff to guests :).
> I suggest we explicitly document the field as a human-readable
> machine-type description that should be never exposed to the guest (just
> in case somebody decides to use .desc on some guest-visible table one
> day).
Where would you document this?
> --
> Eduardo
next prev parent reply other threads:[~2013-08-27 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 7:01 [Qemu-devel] [PATCH] pc: reduce duplication, fix PIIX descriptions Michael S. Tsirkin
2013-08-27 7:29 ` Paolo Bonzini
2013-08-27 8:32 ` Michael S. Tsirkin
2013-08-27 7:51 ` Markus Armbruster
2013-08-27 16:09 ` Eduardo Habkost
2013-08-27 16:13 ` Michael S. Tsirkin [this message]
2013-08-27 19:19 ` Eduardo Habkost
2013-08-27 21:47 ` Michael S. Tsirkin
2013-08-27 16:42 ` 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=20130827161349.GA29285@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=lersek@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).