• G
    spapr: fix device tree properties when using compatibility mode · 9012a53f
    Greg Kurz 提交于
    Commit 51f84465 changed the compatility mode setting logic:
    - machine reset only sets compatibility mode for the boot CPU
    - compatibility mode is set for other CPUs when they are put online
      by the guest with the "start-cpu" RTAS call
    
    This causes a regression for machines started with max-compat-cpu:
    the device tree nodes related to secondary CPU cores contain wrong
    "cpu-version" and "ibm,pa-features" values, as shown below.
    
    Guest started on a POWER8 host with:
         -smp cores=2 -machine pseries,max-cpu-compat=compat7
    
                            ibm,pa-features = [18 00 f6 3f c7 c0 80 f0 80 00
     00 00 00 00 00 00 00 00 80 00 80 00 80 00 00 00];
                            cpu-version = <0x4d0200>;
    
                                   ^^^
                            second CPU core
    
                            ibm,pa-features = <0x600f63f 0xc70080c0>;
                            cpu-version = <0xf000003>;
    
                                   ^^^
                              boot CPU core
    
    The second core is advertised in raw POWER8 mode. This happens because
    CAS assumes all CPUs to have the same compatibility mode. Since the
    boot CPU already has the requested compatibility mode, the CAS code
    does not set it for the secondary one, and exposes the bogus device
    tree properties in in the CAS response to the guest.
    
    A similar situation is observed when hot-plugging a CPU core. The
    related device tree properties are generated and exposed to guest
    with the "ibm,configure-connector" RTAS before "start-cpu" is called.
    The CPU core is advertised to the guest in raw mode as well.
    
    It both cases, it boils down to the fact that "start-cpu" happens too
    late. This can be fixed globally by propagating the compatibility mode
    of the boot CPU to the other CPUs during reset.  For this to work, the
    compatibility mode of the boot CPU must be set before the machine code
    actually resets all CPUs.
    
    It is not needed to set the compatibility mode in "start-cpu" anymore,
    so the code is dropped.
    
    Fixes: 51f84465Signed-off-by: NGreg Kurz <groug@kaod.org>
    Signed-off-by: NDavid Gibson <david@gibson.dropbear.id.au>
    9012a53f
spapr.c 134.9 KB