From: Russ Anderson <rja@sgi.com>
To: linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@linutronix.de
Cc: "H. Peter Anvin" <hpa@zytor.com>, Jack Steiner <steiner@sgi.com>,
Russ Anderson <rja@sgi.com>
Subject: [PATCH 0/4] x86: UV runtime bios calls
Date: Mon, 22 Sep 2008 16:06:44 -0500 [thread overview]
Message-ID: <20080922210644.GC222374@sgi.com> (raw)
[PATCH 0/4] x86: UV runtime bios calls
Purpose:
Create an interface to allow calls into bios to return platform
specific information. The interface uses EFI SAL table entry.
EFI provides a mechanism for defining function pointers to
firmware routines. This patchset builds on the EFI mechanism
to provide access to those firmware routines.
Patches:
uv_efi_bios: Look for SAL entry in EFI tables.
uv_bios_common: Add the EFI callback function using the EFI table
entry. Create associated wrapper code. Initialize
SAL system table entry info at boot time.
uv_bios_call_partition: Add call to get partitioning related info.
uv_sysfs: Create sysfs entrys in /sys/firmware/sgi_uv/ for
partitioning related information.
Implementation comments:
This patch uses sal_systab. sal_systab is used on ia64, but was
not used on x86. An alternative would be to create a new
EFI entry type (uv_systab), though that would require adding
to struct efi.
The location in sysfs (/sys/firmware/sgi_uv/) is based on
community feedback.
If EFI is not configured (CONFIG_EFI), the calls will return -ENOSYS.
If run on a system with a bios that does not supportes EFI SAL, the
calls will return -ENOSYS.
Paul Jackson assisted in the development of this code.
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
next reply other threads:[~2008-09-22 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 21:06 Russ Anderson [this message]
2008-09-24 2:49 ` [PATCH 0/4] x86: UV runtime bios calls Huang Ying
2008-09-24 3:09 ` Huang Ying
2008-09-24 4:24 ` Russ Anderson
-- strict thread matches above, loose matches on Subject: below --
2008-09-29 22:02 Russ Anderson
2008-08-22 21:50 Russ Anderson
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=20080922210644.GC222374@sgi.com \
--to=rja@sgi.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
/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.