public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Zachary Amsden <zach@vmware.com>
Cc: Chuck Ebbert <76306.1226@compuserve.com>, Andi Kleen <ak@suse.de>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] i386: remove IOPL check on task switch
Date: Sat, 04 Nov 2006 11:39:08 -0800	[thread overview]
Message-ID: <454CEC5C.2050507@vmware.com> (raw)
In-Reply-To: <454CE7D9.3070308@vmware.com>

Zachary Amsden wrote:
> Chuck Ebbert wrote:
>> In-Reply-To: <454B850C.3050402@vmware.com>
>>
>> On Fri, 03 Nov 2006 10:06:04 -0800, Zachary Amsden wrote:
>>
>>  
>>> Chuck Ebbert wrote:
>>>    
>>>> IOPL is implicitly saved and restored on task switch,
>>>> so explicit check is no longer needed.
>>>>       
>>> Nack.  This is used for paravirt-ops kernels that use IOPL'd 
>>> userspace.      
>>
>> How does that work?  In the stock kernel, anything done by
>> the call to set_iopl_mask() (that was removed by the patch)
>> will be nullified by the 'popfl' at the end of the switch_to()
>> macro.
>>   
>
> Who put a popfl back in switch_to?  I took it out some time ago.  It 
> should not be there.  The only reason for it was to stop IOPL leaking 
> from one process to another from a sleep during a sysenter based 
> system call.

Ok, checking shows Linus put it back to stop NT leakage.  This is 
correct, but unlikely.  Would be nice to avoid it unless absolutely 
necessary.  Perhaps xor eflags old and new and only set_system_eflags() 
if non-ALU bits have changed.

Zach

  reply	other threads:[~2006-11-04 19:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03 23:57 [patch] i386: remove IOPL check on task switch Chuck Ebbert
2006-11-04 19:19 ` Zachary Amsden
2006-11-04 19:39   ` Zachary Amsden [this message]
2006-11-04 19:52     ` Linus Torvalds
2006-11-04 20:09       ` Zachary Amsden
2006-11-04 20:02     ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2006-11-04  0:00 Chuck Ebbert
2006-11-03  6:27 Chuck Ebbert
2006-11-03 18:06 ` Zachary Amsden
2006-11-03 18:41   ` Andi Kleen

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=454CEC5C.2050507@vmware.com \
    --to=zach@vmware.com \
    --cc=76306.1226@compuserve.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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