From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: x86: Add KVM_GET/SET_VCPU_EVENTS
Date: Sun, 15 Nov 2009 15:33:09 +0100 [thread overview]
Message-ID: <4B001125.7080301@web.de> (raw)
In-Reply-To: <4AFFFDBA.8010102@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
Avi Kivity wrote:
> On 11/12/2009 02:04 AM, Jan Kiszka wrote:
>> This new IOCTL exports all yet user-invisible states related to
>> exceptions, interrupts, and NMIs. Together with appropriate user space
>> changes, this fixes sporadic problems of vmsave/restore, live migration
>> and system reset.
>>
>>
>
> Applied, thanks. I added a flags field to the structure in case we
> discover a new bit that needs to fit in there. Please take a look
> (separate commit in kvm-next).
>
Looks ok.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-11-15 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 0:04 [PATCH] KVM: x86: Add KVM_GET/SET_VCPU_EVENTS Jan Kiszka
2009-11-15 13:10 ` Avi Kivity
2009-11-15 14:33 ` Jan Kiszka [this message]
2010-03-17 13:36 ` Alexander Graf
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=4B001125.7080301@web.de \
--to=jan.kiszka@web.de \
--cc=avi@redhat.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