qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: <ckim@etri.re.kr>
To: "'Peter Maydell'" <peter.maydell@linaro.org>
Cc: "'Paolo Bonzini'" <pbonzini@redhat.com>,
	"'Philippe Mathieu-Daudé'" <philmd@redhat.com>,
	'qemu-devel' <qemu-devel@nongnu.org>,
	"'Markus Armbruster'" <armbru@redhat.com>,
	'qemu-discuss' <qemu-discuss@nongnu.org>
Subject: RE: supported machines for aarch64
Date: Fri, 19 Feb 2021 19:18:21 +0900	[thread overview]
Message-ID: <025a01d706a8$8d029cb0$a707d610$@etri.re.kr> (raw)
In-Reply-To: <CAFEAcA9GJLr_GX3fHgssE2E=-q6waeN5ZKgWfCrdGAyK0e3C_g@mail.gmail.com>

Hi Peter Maydell,

Thanks, that made it clearer to me.(actually I was reading the page you mentioned)

Chan Kim

> -----Original Message-----
> From: Peter Maydell <peter.maydell@linaro.org>
> Sent: Friday, February 19, 2021 7:04 PM
> To: Chan Kim <ckim@etri.re.kr>
> Cc: Philippe Mathieu-Daudé <philmd@redhat.com>; qemu-discuss <qemu-
> discuss@nongnu.org>; Paolo Bonzini <pbonzini@redhat.com>; qemu-devel
> <qemu-devel@nongnu.org>; Markus Armbruster <armbru@redhat.com>
> Subject: Re: supported machines for aarch64
> 
> On Fri, 19 Feb 2021 at 08:05, <ckim@etri.re.kr> wrote:
> > These are the machine lists that included cortex-a72 when I gave
> > qemu-system-aarch64 --machine xxx --cpu help.
> 
> Adding '--machine whatever' to your command line does not change the
> output of '--cpu help'. As Philippe says, it happens that QEMU processes -
> -cpu before --machine, so it handles '--cpu help', prints the fixed list
> of supported CPUs, and ignores whether you passed a valid --machine option
> or not.
> 
> There is no automated way to get QEMU to tell you which CPUs a particular
> board model supports.
> 
> I recommend that you follow the advice given here
> https://qemu.readthedocs.io/en/latest/system/target-arm.html#choosing-a-
> board-model
> for how to choose a board model. (Short answer: if you know you want to
> run guest code for a specific board type, use that board type. Otherwise,
> use 'virt'.) Then, you should stick with the default CPU type (ie, do not
> pass --cpu) for that board, for all board types *except* 'virt'. For
> 'virt' you can pass in the CPU type you want (and the documentation lists
> which types it supports).
> 
> -- PMM






      reply	other threads:[~2021-02-19 10:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <027101d7035b$2e94a600$8bbdf200$@etri.re.kr>
2021-02-15  7:38 ` supported machines for aarch64 Philippe Mathieu-Daudé
2021-02-19  8:01   ` ckim
2021-02-19 10:04     ` Peter Maydell
2021-02-19 10:18       ` ckim [this message]

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='025a01d706a8$8d029cb0$a707d610$@etri.re.kr' \
    --to=ckim@etri.re.kr \
    --cc=armbru@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@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).