From: Benjamin LaHaise <bcrl@redhat.com>
To: Andi Kleen <ak@muc.de>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Workaround for AMD762MPX "mouse" bug
Date: Sun, 29 Dec 2002 15:10:49 -0500 [thread overview]
Message-ID: <20021229151049.A16750@redhat.com> (raw)
In-Reply-To: <20021224162501.GA5363@averell>; from ak@muc.de on Tue, Dec 24, 2002 at 05:25:01PM +0100
On Tue, Dec 24, 2002 at 05:25:01PM +0100, Andi Kleen wrote:
> way would be to always reserve that page, but I didn't feel like
> punishing everybody just for a hardware bug in a single chipset.
>
> Patch for 2.5.53. Please consider applying.
That's the wrong way to do it. Workarounds like this need to be automatic,
and with init code sections, there is no excuse not to. Instead of making
the user pass a quirk option, why not reserve the page and then free it if
the errata is not present?
-ben
next prev parent reply other threads:[~2002-12-29 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-24 16:25 [PATCH] Workaround for AMD762MPX "mouse" bug Andi Kleen
2002-12-29 16:51 ` Eric Lammerts
2002-12-29 20:10 ` Benjamin LaHaise [this message]
2002-12-30 10:35 ` Henning P. Schmiedehausen
-- strict thread matches above, loose matches on Subject: below --
2002-12-29 14:46 David Balazic
2002-12-30 0:50 ` Alan Cox
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=20021229151049.A16750@redhat.com \
--to=bcrl@redhat.com \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).