From: Andy Whitcroft <apw@shadowen.org>
To: alan@lxorguk.ukuu.org.uk, apw@shadowen.org
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tidy AMD 768MPX fix
Date: Fri, 03 Sep 2004 17:46:00 +0100 [thread overview]
Message-ID: <E1C3HCK-0001aU-H4@localhost.localdomain> (raw)
In-Reply-To: <1094225233.8102.16.camel@localhost.localdomain>
> Even if we use a different software page size in some future x86 release
> the workaround is to reserve 4096 bytes. I don't think this change makes
> sense therefore.
I have always assumed that PAGE_SIZE in the bootmem allocator was
hardware page size; such that if software PAGE_SIZE was to change that
it would necessarily be replaced with two different constants. But fair
enough. In that case perhaps we should at least fix the code indent
etc. Revised patch below.
-apw
=== 8< ===
Fix indentation and layout of AMD 768MPX errata #56 fix.
Revision: $Rev: 620 $
Signed-off-by: Andy Whitcroft <apw@shadowen.org>
diffstat 020-tidy-AMD-768MPX-fix
---
setup.c | 10 ++++++----
1 files changed, 6 insertions(+), 4 deletions(-)
diff -X /home/apw/brief/lib/vdiff.excl -rupN reference/arch/i386/kernel/setup.c current/arch/i386/kernel/setup.c
--- reference/arch/i386/kernel/setup.c 2004-09-02 18:05:57.000000000 +0100
+++ current/arch/i386/kernel/setup.c 2004-09-03 17:34:58.000000000 +0100
@@ -1052,12 +1052,14 @@ static unsigned long __init setup_memory
/* reserve EBDA region, it's a 4K region */
reserve_ebda_region();
- /* could be an AMD 768MPX chipset. Reserve a page before VGA to prevent
- PCI prefetch into it (errata #56). Usually the page is reserved anyways,
- unless you have no PS/2 mouse plugged in. */
+ /*
+ * could be an AMD 768MPX chipset. Reserve a page before VGA to
+ * prevent PCI prefetch into it (errata #56). Usually the page is
+ * reserved anyways, unless you have no PS/2 mouse plugged in.
+ */
if (boot_cpu_data.x86_vendor == X86_VENDOR_AMD &&
boot_cpu_data.x86 == 6)
- reserve_bootmem(0xa0000 - 4096, 4096);
+ reserve_bootmem(0xa0000 - 4096, 4096);
#ifdef CONFIG_SMP
/*
next prev parent reply other threads:[~2004-09-03 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 16:13 [PATCH] tidy AMD 768MPX fix Andy Whitcroft
2004-09-03 15:27 ` Alan Cox
2004-09-03 16:46 ` Andy Whitcroft [this message]
2004-09-06 12:34 ` David Woodhouse
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=E1C3HCK-0001aU-H4@localhost.localdomain \
--to=apw@shadowen.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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.