[Qemu-commits] [qemu/qemu] a4c379: spapr/rtas: Print message from "ibm, os-term"

[Peter Maydell]

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: a4c3791ae0c4a2e1f5d91f078bc9ad6e5d58867e
      
https://github.com/qemu/qemu/commit/a4c3791ae0c4a2e1f5d91f078bc9ad6e5d58867e
  Author: Alexey Kardashevskiy <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/ppc/spapr_rtas.c

  Log Message:
  -----------
  spapr/rtas: Print message from "ibm,os-term"

The "ibm,os-term" RTAS call has a single parameter which is a pointer to
a message from the guest kernel about the termination cause; this prints
it.

Signed-off-by: Alexey Kardashevskiy <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Daniel Henrique Barboza <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 2c6e918ef8a101d86e0592051a1ee4bf493a6785
      
https://github.com/qemu/qemu/commit/2c6e918ef8a101d86e0592051a1ee4bf493a6785
  Author: Laurent Vivier <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M qtest.c

  Log Message:
  -----------
  qtest: Fix rtas dependencies

qtest "rtas" command is only available with pseries not all ppc64 targets,
so if I try to compile only powernv machine, the build fails with:

  /usr/bin/ld: qtest.o: in function `qtest_process_command':
  .../qtest.c:645: undefined reference to `qtest_rtas_call'

We fix this by enabling rtas command only with pseries machine.

Fixes: eeddd59f5962 ("tests: add RTAS command in the protocol")
Signed-off-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 90118a657ce88a003f20f24ca65db96bba8be7a9
      
https://github.com/qemu/qemu/commit/90118a657ce88a003f20f24ca65db96bba8be7a9
  Author: Laurent Vivier <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/ppc/Kconfig

  Log Message:
  -----------
  ppc/pnv: Fix PCI_EXPRESS dependency

When PHB4 bridge has been added, the dependencies to PCIE_PORT has been
added to XIVE_SPAPR and indirectly to PSERIES.
The build of the PowerNV machine is fine while we also build the PSERIES
machine.
If we disable the PSERIES machine, the PowerNV build fails because the
PCI Express files are not built:

/usr/bin/ld: hw/ppc/pnv.o: in function `pnv_chip_power8_pic_print_info':
.../hw/ppc/pnv.c:623: undefined reference to `pnv_phb3_msi_pic_print_info'
/usr/bin/ld: hw/ppc/pnv.o: in function `pnv_chip_power9_pic_print_info':
.../hw/ppc/pnv.c:639: undefined reference to `pnv_phb4_pic_print_info'
/usr/bin/ld: ../hw/usb/hcd-ehci-pci.o: in function `usb_ehci_pci_write_config':
.../hw/usb/hcd-ehci-pci.c:129: undefined reference to `pci_default_write_config'
/usr/bin/ld: ../hw/usb/hcd-ehci-pci.o: in function `usb_ehci_pci_realize':
.../hw/usb/hcd-ehci-pci.c:68: undefined reference to `pci_allocate_irq'
/usr/bin/ld: .../hw/usb/hcd-ehci-pci.c:72: undefined reference to 
`pci_register_bar'
/usr/bin/ld: ../hw/usb/hcd-ehci-pci.o:(.data.rel+0x50): undefined reference to 
`vmstate_pci_device'

This patch fixes the problem by adding needed dependencies to POWERNV.

Fixes: 4f9924c4d4cf ("ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge")
Signed-off-by: Laurent Vivier <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: a78492681995ad4b46a2b6e30bb36935dff5ffb1
      
https://github.com/qemu/qemu/commit/a78492681995ad4b46a2b6e30bb36935dff5ffb1
  Author: Michael S. Tsirkin <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/ppc/spapr.c

  Log Message:
  -----------
  ppc: function to setup latest class options

We are going to add more init for the latest machine, so move the setup
to a function so we don't have to change the DEFINE_SPAPR_MACHINE macro
each time.

Signed-off-by: Michael S. Tsirkin <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Laurent Vivier <address@hidden>
Reviewed-by: Greg Kurz <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 3f350f6bb36233be50fc2bc18dc78b6a948a5dbe
      
