public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Nitin A Kamble <nitin.a.kamble-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Question about EMULATE_DO_MMIO
Date: Tue, 16 Oct 2007 13:28:09 -0700	[thread overview]
Message-ID: <1192566489.2488.10.camel@lnitindesktop.sc.intel.com> (raw)
In-Reply-To: <47151B38.1070402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 1200 bytes --]

On Tue, 2007-10-16 at 13:12 -0700, Avi Kivity wrote:

> Why do you think it is better?  I would have thought that vm86 is much
> faster.
> 
I am seeing execution going to strange places in vm86 mode. That issue
is not coming in the emulation.

> I thought of doing it this way:
> 
> - try to run normally
> - if vm entry failed due to invalid guest state (the famous
> 0x80000021),
> then emulate 50 instructions
> - repeat
This may be better, I will give it a try.

> That will also handle the few cases where VT can't handle protected
> mode.
> 
> It should exit to userspace, same as the non-emulating case.  However
> it
> shouldn't happen for normal writes.
> 
Only thing is if it in the real mode, then returning back to user mode
will setup the cpu state as real mode, and because of that vmenter will
fail.

> 
> --
> Do not meddle in the internals of kernels, for they are subtle and
> quick to panic.
> 
> 

Thanks a lot for your input.

-- 
Thanks & Regards,
Nitin
Open Source Technology Center, Intel Corporation
-----------------------------------------------------------------
The mind is like a parachute; it works much better when it's open

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

  parent reply	other threads:[~2007-10-16 20:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 18:24 Question about EMULATE_DO_MMIO Nitin A Kamble
     [not found] ` <1192559057.2488.5.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2007-10-16 20:12   ` Avi Kivity
     [not found]     ` <47151B38.1070402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-16 20:28       ` Nitin A Kamble [this message]
     [not found]         ` <1192566489.2488.10.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2007-10-17 10:50           ` 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=1192566489.2488.10.camel@lnitindesktop.sc.intel.com \
    --to=nitin.a.kamble-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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