[Top][All Lists]

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

[Qemu-devel] [PATCH v2 0/7] kvm: Get coalesced MMIO flushing out of the

From: Jan Kiszka
Subject: [Qemu-devel] [PATCH v2 0/7] kvm: Get coalesced MMIO flushing out of the hot-path
Date: Wed, 27 Jun 2012 18:27:22 +0200

Changes in v2:
 - added memory_region_clear_flush_coalesced
 - call memory_region_clear_flush_coalesced from
 - wrap all region manipulations via memory_region_transaction_begin/
   commit internally
 - flush coalesced MMIO only on memory_region_transaction_begin

Original description:

We currently flush the coalesced MMIO buffer on every vmexit to
userspace. KVM only provides a single buffer per VM, so a central lock
is required to read from it. This is a contention point given a large
enough VCPU set. Moreover, we need to hold the BQL while replaying the
queued requests, probably for a long time until there is more fine
grained locking available. Good reasons to overcome the unconditional

The series achieves this by flushing only on selected memory region
accesses, either generically via the memory access dispatcher or
directly on certain VGA PIO accesses that are not yet fully converted.
Another reason to flush are remappings or other relevant region state

Jan Kiszka (7):
  i82378: Remove bogus MMIO coalescing
  memory: Flush coalesced MMIO on selected region access
  memory: Use transaction_begin/commit also for single-step operations
  memory: Fold memory_region_update_topology into
  memory: Flush coalesced MMIO on mapping and state changes
  VGA: Flush coalesced MMIO on related MMIO/PIO accesses
  kvm: Stop flushing coalesced MMIO on vmexit

 hw/cirrus_vga.c |    7 ++++
 hw/i82378.c     |    1 -
 hw/qxl.c        |    1 +
 hw/vga-isa-mm.c |    1 +
 hw/vga.c        |    5 +++
 hw/vmware_vga.c |    1 +
 kvm-all.c       |    2 -
 memory.c        |  101 +++++++++++++++++++++++++++++++-----------------------
 memory.h        |   24 +++++++++++++
 9 files changed, 97 insertions(+), 46 deletions(-)


reply via email to

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