qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PULL 00/17] x86 and CPU queue, 2016-10-24


From: Eduardo Habkost
Subject: Re: [Qemu-devel] [PULL 00/17] x86 and CPU queue, 2016-10-24
Date: Mon, 24 Oct 2016 14:34:29 -0200
User-agent: Mutt/1.7.0 (2016-08-17)

On Mon, Oct 24, 2016 at 05:20:17PM +0100, Peter Maydell wrote:
> On 24 October 2016 at 15:31, Eduardo Habkost <address@hidden> wrote:
> > The following changes since commit 4387f5671f9676336c87b68f5e87ba54fbea3714:
> >
> >   Merge remote-tracking branch 'remotes/sstabellini/tags/xen-20161021-tag' 
> > into staging (2016-10-24 10:26:44 +0100)
> >
> > are available in the git repository at:
> >
> >   git://github.com/ehabkost/qemu.git tags/x86-pull-request
> >
> > for you to fetch changes up to c100860d23cd21495fcd2c14f246389e401d7900:
> >
> >   target-i386: Print warning when mixing [+-]foo and foo=(on|off) 
> > (2016-10-24 11:51:33 -0200)
> >
> > ----------------------------------------------------------------
> > x86 and CPU queue, 2016-10-24
> >
> > x2APIC support to APIC code, cpu_exec_init() refactor on all
> > architectures, and other x86 changes.
> 
> I'm afraid this generates some spurious warnings under OSX:
> 
>   GTESTER check-qtest-i386
> "kvm" accelerator not found.
> "kvm" accelerator not found.
> "kvm" accelerator not found.
> "kvm" accelerator not found.
> "kvm" accelerator not found.
> "kvm" accelerator not found.
> "kvm" accelerator not found.
> "kvm" accelerator not found.
> qemu-system-i386: warning: Ambiguous CPU model string. Don't mix both
> "-mce" and "mce=on"
> qemu-system-i386: warning: Ambiguous CPU model string. Don't mix both
> "+cx8" and "cx8=off"
> qemu-system-i386: warning: Compatibility of ambiguous CPU model
> strings won't be kept on future QEMU versions
> 
> (similarly for check-qtest-x86_64).
> 
> Tests should never print out strings with "warning:" in them,
> to avoid false-positives when scanning build logs.
> 
> I'm not entirely sure why these only happen on OSX, though.

Probably the host has an older glib version that doesn't support
subprocesses. In this case, the
"/x86/cpuid/parsing-plus-minus/subprocess" test case will be run
on the main process.

I thought that would be better than skipping the test case
entirely. But I can #ifdef the entire
"/x86/cpuid/parsing-plus-minus/subprocess" test case if that's
better.

-- 
Eduardo



reply via email to

[Prev in Thread] Current Thread [Next in Thread]