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>
This commit is contained in:
Antoine Coeur
2020-02-07 02:08:13 +01:00
committed by mergify[bot]
parent 38c92f7030
commit 493dde944d
18 changed files with 31 additions and 31 deletions

View File

@@ -96,7 +96,7 @@
* All generic sub-operations
*
* HYPERVISOR_physdev_op
* No sub-operations are currenty supported
* No sub-operations are currently supported
*
* HYPERVISOR_sysctl
* All generic sub-operations, with the exception of:

View File

@@ -365,7 +365,7 @@ DEFINE_XEN_GUEST_HANDLE(gnttab_unmap_grant_ref_t);
/*
* GNTMAP_contains_pte subflag:
* 0 => This map request contains a host virtual address.
* 1 => This map request contains the machine addess of the PTE to update.
* 1 => This map request contains the machine address of the PTE to update.
*/
#define _GNTMAP_contains_pte (4)
#define GNTMAP_contains_pte (1<<_GNTMAP_contains_pte)
@@ -386,7 +386,7 @@ DEFINE_XEN_GUEST_HANDLE(gnttab_unmap_grant_ref_t);
/* ` enum grant_status { */
#define GNTST_okay (0) /* Normal return. */
#define GNTST_general_error (-1) /* General undefined error. */
#define GNTST_bad_domain (-2) /* Unrecognsed domain id. */
#define GNTST_bad_domain (-2) /* Unrecognised domain id. */
#define GNTST_bad_gntref (-3) /* Unrecognised or inappropriate gntref. */
#define GNTST_bad_handle (-4) /* Unrecognised or inappropriate handle. */
#define GNTST_bad_virt_addr (-5) /* Inappropriate virtual address to map. */

View File

@@ -270,7 +270,7 @@
* access (even when it should be read-only). If the frontend hits the
* maximum number of allowed persistently mapped grants, it can fallback
* to non persistent mode. This will cause a performance degradation,
* since the the backend driver will still try to map those grants
* since the backend driver will still try to map those grants
* persistently. Since the persistent grants protocol is compatible with
* the previous protocol, a frontend driver can choose to work in
* persistent mode even when the backend doesn't support it.

View File

@@ -215,7 +215,7 @@ XENSTORE_STATUS
Grant access to the page Frame to the domain DomainId.
@param This A pointer to XENBUS_PROTOCOL instance.
@param DomainId ID of the domain to grant acces to.
@param DomainId ID of the domain to grant access to.
@param Frame Frame Number of the page to grant access to.
@param ReadOnly Provide read-only or read-write access.
@param RefPtr Reference number of the grant will be written to this pointer.
@@ -266,7 +266,7 @@ UINT32
Send an event to the remote end of the channel whose local endpoint is Port.
@param This A pointer to the XENBUS_PROTOCOL.
@param Port Local port to the the event from.
@param Port Local port to the event from.
@retval UINT32 The return value from the hypercall, 0 if success.
**/

View File

@@ -1,7 +1,7 @@
/** @file
XenIo protocol to abstract arch specific details
The Xen implementations for the Intel and ARM archictures differ in the way
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