public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: nitin.a.kamble-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Question about EMULATE_DO_MMIO
Date: Wed, 17 Oct 2007 12:50:14 +0200	[thread overview]
Message-ID: <4715E8E6.2030708@qumranet.com> (raw)
In-Reply-To: <1192566489.2488.10.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>

Nitin A Kamble wrote:
> 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.
>
>   

That means there's a bug somewhere.  We need to fix it.


>> 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.
>   

It will fail, and we'll see it and go back to emulation.

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


-------------------------------------------------------------------------
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/

      parent reply	other threads:[~2007-10-17 10:50 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
     [not found]         ` <1192566489.2488.10.camel-mpPvwfgnXtFHIUuj5cj4Omt3HXsI98Cx0E9HWUfgJXw@public.gmane.org>
2007-10-17 10:50           ` Avi Kivity [this message]

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=4715E8E6.2030708@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=nitin.a.kamble-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