All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] Kill decode_cache
Date: Wed, 1 Jun 2011 15:47:18 +0300	[thread overview]
Message-ID: <20110601124718.GF491@redhat.com> (raw)
In-Reply-To: <1306931665-26507-1-git-send-email-avi@redhat.com>

On Wed, Jun 01, 2011 at 03:34:23PM +0300, Avi Kivity wrote:
> This mostly mindless patchset folds decode_cache into its enclosing struct,
> x86_emulate_context.  The point is to remove tons of pointless
> 
>        struct decode_cache *c = &ctxt->decode;
> 
> lines from the code, which contribute absolutely nothing.
> 
Didn't we plan some day to have a cache of decoded instructions to skip
decoding stage? Not all the fields currently in decode_cache belong
there of course (regs, io_read, mem_read).

> Avi Kivity (2):
>   KVM: x86 emulator: rename decode_cache::eip to _eip
>   KVM: x86 emulator: fold decode_cache into x86_emulate_ctxt
> 
>  arch/x86/include/asm/kvm_emulate.h |   46 +-
>  arch/x86/kvm/emulate.c             | 1275 +++++++++++++++++-------------------
>  arch/x86/kvm/trace.h               |    8 +-
>  arch/x86/kvm/x86.c                 |   47 +-
>  4 files changed, 631 insertions(+), 745 deletions(-)
> 
> -- 
> 1.7.5.3
> 
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
			Gleb.

  parent reply	other threads:[~2011-06-01 12:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-01 12:34 [PATCH 0/2] Kill decode_cache Avi Kivity
2011-06-01 12:34 ` [PATCH 1/2] KVM: x86 emulator: rename decode_cache::eip to _eip Avi Kivity
2011-06-01 12:34 ` [PATCH 2/2] KVM: x86 emulator: fold decode_cache into x86_emulate_ctxt Avi Kivity
2011-06-01 12:47 ` Gleb Natapov [this message]
2011-06-01 12:56   ` [PATCH 0/2] Kill decode_cache Avi Kivity

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=20110601124718.GF491@redhat.com \
    --to=gleb@redhat.com \
    --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 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.