[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0610051014550.3952@g5.osdl.org>
Date: Thu, 5 Oct 2006 10:21:35 -0700 (PDT)
From: Linus Torvalds <torvalds@...l.org>
To: Andi Kleen <ak@...e.de>
cc: discuss@...-64.org, linux-kernel@...r.kernel.org
Subject: Re: Please pull x86-64 bug fixes
On Thu, 5 Oct 2006, Andi Kleen wrote:
>
> Please pull 'for-linus' from
>
> git://one.firstfloor.org/home/andi/git/linux-2.6
Please write that as
Please pull 'for-linus' from
git://one.firstfloor.org/home/andi/git/linux-2.6 for-linus
ie so that I can't miss the branch-name by mistake. I also cut-and-paste
the repo address (trying to re-type it would be just stupid), and to avoid
mistakes, it's _much_ easier if I can just triple-click and cut the whole
line, and then just do
"git pull <paste>"
without having to be careful about cutting at just the right character and
then having to write the branch-name separately.
Also, I think these two are totally bogus:
> Andi Kleen:
> x86-64: Ignore alignment checks in kernel
> i386: Ignore alignment checks in kernel
Have you actually ever seen an alignment check in the kernel? As far as I
know, the AC flag is only effective in user space, and anything else would
be in violation of the whole definition of the AC flag. The i486 manual
explicitly states that AC events are _only_ handled in ring3.
So I think these both are (a) misleading and (b) wrong.
Please don't do this.
The problem with the AC flag was that it leaked through to user space
because task switching didn't save/restore eflags properly. We already
fixed that (same bug as with the NT flag).
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists