Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: f41d912023e777d95e782a1ade6338c5fed8b842
      
https://github.com/qemu/qemu/commit/f41d912023e777d95e782a1ade6338c5fed8b842
  Author: Michael S. Tsirkin <m...@redhat.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M hw/virtio/trace-events
    M hw/virtio/vhost.c

  Log Message:
  -----------
  Revert "vhost: add traces for memory listeners"

This reverts commit 0750b060216de69ed1f14bc08181bf4ad27fc622.

Follow up patches are reworking the memory listeners, the new mechanism
will add its own set of traces.

Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: 76143618a5a9f33e8bc968f27b3de79d79a286c5
      
https://github.com/qemu/qemu/commit/76143618a5a9f33e8bc968f27b3de79d79a286c5
  Author: Gal Hammer <gham...@redhat.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M hw/block/dataplane/virtio-blk.c
    M hw/scsi/virtio-scsi-dataplane.c
    M hw/virtio/vhost.c
    M hw/virtio/virtio-bus.c
    M hw/virtio/virtio.c
    M include/hw/virtio/virtio-bus.h

  Log Message:
  -----------
  virtio: remove event notifier cleanup call on de-assign

The virtio_bus_set_host_notifier function no longer calls
event_notifier_cleanup when a event notifier is removed.

The commit updates the code to match the new behavior and calls
virtio_bus_cleanup_host_notifier after the notifier was de-assign
and no longer in use.

This change is a preparation to allow executing the
virtio_bus_set_host_notifier function in a memory region
transaction.

Signed-off-by: Gal Hammer <gham...@redhat.com>
Reviewed-by: Greg Kurz <gr...@kaod.org>
Tested-by: Greg Kurz <gr...@kaod.org>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: 710fccf80d787911120145f508f9c4c664cf0e03
      
https://github.com/qemu/qemu/commit/710fccf80d787911120145f508f9c4c664cf0e03
  Author: Gal Hammer <gham...@redhat.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M hw/virtio/virtio.c

  Log Message:
  -----------
  virtio: improve virtio devices initialization time

The loading time of a VM is quite significant when its virtio
devices use a large amount of virt-queues (e.g. a virtio-serial
device with max_ports=511). Most of the time is spend in the
creation of all the required event notifiers (ioeventfd and memory
regions).

This patch pack all the changes to the memory regions in a
single memory transaction.

Reported-by: Sitong Liu
Reported-by: Xiaoling Gao
Signed-off-by: Gal Hammer <gham...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>
Reviewed-by: Greg Kurz <gr...@kaod.org>
Tested-by: Greg Kurz <gr...@kaod.org>


  Commit: c44317efecb240b9b0951ad46ba56eb547114f1d
      
https://github.com/qemu/qemu/commit/c44317efecb240b9b0951ad46ba56eb547114f1d
  Author: Dr. David Alan Gilbert <dgilb...@redhat.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M hw/virtio/vhost.c
    M include/hw/virtio/vhost.h

  Log Message:
  -----------
  vhost: Build temporary section list and deref after commit

Igor spotted that there's a race, where a region that's unref'd
in a _del callback might be free'd before the set_mem_table call in
the _commit callback, and thus the vhost might end up using free memory.

Fix this by building a complete temporary sections list, ref'ing every
section (during add and nop) and then unref'ing the whole list right
at the end of commit.

Signed-off-by: Dr. David Alan Gilbert <dgilb...@redhat.com>
Reviewed-by: Igor Mammedov <imamm...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: 0ca1fd2d6878a360c9e3b5be6b0bbe5d3143280e
      
https://github.com/qemu/qemu/commit/0ca1fd2d6878a360c9e3b5be6b0bbe5d3143280e
  Author: Dr. David Alan Gilbert <dgilb...@redhat.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M hw/virtio/vhost.c

  Log Message:
  -----------
  vhost: Simplify ring verification checks

vhost_verify_ring_mappings() were used to verify that
rings are still accessible and related memory hasn't
been moved after flatview is updated.

It was doing checks by mapping ring's GPA+len and
checking that HVA hadn't changed with new memory map.
To avoid maybe expensive mapping call, we were
identifying address range that changed and were doing
mapping only if ring was in changed range.