https://github.com/qemu/qemu/commit/3f350f6bb36233be50fc2bc18dc78b6a948a5dbe
  Author: Shivaprasad G Bhat <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/acpi/nvdimm.c
    A include/qemu/nvdimm-utils.h
    M util/Makefile.objs
    A util/nvdimm-utils.c

  Log Message:
  -----------
  mem: move nvdimm_device_list to utilities

nvdimm_device_list is required for parsing the list for devices
in subsequent patches. Move it to common utility area.

Signed-off-by: Shivaprasad G Bhat <address@hidden>
Reviewed-by: Igor Mammedov <address@hidden>
Reviewed-by: David Gibson <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 6c5627bb24dcd68c997857a8b671617333b1289f
      
https://github.com/qemu/qemu/commit/6c5627bb24dcd68c997857a8b671617333b1289f
  Author: Shivaprasad G Bhat <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/mem/nvdimm.c
    M include/hw/mem/nvdimm.h

  Log Message:
  -----------
  nvdimm: add uuid property to nvdimm

For ppc64, PAPR requires the nvdimm device to have UUID property
set in the device tree. Add an option to get it from the user.

Signed-off-by: Shivaprasad G Bhat <address@hidden>
Reviewed-by: David Gibson <address@hidden>
Reviewed-by: Igor Mammedov <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: ee3a71e36654317b14ede0290e87628f8b79f850
      
https://github.com/qemu/qemu/commit/ee3a71e36654317b14ede0290e87628f8b79f850
  Author: Shivaprasad G Bhat <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M default-configs/ppc64-softmmu.mak
    M hw/mem/Kconfig
    M hw/ppc/Makefile.objs
    M hw/ppc/spapr.c
    M hw/ppc/spapr_drc.c
    M hw/ppc/spapr_events.c
    A hw/ppc/spapr_nvdimm.c
    M include/hw/ppc/spapr_drc.h
    A include/hw/ppc/spapr_nvdimm.h

  Log Message:
  -----------
  spapr: Add NVDIMM device support

Add support for NVDIMM devices for sPAPR. Piggyback on existing nvdimm
device interface in QEMU to support virtual NVDIMM devices for Power.
Create the required DT entries for the device (some entries have
dummy values right now).

The patch creates the required DT node and sends a hotplug
interrupt to the guest. Guest is expected to undertake the normal
DR resource add path in response and start issuing PAPR SCM hcalls.

The device support is verified based on the machine version unlike x86.

This is how it can be used ..
Ex :
For coldplug, the device to be added in qemu command line as shown below
-object 
memory-backend-file,id=memnvdimm0,prealloc=yes,mem-path=/tmp/nvdimm0,share=yes,size=1073872896
-device 
nvdimm,label-size=128k,uuid=75a3cdd7-6a2f-4791-8d15-fe0a920e8e9e,memdev=memnvdimm0,id=nvdimm0,slot=0

For hotplug, the device to be added from monitor as below
object_add 
memory-backend-file,id=memnvdimm0,prealloc=yes,mem-path=/tmp/nvdimm0,share=yes,size=1073872896
device_add 
nvdimm,label-size=128k,uuid=75a3cdd7-6a2f-4791-8d15-fe0a920e8e9e,memdev=memnvdimm0,id=nvdimm0,slot=0

Signed-off-by: Shivaprasad G Bhat <address@hidden>
Signed-off-by: Bharata B Rao <address@hidden>
               [Early implementation]
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: b5fca656f7011ca56fdfa93160c4296db9e3f4d9
      
https://github.com/qemu/qemu/commit/b5fca656f7011ca56fdfa93160c4296db9e3f4d9
  Author: Shivaprasad G Bhat <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/ppc/spapr_nvdimm.c
    M include/hw/ppc/spapr.h

  Log Message:
  -----------
  spapr: Add Hcalls to support PAPR NVDIMM device

This patch implements few of the necessary hcalls for the nvdimm support.

PAPR semantics is such that each NVDIMM device is comprising of multiple
SCM(Storage Class Memory) blocks. The guest requests the hypervisor to
bind each of the SCM blocks of the NVDIMM device using hcalls. There can
be SCM block unbind requests in case of driver errors or unplug(not
supported now) use cases. The NVDIMM label read/writes are done through
hcalls.

