|Subject:||Re: [Qemu-ppc] [PULL 00/12] ppc-for-2.12 queue 20180108|
|Date:||Wed, 10 Jan 2018 10:37:37 +0000|
Hi devs sorry if i enter in the discussion about.
gcc gave errors in building this queue.
here i paste my build log.
This is my machine infos and so and so
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Big Endian
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 1
NUMA node(s): 1
Model: 1.1 (pvr 0044 0101)
Model name: PPC970MP, altivec supported
CPU max MHz: 2500.0000
CPU min MHz: 1250.0000
L1d cache: 32K
L1i cache: 64K
L2 cache: 1024K
NUMA node0 CPU(s): 0-3
Linux debian 4.9.67 #1 SMP Sat Dec 9 12:20:20 CET 2017 ppc64 GNU/Linux
gcc (Debian 7.2.0-19) 7.2.0
Da: Qemu-ppc <qemu-ppc-bounces+address@hidden> per conto di David Gibson <address@hidden>
Inviato: martedì 9 gennaio 2018 13:16
A: Peter Maydell
Cc: Michael Roth; QEMU Developers; address@hidden; Greg Kurz; address@hidden
Oggetto: Re: [Qemu-ppc] [PULL 00/12] ppc-for-2.12 queue 20180108
On Tue, Jan 09, 2018 at 11:46:41AM +0000, Peter Maydell wrote:
> 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. Even if you can identify which patch it is and we can
postpone that one would be a bug help.
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
|[Prev in Thread]||Current Thread||[Next in Thread]|