From: Andi Kleen <ak@suse.de>
To: Jamie Lokier <jamie@shareable.org>
Cc: Andi Kleen <ak@suse.de>, Linus Torvalds <torvalds@osdl.org>,
Nick Piggin <piggin@cyberone.com.au>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, richard.brunner@amd.com
Subject: Re: [PATCH] Athlon/Opteron Prefetch Fix for 2.6.0test5 + numbers
Date: Thu, 18 Sep 2003 19:06:29 +0200 [thread overview]
Message-ID: <20030918170629.GC7917@wotan.suse.de> (raw)
In-Reply-To: <20030918160456.GC7548@mail.jlokier.co.uk>
On Thu, Sep 18, 2003 at 05:04:56PM +0100, Jamie Lokier wrote:
> Jamie Lokier wrote:
> > > + /* Don't check for LDT code segments because they could have
> > > + non zero bases. Better would be to add in the base in this case. */
> > > + if (regs->xcs & (1<<2))
> > > + return 0;
> >
> > It is possible to have a non-standard code segment in the GDT, too.
> > Thus a better to check is "unlikely((regs->xcs & 0xffff) != __USER_CS)".
>
> Ignore me here, I'm being dense - forgetting about __KERNEL_CS :)
>
> My point is simply that non-zero base GDT segments are possible in
> userspace, and whatever code you add later to add the base should
> be aware of that.
I don't see how a non standard GDT is possible in user space. The GDT
is only managed by the kernel. 2.6 offers to change it for NPTL, but
that only applies to data segments.
In vm86 mode the user can load a different base without LDT, but that
should not matter here (although it may be better to check for VM86 mode
too)
-Andi
next prev parent reply other threads:[~2003-09-18 17:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 2:22 [PATCH] Athlon/Opteron Prefetch Fix for 2.6.0test5 + numbers Andi Kleen
2003-09-17 2:44 ` Andrew Morton
2003-09-17 3:25 ` Andi Kleen
2003-09-17 4:53 ` Nick Piggin
2003-09-17 5:08 ` Andrew Morton
2003-09-17 5:19 ` Nick Piggin
2003-09-17 7:15 ` Dave Hansen
2003-09-17 5:26 ` Andi Kleen
2003-09-17 5:44 ` Nick Piggin
2003-09-17 19:53 ` Linus Torvalds
2003-09-17 20:21 ` Andi Kleen
2003-09-17 20:50 ` Linus Torvalds
2003-09-17 21:12 ` Andi Kleen
2003-09-18 15:38 ` Jamie Lokier
2003-09-18 16:04 ` Jamie Lokier
2003-09-18 17:06 ` Andi Kleen [this message]
2003-09-18 19:48 ` Jamie Lokier
2003-09-19 6:55 ` Kai Henningsen
2003-09-19 10:02 ` Andreas Schwab
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=20030918170629.GC7917@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=richard.brunner@amd.com \
--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 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.