From: Zachary Amsden <zach@vmware.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@suse.de>
Subject: Re: [patch] i386: remove IOPL check on task switch
Date: Fri, 03 Nov 2006 10:06:04 -0800 [thread overview]
Message-ID: <454B850C.3050402@vmware.com> (raw)
In-Reply-To: <200611030130_MC3-1-D02A-DEB@compuserve.com>
Chuck Ebbert wrote:
> IOPL is implicitly saved and restored on task switch,
> so explicit check is no longer needed.
>
> Signed-off-by: Chuck Ebbert <76306.1226@compuserve.com>
>
> --- 2.6.19-rc4-32smp.orig/arch/i386/kernel/process.c
> +++ 2.6.19-rc4-32smp/arch/i386/kernel/process.c
> @@ -681,12 +681,6 @@ struct task_struct fastcall * __switch_t
> loadsegment(gs, next->gs);
>
> /*
> - * Restore IOPL if needed.
> - */
> - if (unlikely(prev->iopl != next->iopl))
> - set_iopl_mask(next->iopl);
> -
> - /*
> * Now maybe handle debug registers and/or IO bitmaps
> */
> if (unlikely((task_thread_info(next_p)->flags & _TIF_WORK_CTXSW)
>
Nack. This is used for paravirt-ops kernels that use IOPL'd userspace.
Fixing it would require a fairly heavy penalty on the iret path, since
every single instruction there contributes to a critical region which
must have custom fixup code, or some other technique to provide
protection against interrupt re-entrancy.
At least, let's discuss other potential solutions first - for now it is
harmless.
Zach
next prev parent reply other threads:[~2006-11-03 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-03 6:27 [patch] i386: remove IOPL check on task switch Chuck Ebbert
2006-11-03 18:06 ` Zachary Amsden [this message]
2006-11-03 18:41 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-11-03 23:57 Chuck Ebbert
2006-11-04 19:19 ` Zachary Amsden
2006-11-04 19:39 ` Zachary Amsden
2006-11-04 19:52 ` Linus Torvalds
2006-11-04 20:09 ` Zachary Amsden
2006-11-04 20:02 ` Andi Kleen
2006-11-04 0:00 Chuck Ebbert
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=454B850C.3050402@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