However it's not neccessary to perform ring's GPA
mapping as we already have its current HVA and all
we need is to verify that ring's GPA translates to
the same HVA in updated flatview.

This will allow the following patches to simplify the range
comparison that was previously needed to avoid expensive
verify_ring_mapping calls.

Signed-off-by: Igor Mammedov <imamm...@redhat.com>
with modifications by:
Signed-off-by: Dr. David Alan Gilbert <dgilb...@redhat.com>
Reviewed-by: Igor Mammedov <imamm...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: 48d7c97577498657f9ccbcbf1f990fdb4b79501f
      
https://github.com/qemu/qemu/commit/48d7c97577498657f9ccbcbf1f990fdb4b79501f
  Author: Dr. David Alan Gilbert <dgilb...@redhat.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M hw/virtio/trace-events
    M hw/virtio/vhost.c

  Log Message:
  -----------
  vhost: Merge sections added to temporary list

As sections are reported by the listener to the _nop and _add
methods, add them to the temporary section list but now merge them
with the previous section if the new one abuts and the backend allows.

Signed-off-by: Dr. David Alan Gilbert <dgilb...@redhat.com>
Reviewed-by: Igor Mammedov <imamm...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: ade6d081fc33948e56e655ee37b1306b6de6e0ef
      
https://github.com/qemu/qemu/commit/ade6d081fc33948e56e655ee37b1306b6de6e0ef
  Author: Dr. David Alan Gilbert <dgilb...@redhat.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M hw/virtio/trace-events
    M hw/virtio/vhost.c

  Log Message:
  -----------
  vhost: Regenerate region list from changed sections list

Compare the sections list that's just been generated, and if it's
different from the old one regenerate the region list.

Signed-off-by: Dr. David Alan Gilbert <dgilb...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>
Reviewed-by: Igor Mammedov <imamm...@redhat.com>


  Commit: 06709c120ca3bae9fa243783b89005c08b71a440
      
https://github.com/qemu/qemu/commit/06709c120ca3bae9fa243783b89005c08b71a440
  Author: Dr. David Alan Gilbert <dgilb...@redhat.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M hw/virtio/vhost.c
    M include/hw/virtio/vhost.h

  Log Message:
  -----------
  vhost: Clean out old vhost_set_memory and friends

Remove the old update mechanism, vhost_set_memory, and the functions
and flags it used.

Signed-off-by: Dr. David Alan Gilbert <dgilb...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: 938eeb640c0a006a3a53ea6f8b409cad56b80a55
      
https://github.com/qemu/qemu/commit/938eeb640c0a006a3a53ea6f8b409cad56b80a55
  Author: Dr. David Alan Gilbert <dgilb...@redhat.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M hw/virtio/vhost.c

  Log Message:
  -----------
  vhost: Merge and delete unused callbacks

Now that the olf vhost_set_memory code is gone, the _nop and _add
callbacks are identical and can be merged.  The _del callback is
no longer needed.

Signed-off-by: Dr. David Alan Gilbert <dgilb...@redhat.com>
Reviewed-by: Igor Mammedov <imamm...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: aa3c40f6bfae251a483b5c19f5ceb8e11bdbdb18
      
https://github.com/qemu/qemu/commit/aa3c40f6bfae251a483b5c19f5ceb8e11bdbdb18
  Author: Dr. David Alan Gilbert <dgilb...@redhat.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M hw/virtio/trace-events
    M hw/virtio/vhost.c

  Log Message:
  -----------
  vhost: Move log_dirty check

Move the log_dirty check into vhost_section.

Signed-off-by: Dr. David Alan Gilbert <dgilb...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: ed247f40db84c8bd4bb7d10948702cd47cc4d5ae
      
https://github.com/qemu/qemu/commit/ed247f40db84c8bd4bb7d10948702cd47cc4d5ae
  Author: Laszlo Ersek <ler...@redhat.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M hw/pci-bridge/i82801b11.c

  Log Message:
  -----------
  pci-bridge/i82801b11: clear bridge registers on platform reset

The "i82801b11-bridge" device model is a descendant of "base-pci-bridge"
(TYPE_PCI_BRIDGE). However, unlike other similar devices, such as

