From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH 0/4] More emulator correctness fixes
Date: Thu, 18 Feb 2010 12:38:23 +0200 [thread overview]
Message-ID: <4B7D189F.4070305@redhat.com> (raw)
In-Reply-To: <1266488102-18839-1-git-send-email-gleb@redhat.com>
On 02/18/2010 12:14 PM, Gleb Natapov wrote:
> This patch series adds proper permission checking during segment
> selector loading. Some missing fault injections are added.
>
Thanks, applied.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-02-18 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 10:14 [PATCH 0/4] More emulator correctness fixes Gleb Natapov
2010-02-18 10:14 ` [PATCH 1/4] KVM: Forbid modifying CS segment register by mov instruction Gleb Natapov
2010-02-18 10:15 ` [PATCH 2/4] KVM: Fix load_guest_segment_descriptor() to inject page fault Gleb Natapov
2010-02-18 10:15 ` [PATCH 3/4] KVM: Fix segment descriptor loading Gleb Natapov
2010-02-18 10:15 ` [PATCH 4/4] KVM: Fix emulate_sys[call, enter, exit]()'s fault handling Gleb Natapov
2010-02-18 10:38 ` Avi Kivity [this message]
2010-02-18 10:55 ` [PATCH 0/4] More emulator correctness fixes Takuya Yoshikawa
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=4B7D189F.4070305@redhat.com \
--to=avi@redhat.com \
--cc=gleb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.