All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org, mtosatti@redhat.com
Subject: Re: [PATCHv4 4/5] KVM: emulator: make linearize() callable from outside of emulator
Date: Thu, 19 Jul 2012 13:32:59 +0300	[thread overview]
Message-ID: <5007E25B.3060207@redhat.com> (raw)
In-Reply-To: <1342683653-32114-5-git-send-email-gleb@redhat.com>

On 07/19/2012 10:40 AM, Gleb Natapov wrote:
> The function will be used outside of the emulator.
> 
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
> ---
>  arch/x86/include/asm/kvm_emulate.h |   16 +++++
>  arch/x86/kvm/emulate.c             |  114 ++++++++++++++++++++----------------
>  2 files changed, 79 insertions(+), 51 deletions(-)
> 
> diff --git a/arch/x86/include/asm/kvm_emulate.h b/arch/x86/include/asm/kvm_emulate.h
> index 7c276ca..9ce651b 100644
> --- a/arch/x86/include/asm/kvm_emulate.h
> +++ b/arch/x86/include/asm/kvm_emulate.h
> @@ -374,6 +374,21 @@ enum x86_intercept {
>  	nr_x86_intercepts
>  };
>  
> +struct x86_linearize_params
> +{
> +	enum x86emul_mode mode;
> +	ulong ea;
> +	unsigned size;
> +	unsigned seg;
> +	struct desc_struct desc;
> +	u16 sel;
> +	bool usable;
> +	bool write;
> +	bool fetch;
> +	u8 ad_bytes;
> +	unsigned cpl;
> +};
> +
> @@ -470,14 +470,6 @@ static void set_seg_override(struct x86_emulate_ctxt *ctxt, int seg)
>  	ctxt->seg_override = seg;
>  }
>  
> -static unsigned long seg_base(struct x86_emulate_ctxt *ctxt, int seg)
> -{
> -	if (ctxt->mode == X86EMUL_MODE_PROT64 && seg < VCPU_SREG_FS)
> -		return 0;
> -
> -	return ctxt->ops->get_cached_segment_base(ctxt, seg);
> -}
> -

> +int x86_linearize(struct x86_linearize_params *p, ulong *linear)
>  {
> -	struct desc_struct desc;
> -	bool usable;
>  	ulong la;
>  	u32 lim;
> -	u16 sel;
>  	unsigned cpl, rpl;
>  
> -	la = seg_base(ctxt, addr.seg) + addr.ea;
> -	switch (ctxt->mode) {
> +	la = get_desc_base(&p->desc) + p->ea;

This makes 64-bit mode slower, since before the patch it avoided reading
the segment base for non-fs/gs segments, and only read the segment base
for fs/gs.  After the patch we always execute 4 VMREADs (and decode the
results).


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



  reply	other threads:[~2012-07-19 10:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19  7:40 [PATCHv4 0/5] improve speed of "rep ins" emulation Gleb Natapov
2012-07-19  7:40 ` [PATCHv4 1/5] Provide userspace IO exit completion callback Gleb Natapov
2012-07-19  7:40 ` [PATCHv4 2/5] KVM: emulator: make x86 emulation modes enum instead of defines Gleb Natapov
2012-07-19  7:40 ` [PATCHv4 3/5] KVM: emulator: move some address manipulation function out of emulator code Gleb Natapov
2012-07-19 10:42   ` Avi Kivity
2012-07-19 10:49     ` Gleb Natapov
2012-07-19 13:34       ` Avi Kivity
2012-07-19 13:43         ` Gleb Natapov
2012-07-19  7:40 ` [PATCHv4 4/5] KVM: emulator: make linearize() callable from outside of emulator Gleb Natapov
2012-07-19 10:32   ` Avi Kivity [this message]
2012-07-19 10:51     ` Gleb Natapov
2012-07-19 12:52       ` Avi Kivity
2012-07-19 12:54         ` Gleb Natapov
2012-07-19  7:40 ` [PATCHv4 5/5] KVM: Provide fast path for "rep ins" emulation if possible Gleb Natapov
2012-07-19 10:37   ` Avi Kivity
2012-07-19 11:09     ` 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=5007E25B.3060207@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.