From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [PATCH] kvm: x86: Remove obsolet SS.RPL/DPL aligment
Date: Mon, 27 Dec 2010 17:37:45 +0200 [thread overview]
Message-ID: <4D18B2C9.4020505@redhat.com> (raw)
In-Reply-To: <4D18A95F.2010601@web.de>
On 12/27/2010 04:57 PM, Jan Kiszka wrote:
> From: Jan Kiszka<jan.kiszka@siemens.com>
>
> This seems to date back to the days KVM didn't support real mode. The
> check is no longer needed and, even worse, is corrupting the guest state
> in case SS.RPL != DPL.
Applied to uq/master (nice how obsolete code propagates itself); thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-12-27 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 14:57 [Qemu-devel] [PATCH] kvm: x86: Remove obsolet SS.RPL/DPL aligment Jan Kiszka
2010-12-27 15:37 ` Avi Kivity [this message]
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=4D18B2C9.4020505@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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).