* All generic sub-operations\r
*\r
* HYPERVISOR_physdev_op\r
- * No sub-operations are currenty supported\r
+ * No sub-operations are currently supported\r
*\r
* HYPERVISOR_sysctl\r
* All generic sub-operations, with the exception of:\r
/*\r
* GNTMAP_contains_pte subflag:\r
* 0 => This map request contains a host virtual address.\r
- * 1 => This map request contains the machine addess of the PTE to update.\r
+ * 1 => This map request contains the machine address of the PTE to update.\r
*/\r
#define _GNTMAP_contains_pte (4)\r
#define GNTMAP_contains_pte (1<<_GNTMAP_contains_pte)\r
/* ` enum grant_status { */\r
#define GNTST_okay (0) /* Normal return. */\r
#define GNTST_general_error (-1) /* General undefined error. */\r
-#define GNTST_bad_domain (-2) /* Unrecognsed domain id. */\r
+#define GNTST_bad_domain (-2) /* Unrecognised domain id. */\r
#define GNTST_bad_gntref (-3) /* Unrecognised or inappropriate gntref. */\r
#define GNTST_bad_handle (-4) /* Unrecognised or inappropriate handle. */\r
#define GNTST_bad_virt_addr (-5) /* Inappropriate virtual address to map. */\r
* access (even when it should be read-only). If the frontend hits the\r
* maximum number of allowed persistently mapped grants, it can fallback\r
* to non persistent mode. This will cause a performance degradation,\r
- * since the the backend driver will still try to map those grants\r
+ * since the backend driver will still try to map those grants\r
* persistently. Since the persistent grants protocol is compatible with\r
* the previous protocol, a frontend driver can choose to work in\r
* persistent mode even when the backend doesn't support it.\r
Grant access to the page Frame to the domain DomainId.\r
\r
@param This A pointer to XENBUS_PROTOCOL instance.\r
- @param DomainId ID of the domain to grant acces to.\r
+ @param DomainId ID of the domain to grant access to.\r
@param Frame Frame Number of the page to grant access to.\r
@param ReadOnly Provide read-only or read-write access.\r
@param RefPtr Reference number of the grant will be written to this pointer.\r
Send an event to the remote end of the channel whose local endpoint is Port.\r
\r
@param This A pointer to the XENBUS_PROTOCOL.\r
- @param Port Local port to the the event from.\r
+ @param Port Local port to the event from.\r
\r
@retval UINT32 The return value from the hypercall, 0 if success.\r
**/\r
/** @file\r
XenIo protocol to abstract arch specific details\r
\r
- The Xen implementations for the Intel and ARM archictures differ in the way\r
+ The Xen implementations for the Intel and ARM architectures differ in the way\r
the base address of the grant table is communicated to the guest. The former\r
uses a virtual PCI device, while the latter uses a device tree node.\r
In order to allow the XenBusDxe UEFI driver to be reused for the non-PCI\r
//\r
if (Pci.Bridge.SubordinateBus > SubBus) {\r
//\r
- // If the suborinate bus number of the PCI-PCI bridge is greater\r
+ // If the subordinate bus number of the PCI-PCI bridge is greater\r
// than the PCI root bridge's current subordinate bus number,\r
// then update the PCI root bridge's subordinate bus number\r
//\r
\r
//\r
// See if the PCI Device is a PCI - ISA or PCI - EISA\r
- // or ISA_POSITIVIE_DECODE Bridge device\r
+ // or ISA_POSITIVE_DECODE Bridge device\r
//\r
if (Pci.Hdr.ClassCode[2] == PCI_CLASS_BRIDGE) {\r
if (Pci.Hdr.ClassCode[1] == PCI_CLASS_BRIDGE_ISA ||\r
}\r
\r
/**\r
- Sets the baud rate, receive FIFO depth, transmit/receice time out, parity,\r
+ Sets the baud rate, receive FIFO depth, transmit/receive time out, parity,\r
data bits, and stop bits on a serial device.\r
\r
@param BaudRate The requested baud rate. A BaudRate value of 0 will use the\r
device's default interface speed.\r
On output, the value actually set.\r
- @param ReveiveFifoDepth The requested depth of the FIFO on the receive side of the\r
+ @param ReceiveFifoDepth The requested depth of the FIFO on the receive side of the\r
serial interface. A ReceiveFifoDepth value of 0 will use\r
the device's default FIFO depth.\r
On output, the value actually set.\r
DefaultParity will use the device's default parity value.\r
On output, the value actually set.\r
@param DataBits The number of data bits to use on the serial device. A DataBits\r
- vaule of 0 will use the device's default data bit setting.\r
+ value of 0 will use the device's default data bit setting.\r
On output, the value actually set.\r
@param StopBits The number of stop bits to use on this serial device. A StopBits\r
value of DefaultStopBits will use the device's default number of\r
@retval EFI_SUCCESS The device was started.\r
@retval EFI_DEVICE_ERROR The device could not be started due to a device error.Currently not implemented.\r
@retval EFI_OUT_OF_RESOURCES The request could not be completed due to a lack of resources.\r
- @retval Others The driver failded to start the device.\r
+ @retval Others The driver failed to start the device.\r
\r
**/\r
EFI_STATUS\r
Send an event to the remote end of the channel whose local endpoint is Port.\r
\r
@param This A pointer to the XENBUS_PROTOCOL.\r
- @param Port Local port to the the event from.\r
+ @param Port Local port to the event from.\r
\r
@retval UINT32 The return value from the hypercall, 0 if success.\r
**/\r
Grant access to the page Frame to the domain DomainId.\r
\r
@param This A pointer to XENBUS_PROTOCOL instance.\r
- @param DomainId ID of the domain to grant acces to.\r
+ @param DomainId ID of the domain to grant access to.\r
@param Frame Frame Number of the page to grant access to.\r
@param ReadOnly Provide read-only or read-write access.\r
@param RefPtr Reference number of the grant will be written to this pointer.\r
/** @file\r
- XenBus Bus driver implemtation.\r
+ XenBus Bus driver implementation.\r
\r
This file implement the necessary to discover and enumerate Xen PV devices\r
through XenStore.\r
/** @file\r
This driver produces XenBus Protocol instances for each Xen PV devices.\r
\r
- This XenBus bus driver will first initialize differente services in order to\r
+ This XenBus bus driver will first initialize different services in order to\r
enumerate the ParaVirtualized devices available.\r
\r
Those services are:\r
@retval EFI_DEVICE_ERROR The device could not be started due to a device error.Currently not implemented.\r
@retval EFI_OUT_OF_RESOURCES The request could not be completed due to a lack of resources.\r
@retval EFI_UNSUPPORTED Something is missing on the system that\r
- prevent to start the edvice.\r
- @retval Others The driver failded to start the device.\r
+ prevent to start the device.\r
+ @retval Others The driver failed to start the device.\r
\r
**/\r
EFI_STATUS\r
*/\r
LIST_ENTRY WatchEvents;\r
\r
- /** Lock protecting the watch calback list. */\r
+ /** Lock protecting the watch callback list. */\r
EFI_LOCK WatchEventsLock;\r
\r
/**\r
}\r
\r
/**\r
- Send a message with an optionally muti-part body to the XenStore service.\r
+ Send a message with an optionally multi-part body to the XenStore service.\r
\r
@param Transaction The transaction to use for this request.\r
@param RequestType The type of message to send.\r
@param FromBackend Read frontend or backend value.\r
@param ValuePtr Where to put the value.\r
\r
- @retval XENSTORE_STATUS_SUCCESS If succefull, will update ValuePtr.\r
+ @retval XENSTORE_STATUS_SUCCESS If successful, will update ValuePtr.\r
@return Any other return value indicate the error,\r
ValuePtr is not updated in this case.\r
**/\r
/**\r
Read/Write BufferSize bytes from Lba into Buffer.\r
\r
- This function is commun to XenPvBlkDxeBlockIoReadBlocks and\r
+ This function is common to XenPvBlkDxeBlockIoReadBlocks and\r
XenPvBlkDxeBlockIoWriteBlocks.\r
\r
@param This Indicates a pointer to the calling context.\r
@retval EFI_SUCCESS The data was read correctly from the device.\r
@retval EFI_DEVICE_ERROR The device reported an error while performing the read.\r
@retval EFI_NO_MEDIA There is no media in the device.\r
- @retval EFI_MEDIA_CHANGED The MediaId does not matched the current device.\r
+ @retval EFI_MEDIA_CHANGED The MediaId does not match the current device.\r
@retval EFI_BAD_BUFFER_SIZE The Buffer was not a multiple of the block size of the device.\r
@retval EFI_INVALID_PARAMETER The read request contains LBAs that are not valid,\r
or the buffer is not on proper alignment.\r
@retval EFI_WRITE_PROTECTED The device can not be written to.\r
@retval EFI_DEVICE_ERROR The device reported an error while performing the write.\r
@retval EFI_NO_MEDIA There is no media in the device.\r
- @retval EFI_MEDIA_CHNAGED The MediaId does not matched the current device.\r
+ @retval EFI_MEDIA_CHANGED The MediaId does not match the current device.\r
@retval EFI_BAD_BUFFER_SIZE The Buffer was not a multiple of the block size of the device.\r
@retval EFI_INVALID_PARAMETER The write request contains LBAs that are not valid,\r
or the buffer is not on proper alignment.\r
@param This Indicates a pointer to the calling context.\r
\r
@retval EFI_SUCCESS All outstanding data was written to the device\r
- @retval EFI_DEVICE_ERROR The device reported an error while writting back the data\r
+ @retval EFI_DEVICE_ERROR The device reported an error while writing back the data\r
@retval EFI_NO_MEDIA There is no media in the device.\r
\r
**/\r
@retval EFI_SUCCESS The data was read correctly from the device.\r
@retval EFI_DEVICE_ERROR The device reported an error while performing the read.\r
@retval EFI_NO_MEDIA There is no media in the device.\r
- @retval EFI_MEDIA_CHANGED The MediaId does not matched the current device.\r
+ @retval EFI_MEDIA_CHANGED The MediaId does not match the current device.\r
@retval EFI_BAD_BUFFER_SIZE The Buffer was not a multiple of the block size of the device.\r
@retval EFI_INVALID_PARAMETER The read request contains LBAs that are not valid,\r
or the buffer is not on proper alignment.\r
@retval EFI_WRITE_PROTECTED The device can not be written to.\r
@retval EFI_DEVICE_ERROR The device reported an error while performing the write.\r
@retval EFI_NO_MEDIA There is no media in the device.\r
- @retval EFI_MEDIA_CHNAGED The MediaId does not matched the current device.\r
+ @retval EFI_MEDIA_CHANGED The MediaId does not match the current device.\r
@retval EFI_BAD_BUFFER_SIZE The Buffer was not a multiple of the block size of the device.\r
@retval EFI_INVALID_PARAMETER The write request contains LBAs that are not valid,\r
or the buffer is not on proper alignment.\r
@param This Indicates a pointer to the calling context.\r
\r
@retval EFI_SUCCESS All outstanding data was written to the device\r
- @retval EFI_DEVICE_ERROR The device reported an error while writting back the data\r
+ @retval EFI_DEVICE_ERROR The device reported an error while writing back the data\r
@retval EFI_NO_MEDIA There is no media in the device.\r
\r
**/\r
@retval EFI_SUCCESS The device was started.\r
@retval EFI_DEVICE_ERROR The device could not be started due to a device error.Currently not implemented.\r
@retval EFI_OUT_OF_RESOURCES The request could not be completed due to a lack of resources.\r
- @retval Others The driver failded to start the device.\r
+ @retval Others The driver failed to start the device.\r
\r
**/\r
EFI_STATUS\r
@retval EFI_SUCCESS The device was started.\r
@retval EFI_DEVICE_ERROR The device could not be started due to a device error.Currently not implemented.\r
@retval EFI_OUT_OF_RESOURCES The request could not be completed due to a lack of resources.\r
- @retval Others The driver failded to start the device.\r
+ @retval Others The driver failed to start the device.\r
\r
**/\r
EFI_STATUS\r