- pci-bridge,
- pcie-pci-bridge,
- PCIE Root Port,
- xio3130 switch upstream and downstream ports,
- dec-21154-p2p-bridge,
- pbm-bridge,
- xilinx-pcie-root,

"i82801b11-bridge" does not clear the bridge specific registers at
platform reset.

This is a problem because devices on "i82801b11-bridge" continue to
respond to config space cycles after platform reset, when addressed with
the bus number that was previously programmed into the secondary bus
number register of "i82801b11-bridge". This error breaks OVMF's search for
extra (PXB) root buses, for example.

The device class reset method for "i82801b11-bridge" is currently NULL;
set it directly to pci_bridge_reset(), like the last three bridge models
in the above listing do.

Cc: "Michael S. Tsirkin" <m...@redhat.com>
Cc: Marcel Apfelbaum <mar...@redhat.com>
Cc: qemu-sta...@nongnu.org
Ref: https://bugzilla.redhat.com/show_bug.cgi?id=1541839
Signed-off-by: Laszlo Ersek <ler...@redhat.com>
Reviewed-by: Marcel Apfelbaum <mar...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: 9d6b9db19c4b99ce5a1ad75b490c01edd2c2b0cf
      
https://github.com/qemu/qemu/commit/9d6b9db19c4b99ce5a1ad75b490c01edd2c2b0cf
  Author: Peter Xu <pet...@redhat.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M hw/pci-bridge/gen_pcie_root_port.c
    M hw/pci-bridge/i82801b11.c
    M hw/pci-bridge/ioh3420.c
    M hw/pci-bridge/pci_bridge_dev.c
    M hw/pci-bridge/pcie_pci_bridge.c
    M hw/pci-bridge/xio3130_downstream.c
    M hw/pci-bridge/xio3130_upstream.c
    M include/migration/vmstate.h

  Log Message:
  -----------
  pci/bus: let it has higher migration priority

In the past, we prioritized IOMMU migration so that we have such a
priority order:

    IOMMU > PCI Devices

When migrating a guest with both vIOMMU and a pcie-root-port, we'll
always migrate vIOMMU first, since pci buses will be seen to have the
same priority of general PCI devices.

That's problematic.

The thing is that PCI bus number information is stored in the root port,
and that is needed by vIOMMU during post_load(), e.g., to figure out
context entry for a device.  If we don't have correct bus numbers for
devices, we won't be able to recover device state of the DMAR memory
regions, and things will be messed up.

So let's boost the PCIe root ports to be even with higher priority:

   PCIe Root Port > IOMMU > PCI Devices

A smoke test shows that this patch fixes bug 1538953.

Also, apply this rule to all the PCI bus/bridge devices: ioh3420,
xio3130_downstream, xio3130_upstream, pcie_pci_bridge, pci-pci bridge,
i82801b11.

I noted that we set pcie_pci_bridge_dev_vmstate twice.  Clean that up
together.

CC: Alex Williamson <alex.william...@redhat.com>
CC: Marcel Apfelbaum <mar...@redhat.com>
CC: Michael S. Tsirkin <m...@redhat.com>
CC: Dr. David Alan Gilbert <dgilb...@redhat.com>
CC: Juan Quintela <quint...@redhat.com>
CC: Laurent Vivier <lviv...@redhat.com>
Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1538953
Reported-by: Maxime Coquelin <maxime.coque...@redhat.com>
Signed-off-by: Peter Xu <pet...@redhat.com>
Reviewed-by: Marcel Apfelbaum <mar...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: 0ebf9a748881fa85491501f0fa3ca5aec79b7afc
      
https://github.com/qemu/qemu/commit/0ebf9a748881fa85491501f0fa3ca5aec79b7afc
  Author: Changpeng Liu <changpeng....@intel.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M hw/virtio/virtio-pci.c
    M include/hw/compat.h

  Log Message:
  -----------
  virtio-blk: enable multiple vectors when using multiple I/O queues

Currently virtio-pci driver hardcoded 2 vectors for virtio-blk device,
for multiple I/O queues scenario, all the I/O queues will share one
interrupt vector, while here, enable multiple vectors according to
the number of I/O queues.

