From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, jan.kiszka@siemens.com, mtosatti@redhat.com
Subject: Re: [PATCH] KVM: move DR register access handling into generic code.
Date: Mon, 12 Apr 2010 17:54:22 +0300 [thread overview]
Message-ID: <4BC3341E.2050108@redhat.com> (raw)
In-Reply-To: <20100412122712.GC23554@redhat.com>
On 04/12/2010 03:27 PM, Gleb Natapov wrote:
> Currently both SVM and VMX have their own DR handling code. Move it to
> x86.c.
>
>
The standard process is to make them identical first and finally merge
identical code, but I guess we can skip it in this case (Jan?)
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2010-04-12 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 12:27 [PATCH] KVM: move DR register access handling into generic code Gleb Natapov
2010-04-12 14:54 ` Avi Kivity [this message]
2010-04-12 16:09 ` Jan Kiszka
2010-04-12 16:52 ` Gleb Natapov
2010-04-12 16:54 ` Avi Kivity
2010-04-12 17:26 ` Gleb Natapov
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=4BC3341E.2050108@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