kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Avi Kivity <avi@redhat.com>, Glauber Costa <glommer@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] deal with interrupt shadow state for emulated instruction
Date: Tue, 14 Apr 2009 10:32:56 -0700	[thread overview]
Message-ID: <49E4C8C8.9060109@zytor.com> (raw)
In-Reply-To: <20090414183111.0243408e@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>> Why?  Do you see a guest filling all of memory with 'mov ss' and 
>> expecting to break out of it via an interrupt?
> 
> Well I did try mapping a page of move ss all through memory on real
> hardware long ago and seeing what happened on a 386 in real mode with
> DOSEMU. I was disappointed ;)
> 

Heheheheh....

	-hpa

  reply	other threads:[~2009-04-14 17:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 20:06 [PATCH] deal with interrupt shadow state for emulated instruction Glauber Costa
2009-04-14  9:07 ` Gleb Natapov
2009-04-14  9:34 ` Avi Kivity
2009-04-14 16:07   ` H. Peter Anvin
2009-04-14 16:14     ` Avi Kivity
2009-04-14 16:25       ` H. Peter Anvin
2009-04-16  9:18         ` Avi Kivity
2009-04-16 22:40           ` H. Peter Anvin
2009-04-19  8:26             ` Avi Kivity
2009-04-14 17:31       ` Alan Cox
2009-04-14 17:32         ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-05 18:40 Glauber Costa
2009-05-06  8:03 ` Gleb Natapov
2009-05-06 10:51   ` Avi Kivity
2009-05-08  5:25     ` Glauber Costa
2009-05-08  7:18       ` Gleb Natapov
2009-05-08 13:02         ` Glauber Costa
2009-04-28 14:30 Glauber Costa
2009-04-30 11:50 ` Avi Kivity
2009-05-05 13:57   ` Glauber Costa
2009-04-08 21:42 Glauber Costa
2009-04-11 16:37 ` Avi Kivity
2009-04-11 21:15   ` H. Peter Anvin

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=49E4C8C8.9060109@zytor.com \
    --to=hpa@zytor.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=avi@redhat.com \
    --cc=glommer@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).