Since each virtual NVDIMM device is divided into multiple SCM blocks,
the bind, unbind, and queries using hcalls on those blocks can come
independently. This doesn't fit well into the qemu device semantics,
where the map/unmap are done at the (whole)device/object level granularity.
The patch doesnt actually bind/unbind on hcalls but let it happen at the
device_add/del phase itself instead.

The guest kernel makes bind/unbind requests for the virtual NVDIMM device
at the region level granularity. Without interleaving, each virtual NVDIMM
device is presented as a separate guest physical address range. So, there
is no way a partial bind/unbind request can come for the vNVDIMM in a
hcall for a subset of SCM blocks of a virtual NVDIMM. Hence it is safe to
do bind/unbind everything during the device_add/del.

Signed-off-by: Shivaprasad G Bhat <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 19b5c4186eccc519e6906838b288b2e206d43efe
      
https://github.com/qemu/qemu/commit/19b5c4186eccc519e6906838b288b2e206d43efe
  Author: BALATON Zoltan <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M target/ppc/cpu.h

  Log Message:
  -----------
  target/ppc/cpu.h: Remove duplicate includes

Commit 74433bf083b added some includes but added them twice. Since
these are guarded against multiple inclusion including them once is
enough.

Signed-off-by: BALATON Zoltan <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Philippe Mathieu-Daudé <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 5a205fcf7700abe442b374d76a8c4edea92eecc7
      
https://github.com/qemu/qemu/commit/5a205fcf7700abe442b374d76a8c4edea92eecc7
  Author: Greg Kurz <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/pci-host/pnv_phb3_msi.c

  Log Message:
  -----------
  pnv/phb3: Convert 1u to 1ull

As reported by Coverity defect CID 1419397, the 'j' variable goes up to
63 and shouldn't be used to left shift a 32-bit integer.

The result of the operation goes to a 64-bit integer : use a 64-bit
constant.

Reported-by: Coverity CID 1419397 Bad bit shift operation
Fixes: 9ae1329ee2fe "ppc/pnv: Add models for POWER8 PHB3 PCIe Host bridge"
Signed-off-by: Greg Kurz <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 7cfb999fe9c80c72f3f76043ce1bf8dee0c020af
      
https://github.com/qemu/qemu/commit/7cfb999fe9c80c72f3f76043ce1bf8dee0c020af
  Author: Greg Kurz <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/pci-host/pnv_phb4_pec.c

  Log Message:
  -----------
  pnv/phb4: Fix error path in pnv_pec_realize()

Obviously, we want to pass &local_err so that we can check it then
line below, not errp.

Reported-by: Coverity CID 1419395 'Constant' variable guards dead code
Fixes: 4f9924c4d4cf "ppc/pnv: Add models for POWER9 PHB4 PCIe Host bridge"
Signed-off-by: Greg Kurz <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: e8ead7d579645a1866813ce563882cad055088b9
      
https://github.com/qemu/qemu/commit/e8ead7d579645a1866813ce563882cad055088b9
  Author: Greg Kurz <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/pci-host/pnv_phb3_pbcq.c

  Log Message:
  -----------
  pnv/phb3: Add missing break statement

We obviously don't want to print out an error message if addr points to
a valid register.

Reported-by: Coverity CID 1419391 Missing break in switch
Fixes: 9ae1329ee2fe "ppc/pnv: Add models for POWER8 PHB3 PCIe Host bridge"
Signed-off-by: Greg Kurz <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 87262806cb48c247ae55d99e280ba96027648c2d
      
https://github.com/qemu/qemu/commit/87262806cb48c247ae55d99e280ba96027648c2d
  Author: Alexey Kardashevskiy <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/ppc/spapr.c
    M include/hw/ppc/spapr.h

  Log Message:
  -----------
  spapr: Allow changing offset for -kernel image

This allows moving the kernel in the guest memory. The option is useful
for step debugging (as Linux is linked at 0x0); it also allows loading
grub which is normally linked to run at 0x20000.

