diff options
author | Laszlo Ersek <lersek@redhat.com> | 2015-03-03 08:13:30 +0000 |
---|---|---|
committer | lersek <lersek@Edk2> | 2015-03-03 08:13:30 +0000 |
commit | 02f69a25f0aa9f6dda38e2b72789136574928f93 (patch) | |
tree | 691d5509b99d01c7bcc9a3118d188db2326b0be5 | |
parent | b5d85f622105298f142c0df88370db540a2cc900 (diff) | |
download | edk2-platforms-02f69a25f0aa9f6dda38e2b72789136574928f93.tar.xz |
OvmfPkg: XenHypercallLib: introduce XenHypercallIsAvailable()
Similarly to QemuFwCfgLib, we prefer mellow library construction code and
an explicit "are you available" query function in the XenHypercallLib
class. In this step we introduce that query function, but move no client
code to it yet.
Suggested-by: Jordan Justen <jordan.l.justen@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Tested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@17000 6f19259b-4bc3-4df7-8a09-765794883524
-rw-r--r-- | OvmfPkg/Include/Library/XenHypercallLib.h | 16 | ||||
-rw-r--r-- | OvmfPkg/Library/XenHypercallLib/ArmXenHypercall.c | 19 | ||||
-rw-r--r-- | OvmfPkg/Library/XenHypercallLib/X86XenHypercall.c | 19 |
3 files changed, 54 insertions, 0 deletions
diff --git a/OvmfPkg/Include/Library/XenHypercallLib.h b/OvmfPkg/Include/Library/XenHypercallLib.h index 1a468ea7dc..509855d302 100644 --- a/OvmfPkg/Include/Library/XenHypercallLib.h +++ b/OvmfPkg/Include/Library/XenHypercallLib.h @@ -17,6 +17,22 @@ #define __XEN_HYPERCALL_LIB_H__
/**
+ Check if the Xen Hypercall library is able to make calls to the Xen
+ hypervisor.
+
+ Client code should call further functions in this library only if, and after,
+ this function returns TRUE.
+
+ @retval TRUE Hypercalls are available.
+ @retval FALSE Hypercalls are not available.
+**/
+BOOLEAN
+EFIAPI
+XenHypercallIsAvailable (
+ VOID
+ );
+
+/**
This function will put the two arguments in the right place (registers) and
invoke the hypercall identified by HypercallID.
diff --git a/OvmfPkg/Library/XenHypercallLib/ArmXenHypercall.c b/OvmfPkg/Library/XenHypercallLib/ArmXenHypercall.c index 1f213d6e6f..58cd3ec76b 100644 --- a/OvmfPkg/Library/XenHypercallLib/ArmXenHypercall.c +++ b/OvmfPkg/Library/XenHypercallLib/ArmXenHypercall.c @@ -15,6 +15,25 @@ #include <Base.h>
+/**
+ Check if the Xen Hypercall library is able to make calls to the Xen
+ hypervisor.
+
+ Client code should call further functions in this library only if, and after,
+ this function returns TRUE.
+
+ @retval TRUE Hypercalls are available.
+ @retval FALSE Hypercalls are not available.
+**/
+BOOLEAN
+EFIAPI
+XenHypercallIsAvailable (
+ VOID
+ )
+{
+ return TRUE;
+}
+
RETURN_STATUS
EFIAPI
XenHypercallLibInit (
diff --git a/OvmfPkg/Library/XenHypercallLib/X86XenHypercall.c b/OvmfPkg/Library/XenHypercallLib/X86XenHypercall.c index 7ee1f2f38d..67892bcf37 100644 --- a/OvmfPkg/Library/XenHypercallLib/X86XenHypercall.c +++ b/OvmfPkg/Library/XenHypercallLib/X86XenHypercall.c @@ -19,6 +19,25 @@ WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED. STATIC VOID *HyperPage;
+/**
+ Check if the Xen Hypercall library is able to make calls to the Xen
+ hypervisor.
+
+ Client code should call further functions in this library only if, and after,
+ this function returns TRUE.
+
+ @retval TRUE Hypercalls are available.
+ @retval FALSE Hypercalls are not available.
+**/
+BOOLEAN
+EFIAPI
+XenHypercallIsAvailable (
+ VOID
+ )
+{
+ return HyperPage != NULL;
+}
+
//
// Interface exposed by the ASM implementation of the core hypercall
//
|