From: Horms <horms@verge.net.au>
To: linux-ia64@vger.kernel.org
Subject: [patch 3/5] Dont map PAL memory if physicall calls are going to be made
Date: Mon, 23 Oct 2006 08:48:43 +0000 [thread overview]
Message-ID: <20061023090334.467483535@tabatha.lab.ultramonkey.org> (raw)
There seems to be no reason to map the PAL code into memory if
physical calls are going to be made.
Signed-Off-By: Simon Horman <horms@verge.net.au>
arch/ia64/kernel/efi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: kexec-ia64-2.6/arch/ia64/kernel/efi.c
=================================--- kexec-ia64-2.6.orig/arch/ia64/kernel/efi.c 2006-10-05 12:51:49.000000000 +0900
+++ kexec-ia64-2.6/arch/ia64/kernel/efi.c 2006-10-05 12:52:10.000000000 +0900
@@ -527,7 +528,6 @@
}
#endif
- efi_map_pal_code();
efi_enter_virtual_mode();
}
@@ -601,6 +601,8 @@
efi.set_variable = virt_set_variable;
efi.get_next_high_mono_count = virt_get_next_high_mono_count;
efi.reset_system = virt_reset_system;
+
+ efi_map_pal_code();
}
/*
--
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
next reply other threads:[~2006-10-23 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 8:48 Horms [this message]
2006-10-24 19:47 ` [patch 3/5] Dont map PAL memory if physicall calls are going to be made Jack Steiner
2006-10-25 7:12 ` Horms
2006-12-13 2:00 ` Horms
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=20061023090334.467483535@tabatha.lab.ultramonkey.org \
--to=horms@verge.net.au \
--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