qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PULL 00/13] ppc-for-2.12 queue 20180119


From: Thomas Huth
Subject: Re: [Qemu-devel] [PULL 00/13] ppc-for-2.12 queue 20180119
Date: Fri, 19 Jan 2018 15:58:51 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2

On 19.01.2018 15:11, Peter Maydell wrote:
> On 19 January 2018 at 09:40, David Gibson <address@hidden> wrote:
>> The following changes since commit b4d6ed1c5ae519d3efb5297be3ef6625ca2a20f4:
>>
>>   Merge remote-tracking branch 'remotes/ericb/tags/pull-nbd-2018-01-17' into 
>> staging (2018-01-18 15:25:17 +0000)
>>
>> are available in the Git repository at:
>>
>>   git://github.com/dgibson/qemu.git tags/ppc-for-2.12-20180119
>>
>> for you to fetch changes up to 040cb0a2badf9e265cdbb78380048cd1624dd434:
>>
>>   target/ppc/spapr_caps: Add macro to generate spapr_caps migration vmstate 
>> (2018-01-19 16:06:26 +1100)
>>
>> ----------------------------------------------------------------
>> ppc patch queue 2018-01-19
>>
>> Quite soon after my previous pull request, but it's already
>> accumulated a reasonable amount of stuff:
>>   * Significant TCG speedup by optimizing cmp generation
>>   * Fix a regression caused by recent change to set compat mode on
>>     hotplugged cpus
>>   * Cleanup of default configs
>>   * Some implementation of msgsnd/msgrcv instructions for server chips
>>
>> ----------------------------------------------------------------
> 
> 
> 'make check' logs are full of
> qemu-system-ppcemb: warning: qemu-system-ppcemb is deprecated, please
> use qemu-system-ppc instead.
> 
> You need to silence that, or it's impossible for me to find actual
> warnings in build tests.

Sorry for that!

David, could you please simply unqueue the ppcemb deprecation patch
until I found a better solution? qtest_enabled() does not seem to work
in ppc_cpu_register_types(), so I've got to find a different spot for
printing the warning...

 Thomas



reply via email to

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