Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

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

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

On 04/25/2018 12:54 PM, Martin Jansa wrote: On Thu, Jun 15, 2017 at 05:37:50PM +0100, Burton, Ross wrote: On 15 June 2017 at 17:17, Martin Kelly wrote: I am no expert, but running qemu -cpu help just says: kvm32 - "Common 32-bit KVM processor" kvm64 - "Common 64-bit KVM

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

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

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

On Thu, Jun 15, 2017 at 05:37:50PM +0100, Burton, Ross wrote: > On 15 June 2017 at 17:17, Martin Kelly wrote: > > > I am no expert, but running qemu -cpu help just says: > > > > kvm32 - "Common 32-bit KVM processor" > > kvm64 - "Common 64-bit KVM processor" > > > > My best guess

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

On 15 June 2017 at 17:17, Martin Kelly wrote: > I am no expert, but running qemu -cpu help just says: > > kvm32 - "Common 32-bit KVM processor" > kvm64 - "Common 64-bit KVM processor" > > My best guess is that, running on qemu without kvm, both cases will be > slow (since it's

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

On 06/15/2017 04:45 AM, Burton, Ross wrote: On 2 May 2017 at 20:20, Martin Kelly > wrote: -QB_CPU_KVM_x86-64 = "-cpu kvm64" +QB_CPU_KVM_x86-64 = "-cpu core2duo" What's the actual meaning of the "kvm64" and "kvm32" CPUs? Is there a performance

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

On 2 May 2017 at 20:20, Martin Kelly wrote: > -QB_CPU_KVM_x86-64 = "-cpu kvm64" > +QB_CPU_KVM_x86-64 = "-cpu core2duo" > What's the actual meaning of the "kvm64" and "kvm32" CPUs? Is there a performance hit? Should we be instead changing the qemu machine to target a different

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

On 05/22/2017 11:09 AM, Martin Kelly wrote: On 05/22/2017 10:53 AM, Randy Witt wrote: On 05/22/2017 10:29 AM, Martin Kelly wrote: (friendly ping) On 05/02/2017 12:20 PM, Martin Kelly wrote: Currently, the qemu CPUs for are specified as generic, but the built artifacts are not. For example,

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

On 05/22/2017 10:53 AM, Randy Witt wrote: On 05/22/2017 10:29 AM, Martin Kelly wrote: (friendly ping) On 05/02/2017 12:20 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

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

On 05/22/2017 10:29 AM, Martin Kelly wrote: (friendly ping) On 05/02/2017 12:20 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

Re: [OE-core] [PATCH resend] qemuboot.conf: make cpus match built artifacts

(friendly ping) On 05/02/2017 12:20 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