Files
system76-edk2/OvmfPkg/Include/Protocol/XenIo.h
Antoine Coeur 493dde944d OvmfPkg/Xen: Fix various typos
Fix various typos in comments and documentation.

Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Anthony Perard <anthony.perard@citrix.com>
Cc: Julien Grall <julien@xen.org>
Signed-off-by: Antoine Coeur <coeur@gmx.fr>
Reviewed-by: Philippe Mathieu-Daude <philmd@redhat.com>
Acked-by: Anthony PERARD <anthony.perard@citrix.com>
Acked-by: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: Philippe Mathieu-Daude <philmd@redhat.com>
Message-Id: <20200207010831.9046-61-philmd@redhat.com>
2020-02-10 22:30:07 +00:00

43 lines
1.1 KiB
C

/** @file
XenIo protocol to abstract arch specific details
The Xen implementations for the Intel and ARM architectures differ in the way
the base address of the grant table is communicated to the guest. The former
uses a virtual PCI device, while the latter uses a device tree node.
In order to allow the XenBusDxe UEFI driver to be reused for the non-PCI
Xen implementation, this abstract protocol can be installed on a handle
with the appropriate base address.
Copyright (C) 2014, Linaro Ltd.
SPDX-License-Identifier: BSD-2-Clause-Patent
**/
#ifndef __PROTOCOL_XENIO_H__
#define __PROTOCOL_XENIO_H__
#include <IndustryStandard/Xen/xen.h>
#define XENIO_PROTOCOL_GUID \
{0x6efac84f, 0x0ab0, 0x4747, {0x81, 0xbe, 0x85, 0x55, 0x62, 0x59, 0x04, 0x49}}
///
/// Forward declaration
///
typedef struct _XENIO_PROTOCOL XENIO_PROTOCOL;
///
/// Protocol structure
///
struct _XENIO_PROTOCOL {
//
// Protocol data fields
//
EFI_PHYSICAL_ADDRESS GrantTableAddress;
};
extern EFI_GUID gXenIoProtocolGuid;
#endif