This uses the existing kernel address by default.

Signed-off-by: Alexey Kardashevskiy <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Fabiano Rosas <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 92eeb004e8832d0020be056eff722702eafde4dc
      
https://github.com/qemu/qemu/commit/92eeb004e8832d0020be056eff722702eafde4dc
  Author: BALATON Zoltan <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M target/ppc/fpu_helper.c
    M target/ppc/translate/fp-impl.inc.c

  Log Message:
  -----------
  target/ppc: Fix typo in comments

"Deferred" was misspelled as "differed" in some comments, correct this
typo,

Signed-off-by: BALATON Zoltan <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: b561615db2fcdb2c3710cf0a0b2757b56bda922e
      
https://github.com/qemu/qemu/commit/b561615db2fcdb2c3710cf0a0b2757b56bda922e
  Author: BALATON Zoltan <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M target/ppc/cpu.h

  Log Message:
  -----------
  target/ppc/cpu.h: Move fpu related members closer in cpu env

Move fp_status and fpscr closer to other floating point and vector
related members in cpu env definition so they are in one group.

Signed-off-by: BALATON Zoltan <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: ad5db2e732c0ed532fe852a2ccf15ab637cb2366
      
https://github.com/qemu/qemu/commit/ad5db2e732c0ed532fe852a2ccf15ab637cb2366
  Author: BALATON Zoltan <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M target/ppc/cpu.h

  Log Message:
  -----------
  target/ppc/cpu.h: Clean up comments in the struct CPUPPCState definition

The cpu env struct is quite complex but comments supposed to explain
it in its definition just make it harder to read. Reformat and reword
some comments to make it clearer and more readable.

Signed-off-by: BALATON Zoltan <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: b2fb7a4368ba99173c9dbf084aa5a7f04cc8bb8e
      
https://github.com/qemu/qemu/commit/b2fb7a4368ba99173c9dbf084aa5a7f04cc8bb8e
  Author: Pan Nengyuan <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/ppc/e500.c
    M hw/ppc/pnv.c

  Log Message:
  -----------
  ppc: free 'fdt' after reset the machine

'fdt' forgot to clean both e500 and pnv when we call 'system_reset' on ppc,
this patch fix it. The leak stacks are as follow:

Direct leak of 4194304 byte(s) in 4 object(s) allocated from:
    #0 0x7fafe37dd970 in __interceptor_calloc (/lib64/libasan.so.5+0xef970)
    #1 0x7fafe2e3149d in g_malloc0 (/lib64/libglib-2.0.so.0+0x5249d)
    #2 0x561876f7f80d in create_device_tree 
/mnt/sdb/qemu-new/qemu/device_tree.c:40
    #3 0x561876b7ac29 in ppce500_load_device_tree 
/mnt/sdb/qemu-new/qemu/hw/ppc/e500.c:364
    #4 0x561876b7f437 in ppce500_reset_device_tree 
/mnt/sdb/qemu-new/qemu/hw/ppc/e500.c:617
    #5 0x56187718b1ae in qemu_devices_reset 
/mnt/sdb/qemu-new/qemu/hw/core/reset.c:69
    #6 0x561876f6938d in qemu_system_reset /mnt/sdb/qemu-new/qemu/vl.c:1412
    #7 0x561876f6a25b in main_loop_should_exit /mnt/sdb/qemu-new/qemu/vl.c:1645
    #8 0x561876f6a398 in main_loop /mnt/sdb/qemu-new/qemu/vl.c:1679
    #9 0x561876f7da8e in main /mnt/sdb/qemu-new/qemu/vl.c:4438
    #10 0x7fafde16b812 in __libc_start_main ../csu/libc-start.c:308
    #11 0x5618765c055d in _start 
(/mnt/sdb/qemu-new/qemu/build/ppc64-softmmu/qemu-system-ppc64+0x2b1555d)

