[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200707191052.18107.juergen127@kreuzholzen.de>
Date: Thu, 19 Jul 2007 10:52:16 +0200
From: Juergen Beisert <juergen127@...uzholzen.de>
To: Andres Salomon <dilinger@...ued.net>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
TAKADA Yoshihito <takada@....nifty.com>,
linux-kernel@...r.kernel.org,
Jordan Crouse <jordan.crouse@....com>,
Andres Salomon <dilinger@...ian.org>, Andi Kleen <ak@...e.de>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH 1/1] i386: Geode's TSC is not neccessary to mark tu unstable
On Thursday 19 July 2007 09:17, Andres Salomon wrote:
> On Thu, 19 Jul 2007 08:49:05 +0200
>
> Juergen Beisert <juergen127@...uzholzen.de> wrote:
> > On Thursday 19 July 2007 03:02, Andrew Morton wrote:
> > > On Sun, 15 Jul 2007 21:06:27 +0200
> > >
> > > Juergen Beisert <juergen127@...uzholzen.de> wrote:
> > > > Replace NSC/Cyrix specific chipset access macros by inlined
> > > > functions. With the macros a line like this fails (and does nothing):
> > > > setCx86(CX86_CCR2, getCx86(CX86_CCR2) | 0x88);
> > > > With inlined functions this line will work as expected.
> > >
> > > I don't get it. Why would the macros behave differently from inlined
> > > functions?
> >
> > X86 magic. The access order is important. The first access must always be
> > the offset at 0x22. This access enables the next access to 0x23 (data).
> > If you do it in wrong order, it fails. With the macros you get something
> > like 0x22, 0x22, 0x23, 0x23. With the inline functions
> > 0x22,0x23,0x22,0x23.
> >
> > Juergen
>
> Wow, that's a really cool bug; nice work! Don't forget to update
> arch/i386/kernel/cpu/mtrr/state.c, though; it uses setCx86() as well. It
> needs to include processor-cyrix.h.
>
>
> Acked-by: Andres Salomon <dilinger@...ian.org>
Missing include patch attached. Thanks.
Juergen
View attachment "missing-include.patch" of type "text/x-diff" (323 bytes)
Powered by blists - more mailing lists