[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20080929220201.GB108640@sgi.com>
Date: Mon, 29 Sep 2008 17:02:04 -0500
From: Russ Anderson <rja@....com>
To: linux-kernel@...r.kernel.org, mingo@...e.hu, tglx@...utronix.de,
Huang Ying <ying.huang@...el.com>
Cc: "H. Peter Anvin" <hpa@...or.com>, Jack Steiner <steiner@....com>,
Russ Anderson <rja@....com>
Subject: [PATCH 0/4] x86: UV runtime bios calls
[PATCH 0/4] x86: UV runtime bios calls
Purpose:
Create an interface to allow calls into bios to return platform
specific information. The interface adds a new EFI runtime call
for OEMs. EFI provides a mechanism for defining runtime calls
to firmware routines. This patchset builds on the EFI mechanism
to provide access to those firmware routines.
Version 3 changes:
Add function (oem) to efi_runtime_services_t, replacing uv_systab.
Use efi_call_virt<n>.
Remove efi_call<n> stubs.
Version 2 changes:
Add uv_systab to efi struct.
Define efi_call* stubs in include/asm-x86/uv/bios.h.
Made symbols EXPORT_SYMBOL_GPL().
Added check for failure on sysfs_create_file() calls.
Other code style changes.
Patches:
uv_efi_bios: Add function (oem) to efi_runtime_services_t.
uv_bios_common: Add the EFI callback function using the EFI oem
runtime function. Create associated wrapper code.
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 adds a new EFI runtime function (oem).
The location in sysfs (/sys/firmware/sgi_uv/) is based on
community feedback. The interface is documented in
Documentation/ABI/testing/sysfs-firmware-sgi_uv.
If EFI is not configured (CONFIG_EFI), the calls will return -ENOSYS.
If run on a system with a bios that does not support EFI UV, 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@....com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists