From: Alex Williamson <alex.williamson@hp.com>
To: linux-ia64@vger.kernel.org
Subject: [PATCH] Move dmi_scan_machine() call ealier
Date: Tue, 06 Nov 2007 17:31:07 +0000 [thread overview]
Message-ID: <1194370267.31834.176.camel@bling> (raw)
I'd like to move our call to dmi_scan_machine up earlier in the boot
process so that we can take advantage of a DMI hook, called out of
acpi_early_init, to enable _OSI(Linux) on Xen HVM domains. Since the
SMBIOS parsing makes use of ioremap, which Bjorn pointed out is fragile
early in boot, I'm reluctant to move this too much earlier. Given those
restrictions, it seems best to simply move this up into our check_bugs
function. Since the DMI hooks are mainly used for adjusting code path
based on platform, it doesn't seem like such an unreasonable place to
set it up. Please let me know if you have comments. Thanks,
Alex
Signed-off-by: Alex Williamson <alex.williamson@hp.com>
--
diff -r c7f1be4e5832 arch/ia64/kernel/setup.c
--- a/arch/ia64/kernel/setup.c Thu Nov 01 12:09:33 2007 -0700
+++ b/arch/ia64/kernel/setup.c Tue Nov 06 09:17:32 2007 -0700
@@ -982,11 +982,5 @@ check_bugs (void)
{
ia64_patch_mckinley_e9((unsigned long) __start___mckinley_e9_bundles,
(unsigned long) __end___mckinley_e9_bundles);
-}
-
-static int __init run_dmi_scan(void)
-{
dmi_scan_machine();
- return 0;
-}
-core_initcall(run_dmi_scan);
+}
next reply other threads:[~2007-11-06 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 17:31 Alex Williamson [this message]
2007-11-07 7:15 ` [PATCH] Move dmi_scan_machine() call ealier Simon Horman
2007-11-07 15:14 ` Alex Williamson
2007-11-07 16:30 ` Luck, Tony
2007-11-07 16:40 ` Alex Williamson
2007-11-08 1:59 ` Simon Horman
2007-11-08 2:00 ` Simon Horman
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=1194370267.31834.176.camel@bling \
--to=alex.williamson@hp.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