Direct leak of 1048576 byte(s) in 1 object(s) allocated from:
    #0 0x7fc0a6f1b970 in __interceptor_calloc (/lib64/libasan.so.5+0xef970)
    #1 0x7fc0a656f49d in g_malloc0 (/lib64/libglib-2.0.so.0+0x5249d)
    #2 0x55eb05acd2ca in pnv_dt_create /mnt/sdb/qemu-new/qemu/hw/ppc/pnv.c:507
    #3 0x55eb05ace5bf in pnv_reset /mnt/sdb/qemu-new/qemu/hw/ppc/pnv.c:578
    #4 0x55eb05f2f395 in qemu_system_reset /mnt/sdb/qemu-new/qemu/vl.c:1410
    #5 0x55eb05f43850 in main /mnt/sdb/qemu-new/qemu/vl.c:4403
    #6 0x7fc0a18a9812 in __libc_start_main ../csu/libc-start.c:308
    #7 0x55eb0558655d in _start 
(/mnt/sdb/qemu-new/qemu/build/ppc64-softmmu/qemu-system-ppc64+0x2b1555d)

Reported-by: Euler Robot <address@hidden>
Signed-off-by: Pan Nengyuan <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Greg Kurz <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 4b63db1289a9e597bc151fa5e4d72f882cb6de1e
      
https://github.com/qemu/qemu/commit/4b63db1289a9e597bc151fa5e4d72f882cb6de1e
  Author: Greg Kurz <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/ppc/spapr_drc.c
    M hw/ppc/spapr_hcall.c
    M include/hw/ppc/spapr_drc.h

  Log Message:
  -----------
  spapr: Don't use spapr_drc_needed() in CAS code

We currently don't support hotplug of devices between boot and CAS. If
this happens a CAS reboot is triggered. We detect this during CAS using
the spapr_drc_needed() function which is essentially a VMStateDescription
.needed callback. Even if the condition for CAS reboot happens to be the
same as for DRC migration, it looks wrong to piggyback a migration helper
for this.

Introduce a helper with slightly more explicit name and use it in both CAS
and DRC migration code. Since a subsequent patch will enhance this helper
to cover the case of hot unplug, let's go for spapr_drc_transient(). While
here convert spapr_hotplugged_dev_before_cas() to the "transient" wording as
well.

This doesn't change any behaviour.

Signed-off-by: Greg Kurz <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: ab8584349c476f9818dc6403359c85f9ab0ad5eb
      
https://github.com/qemu/qemu/commit/ab8584349c476f9818dc6403359c85f9ab0ad5eb
  Author: Greg Kurz <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/ppc/spapr_drc.c

  Log Message:
  -----------
  spapr: Fix handling of unplugged devices during CAS and migration

We already detect if a device is being hot plugged before CAS to trigger
a CAS reboot and during migration to migrate the state of the associated
DRC. But hot unplugging a device is also an asynchronous operation that
requires the guest to take action. This means that if the guest is migrated
after the hot unplug event was sent but before it could release the device
with RTAS, the destination QEMU doesn't know about the pending unplug
operation and doesn't actually remove the device when the guest finally
releases it.

Similarly, if the unplug request is fired before CAS, the guest isn't
notified of the change, just like with hotplug. It ends up booting with
the device still present in the DT and configures it, just like it was
never removed. Even weirder, since the event is still queued, it will
be eventually processed when some other unrelated event is posted to
the guest.

Enhance spapr_drc_transient() to also return true if an unplug request is
pending. This fixes the issue at CAS with a CAS reboot request and
causes the DRC state to be migrated. Some extra care is still needed to
inform the destination that an unplug request is pending : migrate the
unplug_requested field of the DRC in an optional subsection. This might
break backwards migration, but this is still better than ending with
an inconsistent guest.

Signed-off-by: Greg Kurz <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: 438bafcac55308eef4f9029c94dbadd2c7ac3bb7
      
https://github.com/qemu/qemu/commit/438bafcac55308eef4f9029c94dbadd2c7ac3bb7
  Author: Chen Qun <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M hw/ppc/virtex_ml507.c

  Log Message:
  -----------
  hw/ppc/virtex_ml507:fix leak of fdevice tree blob

The device tree blob returned by load_device_tree is malloced.
We should free it after cpu_physical_memory_write().

