From: Martin Hicks <mort@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: 2.6.0 test3 does not boot on ia64 NUMA
Date: Tue, 26 Aug 2003 16:13:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106191478719084@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106191285716253@msgid-missing>
On Tue, Aug 26, 2003 at 05:39:32PM +0200, Xavier Bru wrote:
>
> I tried to put find_memory() after acpi_numa_init() as in 2.5.72, but
> now we get:
> bootmem alloc of 100 bytes failed! in acpi_table_init()
> that now uses the bootmem allocator.
>
> I wonder what should be the right order for initialisation, and if
> there are ia64 platforms running 2.6.0 with CONFIG_NUMA. Any help is
> apreciated.
Jesse Barnes has an unreleased patch to make SGI SN2 work, which does
move the find_memory() after acpi_numa_init(). There is another patch,
which I've attached, which removes the bootmem alloc of memory in ACPI.
I haven't played with this recently, so your mileage may vary. Jesse
should be back from vacation next week, and should release updated SN2
patches then.
mh
--
Wild Open Source Inc. mort@wildopensource.com
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or higher.
# This patch includes the following deltas:
# ChangeSet 1.1395 -> 1.1396
# drivers/acpi/tables.c 1.14 -> 1.15
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 03/07/30 jbarnes@tomahawk.engr.sgi.com 1.1396
# don't use alloc_bootmem in acpi table init
# --------------------------------------------
#
diff -Nru a/drivers/acpi/tables.c b/drivers/acpi/tables.c
--- a/drivers/acpi/tables.c Wed Jul 30 11:45:27 2003
+++ b/drivers/acpi/tables.c Wed Jul 30 11:45:27 2003
@@ -69,7 +69,8 @@
static unsigned long sdt_pa; /* Physical Address */
static unsigned long sdt_count; /* Table count */
-static struct acpi_table_sdt *sdt_entry;
+
+static struct acpi_table_sdt sdt_entry[ACPI_MAX_TABLES];
void
acpi_table_print (
@@ -413,12 +414,6 @@
sdt_count = ACPI_MAX_TABLES;
}
- sdt_entry = alloc_bootmem(sdt_count * sizeof(struct acpi_table_sdt));
- if (!sdt_entry) {
- printk(KERN_ERR "ACPI: Could not allocate mem for SDT entries!\n");
- return -ENOMEM;
- }
-
for (i = 0; i < sdt_count; i++)
sdt_entry[i].pa = (unsigned long) mapped_xsdt->entry[i];
}
@@ -463,12 +458,6 @@
printk(KERN_WARNING PREFIX "Truncated %lu RSDT entries\n",
(sdt_count - ACPI_MAX_TABLES));
sdt_count = ACPI_MAX_TABLES;
- }
-
- sdt_entry = alloc_bootmem(sdt_count * sizeof(struct acpi_table_sdt));
- if (!sdt_entry) {
- printk(KERN_ERR "ACPI: Could not allocate mem for SDT entries!\n");
- return -ENOMEM;
}
for (i = 0; i < sdt_count; i++)
next prev parent reply other threads:[~2003-08-26 16:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 15:39 2.6.0 test3 does not boot on ia64 NUMA Xavier Bru
2003-08-26 16:13 ` Martin Hicks [this message]
2003-08-28 16:38 ` Xavier Bru
2003-08-28 16:59 ` Martin Hicks
2003-08-29 16:41 ` Xavier Bru
2003-08-29 17:07 ` Martin Hicks
2003-09-01 12:36 ` Xavier Bru
2003-09-02 17:27 ` Xavier Bru
2003-09-04 18:31 ` Jesse Barnes
2003-09-04 19:06 ` Luck, Tony
2003-09-04 19:11 ` Jesse Barnes
2003-09-05 9:19 ` Xavier Bru
2003-09-08 19:08 ` Jesse Barnes
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=marc-linux-ia64-106191478719084@msgid-missing \
--to=mort@wildopensource.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox