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 v2
Date: Sat, 27 Sep 2008 09:21:35 +0800 [thread overview]
Message-ID: <1222478495.28661.19.camel@yhuang-dev.sh.intel.com> (raw)
In-Reply-To: <20080926200242.GC138671@sgi.com>
[-- Attachment #1: Type: text/plain, Size: 1332 bytes --]
On Fri, 2008-09-26 at 15:02 -0500, Russ Anderson wrote:
> Index: linux/include/asm-x86/efi.h
> ===================================================================
> --- linux.orig/include/asm-x86/efi.h 2008-09-26 14:13:24.000000000 -0500
> +++ linux/include/asm-x86/efi.h 2008-09-26 14:13:36.000000000 -0500
> @@ -49,6 +49,20 @@ extern u64 efi_call5(void *fp, u64 arg1,
> extern u64 efi_call6(void *fp, u64 arg1, u64 arg2, u64 arg3,
> u64 arg4, u64 arg5, u64 arg6);
>
> +
> +#ifndef CONFIG_EFI
> +/*
> + * IF EFI is not configured, have the EFI calls return -ENOSYS.
> + */
> +#define efi_call0(_f) (-ENOSYS)
> +#define efi_call1(_f, _a1) (-ENOSYS)
> +#define efi_call2(_f, _a1, _a2) (-ENOSYS)
> +#define efi_call3(_f, _a1, _a2, _a3) (-ENOSYS)
> +#define efi_call4(_f, _a1, _a2, _a3, _a4) (-ENOSYS)
> +#define efi_call5(_f, _a1, _a2, _a3, _a4, _a5) (-ENOSYS)
> +#define efi_call6(_f, _a1, _a2, _a3, _a4, _a5, _a6) (-ENOSYS)
> +#endif /* CONFIG_EFI */
> +
> #define efi_call_phys0(f) \
> efi_call0((void *)(f))
> #define efi_call_phys1(f, a1) \
efi_call_virt<n> and efi_call_phys<n> is the API instead of efi_call<n>.
And please put the implementation without CONFIG_EFI defined out of
#ifdef CONFIG_X86_32
<...>
#else
<...>
#endif
Best Regards,
Huang Ying
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-09-27 1:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 20:02 Russ Anderson
2008-09-27 1:21 ` Huang Ying [this message]
2008-09-27 16:10 ` Ingo Molnar
2008-09-28 15:01 ` Russ Anderson
2008-09-29 14:31 ` Russ Anderson
2008-10-02 8:05 ` huang ying
2008-10-02 8:02 ` huang ying
2008-10-02 15:34 ` Russ Anderson
2008-10-03 9:10 ` Ingo Molnar
2008-10-07 20:57 ` 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=1222478495.28661.19.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
Powered by JetHome