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 2/4] x86: Add UV bios call infrastructure
Date: Wed, 24 Sep 2008 11:20:57 +0800	[thread overview]
Message-ID: <1222226457.23099.114.camel@yhuang-dev.sh.intel.com> (raw)
In-Reply-To: <20080922210928.GE222374@sgi.com>

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

Hi, Russ,

On Mon, 2008-09-22 at 16:09 -0500, Russ Anderson wrote:
> +
> +s64 uv_bios_call(int which, u64 a1, u64 a2, u64 a3, u64 a4, u64 a5)
>  {
> -	const char *str;
> -	switch (status) {
> -	case  0: str = "Call completed without error";	break;
> -	case -1: str = "Not implemented";		break;
> -	case -2: str = "Invalid argument";		break;
> -	case -3: str = "Call completed with error";	break;
> -	default: str = "Unknown BIOS status code";	break;
> -	}
> -	return str;
> +	struct sal_systab *tab = &sal_systab;
> +
> +	if (tab->function == (unsigned long)NULL)
> +		/*
> +		 * BIOS does not support SAL systab
> +		 */
> +		return BIOS_STATUS_UNIMPLEMENTED;
> +
> +	return efi_call6((void *)__va(tab->function),
> +					which, a1, a2, a3, a4, a5);
>  }
[...]
> +#else	/* !CONFIG_EFI */
> +/*
> + * IF EFI is not configured, have the EFI calls return unimplemented.
> + */
> +u64 efi_call6(void *fp, u64 arg1, u64 arg2, u64 arg3,
> +			u64 arg4, u64 arg5, u64 arg6)
> +{
> +	return  BIOS_STATUS_UNIMPLEMENTED;
> +}
> +
> +void uv_bios_init(void) { }
> +#endif
> +
[...]
> +
> +#ifndef CONFIG_EFI
> +extern u64 efi_call6(void *, u64, u64, u64, u64, u64, u64);
> +#endif

Either wrap efi_call6() in uv_bios_call() inside #ifdef CONFIG_EFI, or
add efi_call<x>() implementation when CONFIG_EFI is undefined into
include/asm-x86/efi.h.

Best Regards,
Huang Ying


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

  parent reply	other threads:[~2008-09-24  3:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 21:09 Russ Anderson
2008-09-22 22:07 ` H. Peter Anvin
2008-09-22 22:18   ` Russ Anderson
2008-09-23 11:07 ` Ingo Molnar
2008-09-24  3:20 ` Huang Ying [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-08-22 21:53 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=1222226457.23099.114.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®