Signed-off-by: Changpeng Liu <changpeng....@intel.com>
Reviewed-by: Paolo Bonzini <pbonz...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: d61a363d3e801fcfdba0767ba0f2b44cd458be37
      
https://github.com/qemu/qemu/commit/d61a363d3e801fcfdba0767ba0f2b44cd458be37
  Author: Yoni Bettan <ybet...@redhat.com>
  Date:   2018-02-08 (Thu, 08 Feb 2018)

  Changed paths:
    M docs/pcie_pci_bridge.txt
    M hw/block/nvme.c
    M hw/net/e1000e.c
    M hw/pci-bridge/pcie_pci_bridge.c
    M hw/pci-bridge/pcie_root_port.c
    M hw/pci-bridge/xio3130_downstream.c
    M hw/pci-bridge/xio3130_upstream.c
    M hw/pci-host/xilinx-pcie.c
    M hw/pci/pci.c
    M hw/scsi/megasas.c
    M hw/usb/hcd-xhci.c
    M hw/vfio/pci.c
    M hw/xen/xen_pt.c
    M include/hw/pci/pci.h

  Log Message:
  -----------
  pci: removed the is_express field since a uniform interface was inserted

according to Eduardo Habkost's commit fd3b02c889 all PCIEs now implement
INTERFACE_PCIE_DEVICE so we don't need is_express field anymore.

Devices that implements only INTERFACE_PCIE_DEVICE (is_express == 1)
or
devices that implements only INTERFACE_CONVENTIONAL_PCI_DEVICE (is_express == 0)
where not affected by the change.

The only devices that were affected are those that are hybrid and also
had (is_express == 1) - therefor only:
  - hw/vfio/pci.c
  - hw/usb/hcd-xhci.c
  - hw/xen/xen_pt.c

For those 3 I made sure that QEMU_PCI_CAP_EXPRESS is on in instance_init()

Reviewed-by: Marcel Apfelbaum <mar...@redhat.com>
Reviewed-by: Eduardo Habkost <ehabk...@redhat.com>
Signed-off-by: Yoni Bettan <ybet...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: b86107ab43b804e899a226fe287e34ab8acef596
      
https://github.com/qemu/qemu/commit/b86107ab43b804e899a226fe287e34ab8acef596
  Author: Tiwei Bie <tiwei....@intel.com>
  Date:   2018-02-13 (Tue, 13 Feb 2018)

  Changed paths:
    M hw/virtio/virtio-balloon.c

  Log Message:
  -----------
  virtio-balloon: unref the memory region before continuing

Signed-off-by: Tiwei Bie <tiwei....@intel.com>
Cc: qemu-sta...@nongnu.org
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: bb102d1da15a97c6750a4f96810cf15713be2bd6
      
https://github.com/qemu/qemu/commit/bb102d1da15a97c6750a4f96810cf15713be2bd6
  Author: Yongji Xie <elohi...@gmail.com>
  Date:   2018-02-13 (Tue, 13 Feb 2018)

  Changed paths:
    M contrib/libvhost-user/libvhost-user.c

  Log Message:
  -----------
  libvhost-user: Fix resource leak

Free the mmaped memory when we need to mmap new memory
space on vu_set_mem_table_exec() and vu_set_log_base_exec() to
avoid memory leak.

Also close the corresponding fd after mmap() on
vu_set_log_base_exec() to avoid fd leak.

Signed-off-by: Yongji Xie <xieyon...@baidu.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lur...@redhat.com>


  Commit: 293084a7196b1d7781b6fe19b24e85eb8b7f4de0
      
https://github.com/qemu/qemu/commit/293084a7196b1d7781b6fe19b24e85eb8b7f4de0
  Author: Yongji Xie <elohi...@gmail.com>
  Date:   2018-02-13 (Tue, 13 Feb 2018)

  Changed paths:
    M contrib/libvhost-user/libvhost-user.c
    M contrib/libvhost-user/libvhost-user.h

  Log Message:
  -----------
  libvhost-user: Support across-memory-boundary access

The sg list/indirect descriptor table may be contigious
in GPA but not in HVA address space. But libvhost-user
wasn't aware of that. This would cause out-of-bounds
access. Even a malicious guest could use it to get
information from the vhost-user backend.

