All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: 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 19:14:12 +0300	[thread overview]
Message-ID: <49E4B654.6060101@redhat.com> (raw)
In-Reply-To: <49E4B4D4.1020903@zytor.com>

H. Peter Anvin wrote:
> Avi Kivity wrote:
>   
>> The comment about repeating 'mov ss' in the manual has that wonderful
>> word in it, May.  That means we're perfectly allowed to ignore it and
>> just set the flag unconditionally.
>>
>>     
>
> Realistically, though, this should only be done for a limited number of
> sequential instructions.
>
>   

Why?  Do you see a guest filling all of memory with 'mov ss' and 
expecting to break out of it via an interrupt?

>> I doubt we'll ever see a repeated 'mov ss', once is more than enough.
>>     
>
> True enough, except maliciously.
>   

Why do we care?  The guest can only harm itself, and if it wants to 
disable interrupts, it would be a lot easier for it to run a plain 'cli'.

I guess it would be a problem if we emulated 'mov ss' for ordinary 
userspace or vm86 mode, but we don't.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2009-04-14 16:13 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 [this message]
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
  -- 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=49E4B654.6060101@redhat.com \
    --to=avi@redhat.com \
    --cc=glommer@redhat.com \
    --cc=hpa@zytor.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 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.