public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Sheng Yang <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] KVM: x86 emulator: Discard CR2 in x86 emulator
Date: Sun, 18 Nov 2007 12:35:22 +0200	[thread overview]
Message-ID: <4740156A.2090205@qumranet.com> (raw)
In-Reply-To: <200711161630.34137.sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

Sheng Yang wrote:
> From f8aca5afbc018e71dc37d2e6001bcec376499939 Mon Sep 17 00:00:00 2001
> From: Sheng Yang <sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Date: Fri, 16 Nov 2007 16:29:15 +0800
> Subject: [PATCH] KVM: x86 emulator: Discard CR2 in x86 emulator
>
> For CR2 is unreliable and unavailable in many condition, this patch
> completely decode memory operand instead of using CR2 in x86 emulator.
>   

Applied, thanks.

This is just a rename, right?  That means lods/stos was the last 
instance of using cr2.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2007-11-18 10:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16  8:30 [PATCH] KVM: x86 emulator: Discard CR2 in x86 emulator Sheng Yang
     [not found] ` <200711161630.34137.sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2007-11-18 10:35   ` Avi Kivity [this message]
     [not found]     ` <4740156A.2090205-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-18 15:28       ` Sheng Yang

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=4740156A.2090205@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=sheng.yang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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