public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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>,
	Huang Ying <ying.huang@intel.com>, Jack Steiner <steiner@sgi.com>,
	Russ Anderson <rja@sgi.com>
Subject: [PATCH 0/4] x86: UV runtime bios calls v2
Date: Fri, 26 Sep 2008 15:01:32 -0500	[thread overview]
Message-ID: <20080926200132.GA138671@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 adds a new EFI table entry
	for UV.  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.

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:	Look for UV entry in EFI tables.

	uv_bios_common:	Add the EFI callback function using the EFI table
			entry.  Create associated wrapper code.  Initialize
			UV 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 adds a new EFI entry type (uv_systab).

	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 supportes 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@sgi.com

                 reply	other threads:[~2008-09-26 20:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080926200132.GA138671@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 \
    --cc=ying.huang@intel.com \
    /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