All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Pavel Fedin <p.fedin@samsung.com>,
	'Cole Robinson' <crobinso@redhat.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: Fri, 08 May 2015 10:39:12 +0200	[thread overview]
Message-ID: <554C7630.6020004@redhat.com> (raw)
In-Reply-To: <00b501d0895e$abfe8660$03fb9320$@samsung.com>



On 08/05/2015 09:14, 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.

Actually I agree with your patch.  It's the same that x86 does.

Paolo

  parent reply	other threads:[~2015-05-08  8:39 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 [this message]
2015-05-10 21:07             ` Cole Robinson

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=554C7630.6020004@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.