qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] [PULL] kvm updates
Date: Thu, 01 Mar 2012 14:47:43 +0200	[thread overview]
Message-ID: <4F4F6FEF.6050708@redhat.com> (raw)

This batch of updates is mostly Jan's rework of qemu-kvm's TPR
optimization for 32-bit Windows, making Windows XP much faster with kvm
enabled on older Intel and any AMD hardware.  Any similarities to the
original hack are purely coincidental.

Please pull from:

  git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master

----------------------------------------------------------------
Avi Kivity (1):
      pc-bios: update kvmvapic.bin

Gleb Natapov (1):
      kvm: Synchronize cpu state in kvm_arch_stop_on_emulation_error()

Jan Kiszka (10):
      kvm: Set cpu_single_env only once
      Remove useless casts from cpu iterators
      Process pending work while waiting for initial kick-off in TCG mode
      Allow to use pause_all_vcpus from VCPU context
      target-i386: Add infrastructure for reporting TPR MMIO accesses
      kvmvapic: Add option ROM
      kvmvapic: Introduce TPR access optimization for Windows guests
      kvmvapic: Simplify mp/up_set_tpr
      optionsrom: Reserve space for checksum
      kvmvapic: Use optionrom helpers

 .gitignore                    |    1 +
 Makefile                      |    2 +-
 Makefile.target               |    3 +-
 cpu-all.h                     |    3 +-
 cpus.c                        |   26 ++-
 hw/apic.c                     |  126 ++++++-
 hw/apic.h                     |    2 +
 hw/apic_common.c              |   69 ++++-
 hw/apic_internal.h            |   27 ++
 hw/kvm/apic.c                 |   32 ++
 hw/kvmvapic.c                 |  805
+++++++++++++++++++++++++++++++++++++++++
 hw/mc146818rtc.c              |    5 +-
 kvm-all.c                     |    5 -
 pc-bios/kvmvapic.bin          |  Bin 0 -> 9216 bytes
 pc-bios/optionrom/Makefile    |    2 +-
 pc-bios/optionrom/kvmvapic.S  |  335 +++++++++++++++++
 pc-bios/optionrom/optionrom.h |    3 +-
 target-i386/cpu.h             |   10 +
 target-i386/helper.c          |   16 +
 target-i386/kvm.c             |   26 ++-
 20 files changed, 1468 insertions(+), 30 deletions(-)
 create mode 100644 hw/kvmvapic.c
 create mode 100755 pc-bios/kvmvapic.bin
 create mode 100644 pc-bios/optionrom/kvmvapic.S

-- 
error compiling committee.c: too many arguments to function

             reply	other threads:[~2012-03-01 12:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 12:47 Avi Kivity [this message]
2012-03-01 23:45 ` [Qemu-devel] [PULL] kvm updates Andreas Färber
2012-03-04 10:08   ` Avi Kivity
2012-03-02 13:22 ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2012-06-11 13:38 Avi Kivity
2012-06-11 18:28 ` Anthony Liguori
2012-08-12 12:58 Avi Kivity
2012-08-13 21:13 ` Anthony Liguori
2012-09-10 15:25 [Qemu-devel] [PULL] KVM updates Avi Kivity
2012-09-10 15:32 ` Jan Kiszka
2012-09-10 15:49   ` Marcelo Tosatti
2012-09-10 15:54     ` Avi Kivity
2012-09-10 23:03 ` Anthony Liguori
2012-09-11  8:50   ` Avi Kivity
2012-09-11  9:30     ` Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F4F6FEF.6050708@redhat.com \
    --to=avi@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).