From: Martin Kelly <mkelly@xevo.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Joshua G Lock <joshua.g.lock@intel.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH resend] qemuboot.conf: make cpus match built artifacts
Date: Fri, 27 Apr 2018 10:47:22 -0700 [thread overview]
Message-ID: <44ffb221-e22a-6709-b4ee-41f1be0fe552@xevo.com> (raw)
In-Reply-To: <CA+chaQfHaSAPXrU5pk_=M8hEjScxdVrAcUudekjFbzCUpQxSYA@mail.gmail.com>
On 04/25/2018 04:11 PM, Martin Jansa wrote:
> There are actually 3 we need to consider for lowest common denominator.
>
> The one we build for, the one we build on and the one where we will run
> the qemu in the end.
>
> I mean the core2duo is probably best match for core2-64 DEFAULT used by
> qemux86-64 MACHINE. But it's not good match to emulate with QEmu and KVM
> enabled on the host like my.
>
> It's easy to work around this, we probably don't need to change the
> default values, but it would be good to document this case and how to
> override QB_CPU_KVM if your host doesn't match the features of core2duo.
>
Agreed. I just sent a patch to yocto-docs to add some documentation for
this.
prev parent reply other threads:[~2018-04-27 18:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 19:20 [PATCH resend] qemuboot.conf: make cpus match built artifacts Martin Kelly
2017-05-22 17:29 ` Martin Kelly
2017-05-22 17:53 ` Randy Witt
2017-05-22 18:09 ` Martin Kelly
2017-06-13 16:44 ` Martin Kelly
2017-06-15 11:45 ` Burton, Ross
2017-06-15 16:17 ` Martin Kelly
2017-06-15 16:37 ` Burton, Ross
2018-04-25 19:54 ` Martin Jansa
2018-04-25 23:02 ` Martin Kelly
2018-04-25 23:11 ` Martin Jansa
2018-04-27 17:47 ` Martin Kelly [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=44ffb221-e22a-6709-b4ee-41f1be0fe552@xevo.com \
--to=mkelly@xevo.com \
--cc=joshua.g.lock@intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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