From: Andi Kleen <andi@firstfloor.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Andi Kleen <andi@firstfloor.org>,
Peter Fordham <peter.fordham@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: fpu IO port reservation (arch/i386)
Date: Fri, 21 Sep 2007 21:30:35 +0200 [thread overview]
Message-ID: <20070921193035.GA16811@one.firstfloor.org> (raw)
In-Reply-To: <Pine.LNX.4.64N.0709211724470.2724@blysk.ds.pg.gda.pl>
> For the curious the details of all the hassle are reasonably well
> described in the Intel's AP-578 application note.
Thanks. Ok it has to stay for for i386 then; although it would be in theory
possible to only reserve when the CPU is a real 386. For x86-64 it's
gone now.
-Andi
next prev parent reply other threads:[~2007-09-21 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 13:22 fpu IO port reservation (arch/i386) Peter Fordham
2007-09-21 13:52 ` Maciej W. Rozycki
2007-09-21 16:22 ` Andi Kleen
2007-09-21 16:52 ` Maciej W. Rozycki
2007-09-21 19:30 ` Andi Kleen [this message]
2007-09-24 11:42 ` Maciej W. Rozycki
2007-09-28 19:33 ` Bill Davidsen
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=20070921193035.GA16811@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=peter.fordham@gmail.com \
/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