Introduce a plen parameter in vu_gpa_to_va() so we can
handle this case, returning the actual mapped length.

Signed-off-by: Yongji Xie <xieyon...@baidu.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>
Reviewed-by: Maxime Coquelin <maxime.coque...@redhat.com>


  Commit: fc67208f228af8e444f74362db1bced56a3daa71
      
https://github.com/qemu/qemu/commit/fc67208f228af8e444f74362db1bced56a3daa71
  Author: Marcel Apfelbaum <mar...@redhat.com>
  Date:   2018-02-13 (Tue, 13 Feb 2018)

  Changed paths:
    M hw/pci/pci_bridge.c
    M include/hw/pci/pci_bridge.h

  Log Message:
  -----------
  hw/pci-bridge: fix pcie root port's IO hints capability

The gen_pcie_root_port mem-reserve and pref32-reserve properties are
defined as size (so uint64_t), but passed as uint32_t when building
the 'IO hints' vendor specific capability.
Passing 4G (or more) gets truncated and passed as a zero reservation.
Is not a huge issue since the guest firmware will always compare the
hints with the default value and take the maximum.

Fix it by passing the values as uint64_t and failing to init the
gen_pcie_root_port id invalid values are used.

Signed-off-by: Marcel Apfelbaum <mar...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: 92146b7a0fe6d6f9df34eeb22dc8e33785a49a42
      
https://github.com/qemu/qemu/commit/92146b7a0fe6d6f9df34eeb22dc8e33785a49a42
  Author: Igor Mammedov <imamm...@redhat.com>
  Date:   2018-02-13 (Tue, 13 Feb 2018)

  Changed paths:
    M tests/bios-tables-test.c

  Log Message:
  -----------
  tests: acpi: fix FADT not being compared to reference table

It turns out that FADT isn't actually tested for changes
against reference table, since it happens to be the 1st
table in RSDT which is currently ignored.
Fix it by making sure that all tables from RSDT are added
to test list.

NOTE: FADT contains guest allocated pointers to FACS/DSDT,
zero them out so that possible FACS/DSDT address change
won't affect test results.

Signed-off-by: Igor Mammedov <imamm...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: 562a140765e56b898601fbd84046fc4d9b9a3bed
      
https://github.com/qemu/qemu/commit/562a140765e56b898601fbd84046fc4d9b9a3bed
  Author: Michael S. Tsirkin <m...@redhat.com>
  Date:   2018-02-13 (Tue, 13 Feb 2018)

  Changed paths:
    M hw/isa/lpc_ich9.c

  Log Message:
  -----------
  lpc: drop pcie host dependency

Doesn't look like that header is used.

Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: e89e7ea620f866ab42cbaa2de964552a3d2f7494
      
https://github.com/qemu/qemu/commit/e89e7ea620f866ab42cbaa2de964552a3d2f7494
  Author: Michael S. Tsirkin <m...@redhat.com>
  Date:   2018-02-13 (Tue, 13 Feb 2018)

  Changed paths:
    M tests/acpi-test-data/pc/FACP
    M tests/acpi-test-data/q35/FACP

  Log Message:
  -----------
  acpi-test: update FADT

Previous commit ("tests: acpi: fix FADT not being compared to reference table")
started tracking changes to the FADT. Generate the expected FACP files -
apparently these weren't updated since 2013.

Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: bf1e7140ef0b3a149860ab9f05b36665133238f6
      
https://github.com/qemu/qemu/commit/bf1e7140ef0b3a149860ab9f05b36665133238f6
  Author: Tomáš Golembiovský <tgole...@redhat.com>
  Date:   2018-02-13 (Tue, 13 Feb 2018)

  Changed paths:
    M hw/virtio/virtio-balloon.c
    M include/standard-headers/linux/virtio_balloon.h

  Log Message:
  -----------
  virtio-balloon: include statistics of disk/file caches

Signed-off-by: Tomáš Golembiovský <tgole...@redhat.com>
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Signed-off-by: Michael S. Tsirkin <m...@redhat.com>


  Commit: b734ed9de10dbf10a873ae4b44cb1c13f59213d0
      