Reported-by: Euler Robot <address@hidden>
Signed-off-by: Chen Qun <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: David Gibson <address@hidden>


  Commit: a8c6af67e1e8d460e2c6e87070807e0a02c0fec2
      
https://github.com/qemu/qemu/commit/a8c6af67e1e8d460e2c6e87070807e0a02c0fec2
  Author: Peter Maydell <address@hidden>
  Date:   2020-02-21 (Fri, 21 Feb 2020)

  Changed paths:
    M default-configs/ppc64-softmmu.mak
    M hw/acpi/nvdimm.c
    M hw/mem/Kconfig
    M hw/mem/nvdimm.c
    M hw/pci-host/pnv_phb3_msi.c
    M hw/pci-host/pnv_phb3_pbcq.c
    M hw/pci-host/pnv_phb4_pec.c
    M hw/ppc/Kconfig
    M hw/ppc/Makefile.objs
    M hw/ppc/e500.c
    M hw/ppc/pnv.c
    M hw/ppc/spapr.c
    M hw/ppc/spapr_drc.c
    M hw/ppc/spapr_events.c
    M hw/ppc/spapr_hcall.c
    A hw/ppc/spapr_nvdimm.c
    M hw/ppc/spapr_rtas.c
    M hw/ppc/virtex_ml507.c
    M include/hw/mem/nvdimm.h
    M include/hw/ppc/spapr.h
    M include/hw/ppc/spapr_drc.h
    A include/hw/ppc/spapr_nvdimm.h
    A include/qemu/nvdimm-utils.h
    M qtest.c
    M target/ppc/cpu.h
    M target/ppc/fpu_helper.c
    M target/ppc/translate/fp-impl.inc.c
    M util/Makefile.objs
    A util/nvdimm-utils.c

  Log Message:
  -----------
  Merge remote-tracking branch 'remotes/dgibson/tags/ppc-for-5.0-20200221' into 
staging

ppc patch queue 2020-02-21

Here's the next patch of ppc target patches.  Highlights are:
  * Some fixes for CAS / unplug interactions
  * Remove some leaks of device trees
  * Some fixes for the PHB3 and PHB4 devices
  * Support for NVDIMMs on the pseries machine type
  * Assorted other fixes and cleanups

# gpg: Signature made Fri 21 Feb 2020 03:35:40 GMT
# gpg:                using RSA key 75F46586AE61A66CC44E87DC6C38CACA20D9B392
# gpg: Good signature from "David Gibson <address@hidden>" [full]
# gpg:                 aka "David Gibson (Red Hat) <address@hidden>" [full]
# gpg:                 aka "David Gibson (ozlabs.org) <address@hidden>" [full]
# gpg:                 aka "David Gibson (kernel.org) <address@hidden>" 
[unknown]
# Primary key fingerprint: 75F4 6586 AE61 A66C C44E  87DC 6C38 CACA 20D9 B392

* remotes/dgibson/tags/ppc-for-5.0-20200221:
  hw/ppc/virtex_ml507:fix leak of fdevice tree blob
  spapr: Fix handling of unplugged devices during CAS and migration
  spapr: Don't use spapr_drc_needed() in CAS code
  ppc: free 'fdt' after reset the machine
  target/ppc/cpu.h: Clean up comments in the struct CPUPPCState definition
  target/ppc/cpu.h: Move fpu related members closer in cpu env
  target/ppc: Fix typo in comments
  spapr: Allow changing offset for -kernel image
  pnv/phb3: Add missing break statement
  pnv/phb4: Fix error path in pnv_pec_realize()
  pnv/phb3: Convert 1u to 1ull
  target/ppc/cpu.h: Remove duplicate includes
  spapr: Add Hcalls to support PAPR NVDIMM device
  spapr: Add NVDIMM device support
  nvdimm: add uuid property to nvdimm
  mem: move nvdimm_device_list to utilities
  ppc: function to setup latest class options
  ppc/pnv: Fix PCI_EXPRESS dependency
  qtest: Fix rtas dependencies
  spapr/rtas: Print message from "ibm,os-term"

Signed-off-by: Peter Maydell <address@hidden>


Compare: https://github.com/qemu/qemu/compare/9e6b7f7eb895...a8c6af67e1e8