From: Cole Robinson <crobinso@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>,
'Peter Maydell' <peter.maydell@linaro.org>
Cc: 'QEMU Developers' <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Fix default CPU model for ARM64
Date: Sun, 10 May 2015 17:07:26 -0400 [thread overview]
Message-ID: <554FC88E.70208@redhat.com> (raw)
In-Reply-To: <00b501d0895e$abfe8660$03fb9320$@samsung.com>
On 05/08/2015 03:14 AM, Pavel Fedin wrote:
> Hello!
>
>> FWIW virt-manager 1.2.0 (just released) will do the following when creating a
>> new VM:
>>
>> - aarch64 + kvm : -cpu host
>> - aarch64 + tcg : -cpu cortex-a57
>> - arm32 + kvm : -cpu host
>> - arm32 + tcg : defer to qemu
>>
>> Though if you explicitly request 'hypervisor default' then we won't specify
>> any -cpu and defer to qemu, which will hit the cortex-a15 default for aarch64
>
> virt-manager is not the only tool to create VMs...
> But, okay. Seems you just don't want to change this. Well... I still don't agree and this
> default looks strange for me, but it's just me. I'm out of further arguments.
>
I wasn't implying any opinion about your proposed patch, just clarifying the
details about how latest virt-manager performs since you mentioned it
upthread. FWIW I agree with the idea of your patch
- Cole
prev parent reply other threads:[~2015-05-10 21:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 15:03 [Qemu-devel] [PATCH] Fix default CPU model for ARM64 Pavel Fedin
2015-05-06 15:50 ` Peter Maydell
2015-05-06 18:06 ` Pavel Fedin
2015-05-06 18:15 ` Peter Maydell
2015-05-07 6:36 ` Pavel Fedin
2015-05-07 14:38 ` Cole Robinson
2015-05-08 7:14 ` Pavel Fedin
2015-05-08 7:59 ` Peter Crosthwaite
2015-05-08 8:44 ` Pavel Fedin
2015-05-08 15:59 ` Peter Crosthwaite
2015-05-08 8:39 ` Paolo Bonzini
2015-05-10 21:07 ` Cole Robinson [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=554FC88E.70208@redhat.com \
--to=crobinso@redhat.com \
--cc=p.fedin@samsung.com \
--cc=peter.maydell@linaro.org \
--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).