From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH v2 0/7] KVM: Enhancements and fixes around guest debugging
Date: Wed, 24 Feb 2010 12:52:44 +0200 [thread overview]
Message-ID: <4B8504FC.6020400@redhat.com> (raw)
In-Reply-To: <cover.1266943665.git.jan.kiszka@siemens.com>
On 02/23/2010 06:47 PM, Jan Kiszka wrote:
> Changes in v2:
> - Retreat TF emulation patch, waiting for emulator rework
> - Spilt out svm_queue_exception moving
> - Factor out kvm_is_linear_rip ("Saved linear RIP == current RIP?")
> - Fixed breakage in INT3 emulation code and addressed review comments
>
> Patch 5 targets also 2.6.33., patch 1 should additionally be considered
> for stable 2.6.32.
>
All applied, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-02-24 10:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 16:47 [PATCH v2 0/7] KVM: Enhancements and fixes around guest debugging Jan Kiszka
2010-02-23 16:47 ` [PATCH v2 1/7] KVM: VMX: Update instruction length on intercepted BP Jan Kiszka
2010-02-23 16:47 ` [PATCH v2 2/7] KVM: SVM: Move svm_queue_exception Jan Kiszka
2010-02-23 16:47 ` [PATCH v2 3/7] KVM: x86: Add kvm_is_linear_rip Jan Kiszka
2010-02-23 16:47 ` [PATCH v2 4/7] KVM: SVM: Emulate nRIP feature when reinjecting INT3 Jan Kiszka
2010-02-23 16:47 ` [PATCH v2 5/7] KVM: x86: Add KVM_CAP_X86_ROBUST_SINGLESTEP Jan Kiszka
2010-02-23 16:47 ` [PATCH v2 6/7] KVM: x86: Drop RF manipulation for guest single-stepping Jan Kiszka
2010-02-23 16:47 ` [PATCH v2 7/7] KVM: x86: Preserve injected TF across emulation Jan Kiszka
2010-02-24 10:52 ` Avi Kivity [this message]
2010-02-24 10:58 ` [PATCH v2 0/7] KVM: Enhancements and fixes around guest debugging Avi Kivity
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=4B8504FC.6020400@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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