mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Huang Ying <ying.huang@intel.com>
To: Russ Anderson <rja@sgi.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@linutronix.de,
	"H. Peter Anvin" <hpa@zytor.com>, Jack Steiner <steiner@sgi.com>
Subject: Re: [PATCH 0/4] x86: UV runtime bios calls
Date: Wed, 24 Sep 2008 10:49:10 +0800	[thread overview]
Message-ID: <1222224550.23099.99.camel@yhuang-dev.sh.intel.com> (raw)
In-Reply-To: <20080922210644.GC222374@sgi.com>

[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]

Hi, Russ,

This seems to include a extension to EFI runtime services. Why not also
discuss that on UEFI forum? You can get some information about UEFI
forum from http://www.uefi.org/.

Best Regards,
Huang Ying

On Mon, 2008-09-22 at 16:06 -0500, Russ Anderson wrote:
> [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.
> 	

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-09-24  2:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 21:06 Russ Anderson
2008-09-24  2:49 ` Huang Ying [this message]
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=1222224550.23099.99.camel@yhuang-dev.sh.intel.com \
    --to=ying.huang@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rja@sgi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®