From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Martin Kelly <mkelly@xevo.com>, poky@yoctoproject.org
Cc: "Lock, Joshua G" <joshua.g.lock@intel.com>,
Patrick Ohly <patrick.ohly@intel.com>
Subject: Re: [PATCH] qemuboot.conf: make cpus match built artifacts
Date: Mon, 24 Apr 2017 11:50:09 -0500 [thread overview]
Message-ID: <58FE2CC1.8030405@linux.intel.com> (raw)
In-Reply-To: <1492820479-2808-1-git-send-email-mkelly@xevo.com>
[-- Attachment #1: Type: text/plain, Size: 2325 bytes --]
Hi Martin,
It looks that we need to improve the alignment between compiler flags
and runqemu configurations. I don't know if is the right way to change
the cpu's to pentium and core2due may be could cause side-effects.
I think will be better to review the qemuboot profiles and to provide a
mechanism to modify it.
I want to know, what was your build settings?
Finally this patch needs to be send to oe-core mailing list.
Best regards,
Anibal
On 04/21/2017 07:21 PM, Martin Kelly wrote:
> Currently, the qemu CPUs for are specified as generic, but the built
> artifacts are not. For example, we build x86-64 artifacts targeting
> core2duo but run them in qemu with generic qemu/kvm CPUs. This causes
> some packages that take advantage of the host architecture to crash
> because they try to use CPU features not advertised by qemu. As an
> example, Qt uses ssse3. When artifacts linked against Qt and built
> targeting core2duo attempt to run on a generic qemu/kvm CPU, we get
> the following crash:
>
> Incompatible processor. This Qt build requires the following features:
> ssse3
>
> We could fix this by making packages like Qt not take advantage of CPU
> features. However, we will probably keep facing similar issues over
> time, so it's better to resolve them in a more enduring way.
>
> Fix this by making the qemu -cpu arguments match the built artifacts.
>
> Signed-off-by: Martin Kelly <mkelly@xevo.com>
> ---
> meta/conf/machine/include/qemuboot-x86.inc | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta/conf/machine/include/qemuboot-x86.inc b/meta/conf/machine/include/qemuboot-x86.inc
> index 06ac983..acd03a1 100644
> --- a/meta/conf/machine/include/qemuboot-x86.inc
> +++ b/meta/conf/machine/include/qemuboot-x86.inc
> @@ -1,12 +1,12 @@
> # For runqemu
> IMAGE_CLASSES += "qemuboot"
> QB_SYSTEM_NAME_x86 = "qemu-system-i386"
> -QB_CPU_x86 = "-cpu qemu32"
> -QB_CPU_KVM_x86 = "-cpu kvm32"
> +QB_CPU_x86 = "-cpu pentium2"
> +QB_CPU_KVM_x86 = "-cpu pentium2"
>
> QB_SYSTEM_NAME_x86-64 = "qemu-system-x86_64"
> QB_CPU_x86-64 = "-cpu core2duo"
> -QB_CPU_KVM_x86-64 = "-cpu kvm64"
> +QB_CPU_KVM_x86-64 = "-cpu core2duo"
>
> QB_AUDIO_DRV = "alsa"
> QB_AUDIO_OPT = "-soundhw ac97,es1370"
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-04-24 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 0:21 [PATCH] qemuboot.conf: make cpus match built artifacts Martin Kelly
2017-04-23 19:50 ` Burton, Ross
2017-04-24 15:59 ` Martin Kelly
2017-04-24 16:31 ` Richard Purdie
2017-04-24 17:57 ` Martin Kelly
2017-04-24 17:57 ` [poky] " Martin Kelly
2017-04-24 16:50 ` Aníbal Limón [this message]
2017-04-24 17:57 ` Martin Kelly
2017-04-24 17:57 ` Martin Kelly
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=58FE2CC1.8030405@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=joshua.g.lock@intel.com \
--cc=mkelly@xevo.com \
--cc=patrick.ohly@intel.com \
--cc=poky@yoctoproject.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.