qemu-ppc
[Top][All Lists]
Advanced

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

Re: [Qemu-ppc] [PULL 00/12] ppc-for-2.12 queue 20180108


From: Peter Maydell
Subject: Re: [Qemu-ppc] [PULL 00/12] ppc-for-2.12 queue 20180108
Date: Tue, 9 Jan 2018 11:46:41 +0000

On 8 January 2018 at 05:53, David Gibson <address@hidden> wrote:
> The following changes since commit 281f327487c9c9b1599f93c589a408bbf4a651b8:
>
>   Merge remote-tracking branch 
> 'remotes/vivier/tags/m68k-for-2.12-pull-request' into staging (2017-12-22 
> 00:11:36 +0000)
>
> are available in the Git repository at:
>
>   git://github.com/dgibson/qemu.git tags/ppc-for-2.12-20180108
>
> for you to fetch changes up to 9f173585d3f35345b2facce50620ce2cdda05f2f:
>
>   spapr: Correct compatibility mode setting for hotplugged CPUs (2018-01-08 
> 13:33:17 +1100)
>
> ----------------------------------------------------------------
> ppc patch queue 2018-01-08
>
> This pull requests supersedes both ppc-for-2.12-20180103 and
> ppc-for-2.12-20171219.  We've discovered that some substantial
> extensions to the proposed capabilities infrastructure will be
> valuable, amongst other things for managing/advertising workarounds
> for the dreaded Meltdown/Spectre bugs.
>
> Although that could be done as follow on changes, since the caps
> infrastructure hasn't been merged yet, we might as well pull it out
> while we rework, and just merge the unrelated bugfixes.
>
> The last two pull requests apparently had problems on some arm32
> systems.  I haven't been able to reproduce those, so I have no idea
> which patch is causing them.  If we get lucky and it was one of the
> patches I've removed from this series, this may also serve to unjam
> the other fixes.

This still hangs on my arm32 setup in the migration test. I'll see
if I can identify what is going wrong.

thanks
-- PMM



reply via email to

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