qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Richard Henderson <rth@twiddle.net>, Jia Liu <proljc@gmail.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] -cpu behavior (was: [PATCH v3 4/4] target-openrisc: Fix cpu_model by name)
Date: Mon, 22 Jul 2013 18:29:25 +0200	[thread overview]
Message-ID: <51ED5DE5.5090704@suse.de> (raw)
In-Reply-To: <CAFEAcA8no=NUG9otyznMgTZ1VHrKdv5Zcz5XDMUNFCMhsXeuoA@mail.gmail.com>

Am 22.07.2013 17:38, schrieb Peter Maydell:
> On 22 July 2013 16:25, Anthony Liguori <anthony@codemonkey.ws> wrote:
>> Andreas Färber <afaerber@suse.de> writes:
>>> Am 22.07.2013 13:34, schrieb Peter Maydell:
>>>> Looking at all of the '-cpu help' output, alpha seems to be
>>>> the odd one out here: none of the others list valid CPUs
>>>> with "-$arch-cpu" suffixes.
>>>
>>> Right, because all others had implemented -cpu ? before we introduced
>>> that naming scheme and I tried to keep output compatibility for them.
>>> Focus for alpha was therefore on -cpu foo compatibility only.
>>>
>>> Anthony had clearly stated on a KVM call that using full type names for
>>> future CPU hot-add was the right thing to do and possibly even composite
>>> convenience types like 4core-xeonblabla-x86_64-cpu; how that relates to
>>> -cpu and new targets was never clearly defined though. ;)
>>
>> That's pretty gross, but yes, we should have:
>>
>> qemu -device Xeon-E5-4610,id=sock0 -device Xeon-E5-4610,id=sock1
>>
>> Which effectively does:
>>
>> qemu -cpu SandyBridge -smp cores=6,threads=2,sockets=2
>>
>> By today's standards.
> 
> That doesn't really answer the question of "should the argument
> to -cpu be a QOM typename or a human friendly name?" though
> (though I note none of your -cpu or -device argument examples
> are QOM type names, since they're missing the -$arch-cpu suffix).

Depending on how we register those types, they don't necessarily need an
-$arch-cpu suffix iff they are deemed globally unique. In this case
there would be a 32-bit and 64-bit type though, I guess.

But there's no qemu executable either, so we shouldn't take the example
literally. :P

>> I think this applies equally well to other architecture.
>>  Model hardware more closely.
> 
> For ARM this would mean "don't support -cpu at all, it
> is always hardwired by the board model" :-)

No, it means the board creates the equivalent of -device tegra2-soc. :)
Or exynos4210, highbank-soc or whatever. Less code in machine init, more
code in QOM devices reusable with -M none -readconfig foo.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-07-22 16:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22  8:56 [Qemu-devel] [PATCH v3 0/4] target-openrisc hw/openrisc: Some OpenRISC fix Jia Liu
2013-07-22  8:56 ` [Qemu-devel] [PATCH v3 1/4] hw/openrisc: Indent typo Jia Liu
2013-07-22  9:21   ` Peter Maydell
2013-07-22  8:56 ` [Qemu-devel] [PATCH v3 2/4] hw/openrisc: Use stderr output instead of qemu_log Jia Liu
2013-07-22  9:21   ` Peter Maydell
2013-07-22  8:56 ` [Qemu-devel] [PATCH v3 3/4] target-openrisc: Free typename Jia Liu
2013-07-22  9:37   ` Jia Liu
2013-07-22  9:41     ` Peter Maydell
2013-07-22  9:43       ` Jia Liu
2013-07-22  8:56 ` [Qemu-devel] [PATCH v3 4/4] target-openrisc: Fix cpu_model by name Jia Liu
2013-07-22  9:29   ` Peter Maydell
2013-07-22  9:42     ` Jia Liu
2013-07-22  9:43       ` Peter Maydell
2013-07-22  9:54         ` Jia Liu
2013-07-22 10:12         ` Jia Liu
2013-07-22 10:37         ` Andreas Färber
2013-07-22 10:40           ` Peter Maydell
2013-07-22 11:17             ` Andreas Färber
2013-07-22 11:34               ` Peter Maydell
2013-07-22 12:26                 ` [Qemu-devel] -cpu behavior (was: [PATCH v3 4/4] target-openrisc: Fix cpu_model by name) Andreas Färber
2013-07-22 12:33                 ` [Qemu-devel] [PATCH v3 4/4] target-openrisc: Fix cpu_model by name Andreas Färber
2013-07-22 15:25                   ` Anthony Liguori
2013-07-22 15:38                     ` Peter Maydell
2013-07-22 16:29                       ` Andreas Färber [this message]
2013-07-22 17:39                       ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2013-07-22 17:34 [Qemu-devel] -cpu behavior (was: [PATCH v3 4/4] target-openrisc: Fix cpu_model by name) Michael Mueller

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=51ED5DE5.5090704@suse.de \
    --to=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=borntraeger@de.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=proljc@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).