From: David Hildenbrand <david@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: David Gibson <dgibson@redhat.com>,
Jiri Denemark <jdenemar@redhat.com>,
David Hildenbrand <dhildenb@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Default CPU models on s390x and ppc64
Date: Thu, 17 Oct 2019 18:18:22 +0200 [thread overview]
Message-ID: <1feb4b48-a380-8c9e-561d-d62e8e45b3e8@redhat.com> (raw)
In-Reply-To: <CAFEAcA-pkD_LCh++TWoO77=Bu9mYe7HOkaeyCXjLopAmqhpi-g@mail.gmail.com>
On 17.10.19 18:13, Peter Maydell wrote:
> On Thu, 17 Oct 2019 at 17:09, David Hildenbrand <david@redhat.com> wrote:
>> The default model under KVM is "host", under TCG it's "qemu". We should
>> not use "qemu" under KVM, although it might work on some setups ...
>
> Possibly a tangent, but on Arm the approach we used to deal
> with "'-cpu host' only works for kvm" was to define a "-cpu max"
> meaning "best thing you can give me", which is an alias for
> -cpu host with KVM and an alias for a CPU with all the extra
> features we have emulation support under TCG. Then users can
> use '-cpu max' and have something that generally will DTRT
> regardless of accelerator.
>
We do have "-cpu max" on s390x as well. (under TCG, it enables some
additional features over "qemu", under KVM it is basically "host).
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2019-10-17 16:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 15:16 Default CPU models on s390x and ppc64 Jiri Denemark
2019-10-17 15:18 ` David Hildenbrand
2019-10-17 15:31 ` David Hildenbrand
2019-10-17 15:35 ` David Hildenbrand
2019-10-18 13:58 ` Jiri Denemark
2019-10-18 14:27 ` David Hildenbrand
2019-10-17 16:13 ` Peter Maydell
2019-10-17 16:18 ` David Hildenbrand [this message]
2019-10-18 14:02 ` Jiri Denemark
2019-10-18 14:14 ` Peter Maydell
2019-10-18 14:44 ` Christian Borntraeger
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=1feb4b48-a380-8c9e-561d-d62e8e45b3e8@redhat.com \
--to=david@redhat.com \
--cc=dgibson@redhat.com \
--cc=dhildenb@redhat.com \
--cc=jdenemar@redhat.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).