From: "Andreas Färber" <afaerber@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>,
KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PULL] kvm updates
Date: Fri, 02 Mar 2012 00:45:31 +0100 [thread overview]
Message-ID: <4F500A1B.7010905@suse.de> (raw)
In-Reply-To: <4F4F6FEF.6050708@redhat.com>
Am 01.03.2012 13:47, schrieb Avi Kivity:
> 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
What about my kvmclock kvm_enabled() fix? Should I rather submit that as
part of my qom-cpu queue? It depends on it.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-03-01 23:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 12:47 [Qemu-devel] [PULL] kvm updates Avi Kivity
2012-03-01 23:45 ` Andreas Färber [this message]
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=4F500A1B.7010905@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--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).