All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russ Anderson <rja@sgi.com>
To: Ingo Molnar <mingo@elte.hu>,
	tglx@linutronix.de, linux-kernel@vger.kernel.org
Cc: Huang Ying <ying.huang@intel.com>, Jack Steiner <steiner@sgi.com>,
	Russ Anderson <rja@sgi.com>
Subject: [PATCH 0/7] x86: UV runtime bios calls
Date: Wed, 15 Oct 2008 15:10:58 -0500	[thread overview]
Message-ID: <20081015201058.GA197213@sgi.com> (raw)

[PATCH 0/7] x86: UV runtime bios calls

Resubmit four patches (per Ingo's request) with three additional patches.

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 for UV.

Patches:
	[1/7] uv_efi_bios:	Look for UV entry in EFI tables.

	[2/7] 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.

	[3/7] uv_bios_call_partition: Add call to get partitioning related info.

	[4/7] uv_sysfs:	Create sysfs entrys in /sys/firmware/sgi_uv/ for
			partitioning related information.

	[5/7] uv_bios_call_watchlist:	 Access UV watchlists.
	[6/7] uv_bios_call_memprotect: Modify UV memory protection.
	[7/7] uv_bios_call_reserve_page: Access UV reserve page.

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

                 reply	other threads:[~2008-10-15 20:11 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=20081015201058.GA197213@sgi.com \
    --to=rja@sgi.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 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.