https://github.com/qemu/qemu/commit/b734ed9de10dbf10a873ae4b44cb1c13f59213d0
  Author: Peter Maydell <peter.mayd...@linaro.org>
  Date:   2018-02-13 (Tue, 13 Feb 2018)

  Changed paths:
    M contrib/libvhost-user/libvhost-user.c
    M contrib/libvhost-user/libvhost-user.h
    M docs/pcie_pci_bridge.txt
    M hw/block/dataplane/virtio-blk.c
    M hw/block/nvme.c
    M hw/isa/lpc_ich9.c
    M hw/net/e1000e.c
    M hw/pci-bridge/gen_pcie_root_port.c
    M hw/pci-bridge/i82801b11.c
    M hw/pci-bridge/ioh3420.c
    M hw/pci-bridge/pci_bridge_dev.c
    M hw/pci-bridge/pcie_pci_bridge.c
    M hw/pci-bridge/pcie_root_port.c
    M hw/pci-bridge/xio3130_downstream.c
    M hw/pci-bridge/xio3130_upstream.c
    M hw/pci-host/xilinx-pcie.c
    M hw/pci/pci.c
    M hw/pci/pci_bridge.c
    M hw/scsi/megasas.c
    M hw/scsi/virtio-scsi-dataplane.c
    M hw/usb/hcd-xhci.c
    M hw/vfio/pci.c
    M hw/virtio/trace-events
    M hw/virtio/vhost.c
    M hw/virtio/virtio-balloon.c
    M hw/virtio/virtio-bus.c
    M hw/virtio/virtio-pci.c
    M hw/virtio/virtio.c
    M hw/xen/xen_pt.c
    M include/hw/compat.h
    M include/hw/pci/pci.h
    M include/hw/pci/pci_bridge.h
    M include/hw/virtio/vhost.h
    M include/hw/virtio/virtio-bus.h
    M include/migration/vmstate.h
    M include/standard-headers/linux/virtio_balloon.h
    M tests/acpi-test-data/pc/FACP
    M tests/acpi-test-data/q35/FACP
    M tests/bios-tables-test.c

  Log Message:
  -----------
  Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging

virtio,vhost,pci,pc: features, fixes and cleanups

- new stats in virtio balloon
- virtio eventfd rework for boot speedup
- vhost memory rework for boot speedup
- fixes and cleanups all over the place

Signed-off-by: Michael S. Tsirkin <m...@redhat.com>

# gpg: Signature made Tue 13 Feb 2018 16:29:55 GMT
# gpg:                using RSA key 281F0DB8D28D5469
# gpg: Good signature from "Michael S. Tsirkin <m...@kernel.org>"
# gpg:                 aka "Michael S. Tsirkin <m...@redhat.com>"
# Primary key fingerprint: 0270 606B 6F3C DF3D 0B17  0970 C350 3912 AFBE 8E67
#      Subkey fingerprint: 5D09 FD08 71C8 F85B 94CA  8A0D 281F 0DB8 D28D 5469

* remotes/mst/tags/for_upstream: (22 commits)
  virtio-balloon: include statistics of disk/file caches
  acpi-test: update FADT
  lpc: drop pcie host dependency
  tests: acpi: fix FADT not being compared to reference table
  hw/pci-bridge: fix pcie root port's IO hints capability
  libvhost-user: Support across-memory-boundary access
  libvhost-user: Fix resource leak
  virtio-balloon: unref the memory region before continuing
  pci: removed the is_express field since a uniform interface was inserted
  virtio-blk: enable multiple vectors when using multiple I/O queues
  pci/bus: let it has higher migration priority
  pci-bridge/i82801b11: clear bridge registers on platform reset
  vhost: Move log_dirty check
  vhost: Merge and delete unused callbacks
  vhost: Clean out old vhost_set_memory and friends
  vhost: Regenerate region list from changed sections list
  vhost: Merge sections added to temporary list
  vhost: Simplify ring verification checks
  vhost: Build temporary section list and deref after commit
  virtio: improve virtio devices initialization time
  ...

Signed-off-by: Peter Maydell <peter.mayd...@linaro.org>


Compare: https://github.com/qemu/qemu/compare/fb68096da3d3...b734ed9de10d

Reply via email to