# Patent

## Title
Virtualised interface functions

## Abstract

Roughly described, a data processing system comprises a memory addressable by a range of physical memory addresses; a plurality of non-privileged software domains each having a virtual memory address space; a privileged software domain; a memory management unit operable to perform virtual address translation of a virtual memory address into a physical memory address; and an I/O device supporting virtualised interfaces each associated with a respective non-privileged software domain, the I/O device comprising an operation management unit operable to perform virtual address translation in one or more of the virtual memory address spaces; wherein, for I/O operations requested by a virtualised interface, the I/O device invokes the operation management unit to perform virtual address translation for those I/O operations meeting first criteria and to invoke the memory management unit to perform virtual address translation for those I/O operations which do not meet the first criteria.

## Background
BACKGROUND OF THE INVENTION
This invention relates to data transfer in a data processing system supporting virtualised input/output devices. In particular, this invention relates to an improved technique by which translation and protection of virtual memory addresses is performed in a virtualised data processing system.
High performance I/O (input/output) devices of a data processing system are typically able to access host memory directly via Direct Memory Access (DMA). That is, they are able to read the contents of memory and write data to memory directly, without mediation by host software. The addresses from which a device reads and to which it writes are typically supplied by a device driver.
With reference to FIG. 1, in some systems the addresses used by a device 103 to access host memory 101 do not correspond directly with physical memory addresses. In these systems, I/O addresses on the I/O bus 104 must be translated into machine physical addresses on the system bus 105. This translation is generally performed at a device called an I/O Memory Management Unit (IOMMU) 102. An IOMMU may perform either or both of translation services (converting I/O addresses to machine physical addresses) and protection services (limiting the range of machine physical addresses that are accessible by individual devices, or all devices on an I/O bus).
To maintain the integrity of a data processing system it is essential that an I/O device only write into regions of host memory that are intended for I/O. In conventional monolithic systems, the device driver for an I/O device is a trusted component of the system that is generally supported at the kernel, and so can be relied upon to supply valid addresses for I/O buffers in host memory.
In virtualised systems, a single host supports multiple guest system images, each running an untrusted operating system instance. The host and guests are managed by a trusted hypervisor (or more generally a privileged software domain or domains). Typically only the hypervisor has direct access to I/O devices, and forwards I/O requests from guests via a software indirection. Guests cannot be given direct access to the physical interface of conventional I/O devices which are designed to be exclusively accessed by a single trusted device driver, and because a device driver of a guest operating system is not trusted to supply valid addresses for DMA.
The mediation of the hypervisor in the I/O path adds significant overhead and reduces performance through additional processing, context switches and copy operations. In order to address this inefficiency it is desirable to grant guests direct access to I/O devices. This can be achieved in paravirtualised systems whilst maintaining system integrity by arranging that:

    (i) I/O devices provide multiple virtual interfaces; at least one for each guest that will access the device directly.
    (ii) addresses supplied to the I/O device by device drivers in untrusted guests are translated in a secure manner to machine physical addresses that correspond to memory allocated to the guest.


The second requirement is necessary to ensure that a guest cannot compromise system integrity by causing the I/O device to write to areas of host memory belonging to other guests or the hypervisor, and to prevent the guest reading from areas of memory it is not authorised to access. Translation and protection of guest I/O addresses to machine physical addresses is conventionally performed at a system IOMMU.
The PCI-IOV (Peripheral Component Interconnect—I/O Virtualisation) architecture was designed to address the problem of supporting DMA by I/O devices using addresses supplied by untrusted guests. PCI-IOV defines a standard by which a device can export multiple interfaces (one to each guest) and perform secure address translation and protection for DMA transfers on a per-guest basis. In the PCI-IOV architecture the translation and protection are performed in an IOMMU.
Under the PCI-IOV standard, each of the exported interfaces is referred to as a Virtual Function (VF). A guest is given direct access to a VF which it uses to initiate I/O requests. Each device also has at least one Physical Function (PF) that is typically used by a privileged device driver in the hypervisor to manage the device, and may also be used in some cases for control and data-path operations. A PF is the physical interface defined by the PCI Express base specification to which PCI-IOV is an extension.
Each VF and PF is assigned a unique Requester ID (RID). By extension, each RID is therefore associated with a particular protection domain (guest or hypervisor) of a virtualised system. When an I/O device initiates an I/O operation request using an I/O address supplied by a guest (by means of a VF), it uses that guest's RID in the request so that the IOMMU (referred to as a Translation Agent (TA) under the PCI-IOV standard) can translate the guest I/O address to a machine physical address accessible to the I/O bus. Typically, the I/O addresses used by a PF are not translated—or have a simple fixed translation—and require no protection.
Under the PCI-IOV standard, a guest can invoke an I/O device via a VF to request an I/O operation, specifying one or more guest I/O addresses. In response the device issues requests on the I/O bus with the RID that corresponds to the guest. The IOMMU uses the RID to identify a mapping from guest I/O addresses to machine physical addresses of memory accessible to the guest. The IOMMU issues an error if the I/O address is not valid for the particular protection domain (guest).
The translation of addresses at the IOMMU can be a bottleneck for a virtualised data processing system. To address this, some I/O devices are able to request that addresses be pre-translated by the IOMMU, and the translated addresses are cached on the I/O device. The device can then issue requests with the pre-translated addresses, and when it does so it tells the IOMMU that no further translation is needed. The protocol for managing the caching of translations over PCI is formalised in the Address Translation Services (ATS) specification. However, this scheme is complex and expensive to implement in terms of hardware and software design.
There is therefore a need for an improved technique by which translation and protection is performed in a system supporting virtualised I/O devices.
SUMMARY OF THE INVENTION
According to a first aspect of the present invention there is provided a data processing system comprising: a memory addressable by a range of physical memory addresses; a plurality of non-privileged software domains each having a virtual memory address space; at least one privileged software domain; a memory management unit operable to perform virtual address translation of a virtual memory address into a physical memory address; and an input and/or output device supporting a plurality of virtualised interfaces, each virtualised interface being associated with a respective one of the non-privileged software domains, the input and/or output device further comprising at least one operation management unit operable to perform virtual address translation in one or more of the virtual memory address spaces; wherein, for I/O operations requested by a virtualised interface of the input and/or output device, the input and/or output device is configured to invoke the operation management unit to perform virtual address translation for those I/O operations meeting one or more predefined first criteria and to invoke the memory management unit to perform virtual address translation for those I/O operations which do not meet the one or more predefined first criteria.
Preferably each virtualised interface of the input and/or output device is assigned a unique identifier, and an I/O operation requested by a particular virtualised interface uses the identifier of that interface. Preferably the input and/or output device provides a physical interface having a unique identifier. Preferably the input and/or output device is configured to use the identifier of its physical interface for those I/O operations which meet the one or more predefined first criteria.
Preferably the operation management unit is further operable to perform memory protection by preventing I/O operations requested by a particular virtualised interface of the Input and/or output device from accessing areas of the memory which the software domain associated with that virtualised interface is not permitted to access, and the input and/or output device is further configured to invoke the operation management unit to perform memory protection for the said input and/or output operations meeting one or more predefined second criteria.
Preferably the memory management unit is further operable to perform memory protection by preventing I/O operations requested by a particular virtualised interface of the input and/or output device from accessing areas of the memory which the software domain associated with that virtualised interface is not permitted to access, and the input and/or output device is further configured to invoke the memory management unit to perform memory protection for the said input and/or output operations which do not meet the one or more predefined second criteria.
Suitably the predefined first and second criteria are the same criteria.
Suitably the predefined first and second criteria are chosen such that the operation management unit is configured to perform virtual address translation for all I/O operations requested by at least one virtualised interface of the input and/or output device and the memory management unit is configured to perform memory protection for all those I/O operations.
Suitably the predefined first and second criteria are chosen such that the operation management unit is configured to perform memory protection for all I/O operations requested by at least one virtualised interface of the input and/or output device and the memory management unit is configured to perform virtual address translation for all those I/O operations.
Preferably the input and/or output device is configured to use the identifier of its physical interface for those I/O operations which meet the one or more predefined first criteria and the one or more predefined second criteria.
Preferably the input and/or output device is configured to use the identifier of the virtualised interface requesting the I/O operation for those I/O operations which do not meet either the one or more predefined first criteria or the one or more predefined second criteria.
Preferably the one or more predefined second criteria include the identifier of the virtualised interface such that memory protection for a particular I/O operation is selectively performed at the memory management unit or the operation management unit in dependence on which virtualised interface is requesting the I/O operation.
Preferably the one or more predefined first criteria include the identifier of the virtualised interface such that virtual address translation for a particular I/O operation is selectively performed at the memory management unit or the operation management unit in dependence on which virtualised interface is requesting the I/O operation.
Suitably the one or more predefined first criteria includes the type of I/O operation. Suitably the one or more predefined second criteria includes the type of I/O operation.
The input and/or output device may be a network interface device. The I/O operation types may include DMA reads, DMA writes, control path operations, data path operations and an interrupts. Preferably the one or more predefined first criteria are chosen such that virtual address translation for I/O operations belonging to a control path are performed at the memory management unit and virtual address translation for I/O operations belonging to the data path are performed at the operation management unit. I/O operations belonging to the control path may include descriptor fetches, interrupts, configuration operations and notification operations. Preferably the one or more predefined first criteria are chosen such that virtual address translation for data transmission operations and interrupts are performed at the memory management unit and virtual address translation for data reception operations, descriptor operations and completion operations are performed at the operation management unit.
Suitably at least one of the non-privileged software domains supports at least one application having a lower privilege level than its supporting domain, each application being granted access to the virtualised interface associated with its supporting domain and to an application memory address space within the address space of the supporting domain. Preferably, for I/O operations requested on behalf of an application, the input and/or output device is configured to: (i) at the operation management unit, perform translation of an application memory address into a virtual memory address of the supporting domain; and (ii) subsequently, invoke the memory management unit to perform virtual address translation of the virtual memory address into a physical memory address.
Preferably each application is granted direct access to a sub-interface of the virtualised interface of the supporting domain and each sub-interface is assigned a unique identifier. Preferably the one or more predefined first criteria are chosen such that the memory management unit performs virtual address translation of the virtual memory address into a physical memory address
Preferably the predefined criteria are stored at the input and/or output device. Preferably a device driver supported at the privileged software domain is configured to maintain the predefined criteria stored at the input and/or output device.
Preferably the input and/or output device comprises a plurality of the said operation management units, each operation management unit being supported at one of the virtualised interfaces, and, on invoking the operation management unit, the input and/or output device is configured to invoke the instance of the operation management unit supported at the virtualised interface requesting the I/O operation.
Preferably the privileged software domain maintains a memory address translation table. Preferably the input and/or output device maintains a copy of the translation table.
Suitably the privileged software domain is a hypervisor and the non-privileged software domains are guest operating systems supported by the hypervisor.
Suitably the privileged software domain is an operating system kernel and the non-privileged software domains are user level entities supported by the kernel.
Suitably the input and/or output device is a PCI Express device and the virtualised interfaces of the input and/or output device are provided in accordance with the PCI-IOV specification. Each identifier may be a PCI Requester ID.
According to a second aspect of the present invention there is provided a method for handling virtual memory addresses at a data processing system comprising a memory and an input and/or output device, the data processing system supporting (a) at least one privileged software domain and (b) a plurality of non-privileged software domains each having a virtual memory address space and each being associated with a respective virtualised interface of the input and/or output device, the method comprising: receiving at a virtualised interface of the input and/or output device at least one virtual memory address from the respective one of the non-privileged software domains; the virtualised interface requesting an I/O operation using the at least one virtual memory address; determining at the input and/or output device whether the I/O operation request meets one or more predefined first criteria; and: if the one or more first criteria are met, performing translation of the virtual memory address into a physical memory address at the input and/or output device; otherwise, invoking a memory management unit of the data processing system to perform translation of the virtual memory address into a physical memory address.
Preferably the method further comprises: determining at the input and/or output device whether the I/O operation request meets one or more predefined second criteria; and: if the one or more predefined second criteria are met, preventing the I/O operation requested by the virtualised interface from accessing areas of the memory which the non-privileged software domain associated with the virtualised interface is not permitted to access; otherwise, invoking a memory management unit of the data processing system to perform memory protection for the I/O operation.



DESCRIPTION OF THE DRAWINGS
The present invention will now be described by way of example with reference to the accompanying drawings, in which:
FIG. 1 is a schematic diagram which shows a typical relationship between an I/O device and host memory.
FIG. 2 is a schematic diagram which shows a data processing system configured in accordance with the present invention.



DETAILED DESCRIPTION OF THE DRAWINGS
The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art.
The general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
FIG. 2 shows hardware and software elements of a data processing system configured in accordance with the present invention. The host system 201 of the data processing system supports input/output (I/O) device 209, which could be a network interface device, graphics card or other peripheral device. Preferably I/O device 209 is coupled to host system 201 by means of a PCI Express interface (not shown).
Host system 201 supports a plurality of software domains 202 and 203. In the embodiment shown in FIG. 2, the host system is virtualised: software domain 202 is a privileged software domain (for example, a hypervisor under the VMWare architecture) and software domains 203 are non-privileged guest domains (for example, untrusted guest operating systems). The host system and guest domains are managed by trusted software domain(s) 202 (there may be more than one). Thus, trusted domain 202 allocates hardware resources to guest domains 203 and controls their access to I/O devices.
Typically, each guest domain is an instance of an operating system having a kernel 205 and supporting applications 206 at user level 204. The guest domains have a lower privilege level than trusted domain 202—for example, on an x86 system, trusted domain might operate at privilege level CPL0, the guest operating systems 205 at CPL1-2 and applications 206 at CPL3. The software domains of host system 201 have access to host memory, with trusted domain 202 allocating regions of physical memory to each of the guest domains. Each guest domain addresses its region by means of a virtual address space.
Host system 201 can access one or more I/O devices 209 by means of data bus 208. Preferably the bus is a PCI Express (PCIe) data bus and the I/O devices 209 are PCIe devices. Each I/O device 209 provides an interface by means of which it can communicate with host system 201 over bus 208. Logically, this physical interface is represented by physical interface 210, which is referred to as a physical function, or PF, in the PCIe specification. An I/O device may have more than one PF and a single device may support many different types of PF—for example, a network interface, a data storage interface, etc.
Each I/O device 209 further provides two or more virtual interfaces, one for each of the guest domains 203. Preferably these virtual interfaces are configured in accordance with the PCI-IOV specification, in which virtual interfaces are referred to as virtual functions (VFs). Each of the guest domains 203 is operable to access the particular one of the virtual interfaces of I/O device 209 with which it is associated and invoke that virtual interface to perform I/O operations by means of I/O operation requests that include the virtual memory addresses of the guest domain to which or from which the I/O data is to be written.
In order for an I/O device to access host memory, the host system must receive the physical memory address from which data is to be read, or to which data is to be written. However, a guest software domain does not have access to the physical memory address space and can only provide virtual memory addresses. Memory management unit 207 (an IOMMU as described above) is therefore required on bus 208 to translate the virtual memory addresses provided in an I/O request into physical memory addresses understood by the host memory subsystems. In a system having the PCI-IOV architecture, IOMMU 207 is referred to as a translation agent (TA), which is typically a hardware functionality provided with access to translation tables maintained by trusted domain 202. Alternatively, IOMMU 207 could be at least partially embodied in software.
In addition to translating virtual memory addresses, an IOMMU can be configured to provide protection functions for host memory. For example, the IOMMU can be configured only to allow I/O operations on behalf of a particular guest domain access to those memory areas which the trusted domain indicates that that guest domain is allowed to access. An error may be returned for any virtual addresses which translate to physical memory addresses outside the regions of memory to which a particular guest domain is permitted access.
Trusted domain 202 can communicate directly with I/O device 209 over bus 208 using I/O requests that include physical memory addresses. Trusted domain 202 typically accesses physical interface 210 of the I/O device. No virtual address translation (or a simple fixed translation) is therefore required at IOMMU 207 for I/O operations on behalf of the trusted domain between an I/O device and host memory. Furthermore, I/O requests on behalf of privileged domain 202 need not be protected because the software domain is trusted.
Each physical and virtual interface of the I/O device is preferably assigned an identifier which it uses in its I/O requests so as to identify which of the I/O interfaces is making the request. This interface identifier is referred to as the requester ID (RID) in the PCI-IOV standard, and it unique to each PF and VF. Since each interface of the I/O device is associated with a particular software domain of the host system, an identifier also identifies on behalf of which software domain an I/O request is being made. Using this identifier allows IOMMU 207 of the host system to determine (a) whether the software domain is permitted to perform the requested I/O operation (the protective function), and (b) in which virtual address space the virtual memory addresses are defined (the translation function). One or both of the protective and translation functions may be performed at the IOMMU.
In accordance with the present invention, I/O device 209 further includes translation and protection unit (TPU) 211. TPU 211 is operable to perform the translation of virtual memory addresses provided by guest domains into physical memory addresses. TPU 211 is further operable to protect host memory by only allowing I/O operations to access those memory areas which are accessible to the software domain corresponding to the RID carried in the I/O request. I/O requests directed to virtual memory addresses that are translated at TPU 211 are passed to the host system with the translated physical memory addresses and having the RID of the physical interface (PF). Such I/O requests do not therefore require translation or protection by IOMMU 207.
In order to perform virtual address translation, TPU must have access to an address translation table or database. So as to minimise lookups over bus 208, it is advantageous for the translation table to be supported at the I/O device. Preferably the translation table is maintained by a device driver of trusted domain 202, or another trusted entity. The device driver can be arranged to update the translation table of the I/O device with any modifications to the mappings between virtual and physical addresses that are maintained by trusted domain 202.
By providing means for translating and/or protecting virtual memory addresses at the I/O device, the I/O device can choose whether to perform translation and/or protection functions at the I/O device or, as is conventional, at the IOMMU. This has several advantages.
The performance of I/O operations on behalf of a physical function is generally better than that of I/O operations on behalf of virtual functions of an I/O device. This is because the memory addresses used by a PF are not subject to the translation and protection bottlenecks typically present at an IOMMU (or a simple fixed translation may be required). Translation table lookups performed by an IOMMU to determine the physical memory addresses represented by a set of virtual memory addresses can be slow—typically the translation table will be supported in host memory. Various caching schemes exist to improve the performance of address translation but these schemes are complex and expensive to implement in hardware. Their benefit is particularly limited in systems having a large number of virtualised interfaces and guest domains due to the number of different virtual address spaces which must be supported. Replacing I/O operations having a high translation overhead with I/O operations having a much lower translation overhead, provides significant I/O performance increases.
Preferably the I/O device can select between performing virtual address translation and/or protection at the I/O device and at IOMMU 207. This selection is performed on-the-fly at the I/O device for I/O operations in dependence on the characteristics of each operation. If an I/O operation meets one or more predefined characteristics, translation and/or protection is performed at TPU 211, otherwise translation and/or protection is performed at IOMMU 207.
The predefined characteristics are preferably determined by a trusted entity of privileged domain 202, such as the I/O device driver. The characteristics may be set at runtime—for example, during initialisation of the I/O device. The predefined characteristics may be determined in dependence on the type of I/O device and the particular architecture of the data processing system. The predefined characteristics may be configurable by a user of the data processing system having the necessary privilege level.
The present invention may be applied to a data processing system supporting any type of I/O device, including network interface devices, data storage devices and display adapters. If the I/O device is a network interface device, the predefined characteristics of I/O operations which causes the I/O device to invoke its TPU to perform translation and/or protection functions may be any of the following:
I/O operations associated with the receive path; those associated with the transmit path are handled by the IOMMU.
I/O operations associated with the control path; those associated with the data path are handled by the IOMMU.
I/O write operations to host memory; I/O read operations from host memory are handled by the IOMMU.
More generally, the types of I/O operation performed by a network interface device (and which represent characteristics based on which the I/O device could select whether translation and/or protection is to be performed at the I/O device or at the IOMMU) include:
Transfers of data for transmission (Tx)
Transfers of received data (Rx)
Tx descriptor fetches
Rx descriptor fetches
Completion notifications
Interrupts
The determination as to whether memory translation and protection functions should be handled at the I/O device or IOMMU may be based on analogous I/O operation types for other types of I/O device.
Preferably the predefined criteria are set in hardware at the I/O device—for example, for each virtualised interface of the I/O device and for each of a set of types of I/O operations, a stored bit in a register could indicate whether a particular operation should be handled at the I/O device or at the IOMMU.
More than one translation and/or protection unit 211 may be supported at the I/O device. In one embodiment of the present invention, each of the virtual interfaces of the I/O device supports a TPU 211, with the I/O operations requested by a particular virtualised interface (and meeting the predefined criteria) being handled by the TPU of that interface. Each TPU may have its own set of predefined criteria.
In preferred embodiments of the present invention, each virtual interface has an identifier which it uses in the I/O operation requests it generates. A virtual interface identifier may be assigned by a trusted entity of the privileged domain, such as a device driver, or it may be assigned by an entity of the I/O device, such as its physical interface. In I/O devices configured in accordance with the PCI-IOV specification, an identifier of a virtual interface is referred to as a requester ID (RID). By including an identifier with I/O operation requests, entities that receive the request (such as an IOMMU) can identify which virtual interface is making the request. Furthermore, since each virtual interface is associated with a particular one of the guest software domains, those receiving entities can also identify on behalf of which guest domain the request is being made, and therefore in which virtual address space the addresses for translation are defined.
In preferred embodiments of the present invention, when the TPU 211 of the I/O device performs virtual address translation for an I/O operation requested by a virtual interface, it replaces the identifier of that virtual interface with the identifier of the physical interface. This ensures that further translation/protection of the I/O request does not occur at IOMMU 207 when it is transmitted over bus 208 to host system 201. Thus, according to an aspect of the present invention, when performing I/O operations the I/O device is enabled to choose between using the identifier of the virtual interface (and allowing translation and/or protection to be performed at the IOMMU) and using the identifier of the physical interface (by performing translation and/or protection at a TPU).
Alternatively, the I/O device may be configured to perform only one of translation or protection at its TPU, and allow the IOMMU to perform the remaining function. For example, TPU 211 could perform virtual address translation for an I/O request and leave the identifier of the virtual interface making the request unmodified such that the IOMMU will perform its function—in this case the IOMMU is configured to perform memory protection.
It is sometimes advantageous to perform address translation and protection steps at both the I/O device and at the system IOMMU. This allows the virtualised I/O device to support software domains having multiple levels of privilege, with each privilege level being allowed to access different areas of memory. In virtualised data processing systems, a guest software domain typically supports at least two privilege levels: that of the guest operating system kernel and that of the user-level applications supported by the guest operating system, the guest OS kernel having a higher privilege level than the applications. It can be advantageous to grant user-level applications direct access to an I/O device by allowing the applications to address a virtualised interface of the I/O device. In this case it is necessary to ensure that I/O operations initiated by the virtualised interface of the device only access those areas of host memory that are allocated to the application.
Each guest domain of the data processing system is assigned a virtualised interface of the I/O device. The kernel of the guest domain is permitted to access all the memory regions allocated to the guest. In order to allow an application supported at the guest domain to access the virtualised interface of the I/O device, a sub-interface within the virtualised interface assigned to the guest domain is allocated to the application. The sub-interface holds information such as which regions of the virtual address space of the guest domain are accessible to the application for which the sub-interface is provided. This allows a TPU of I/O device (preferably a TPU supported at the virtualised interface) to perform translation and protection for I/O requests formed using virtual memory addresses provided by the application. Addresses presented by the application to the interface are thus first translated by the TPU to addresses within the virtual address space of the guest domain supporting the application. The IOMMU is configured to translate I/O requests made on behalf of the guest domain such that the virtual memory addresses translated by the TPU are subsequently translated into physical addresses by the IOMMU.
A virtualised interface 212 may support multiple sub-interfaces. Preferably a first sub-interface is allocated to the guest domain and subsequent sub-interfaces are allocated to applications supported at that guest domain.
In other embodiments of the present invention, the non-privileged software domains 203 are application domains and trusted domain 202 is the kernel of an operating system. In these embodiments, the I/O device may provide a virtualised function for each application in the manner described herein.
The present invention has been described in relation to the PCIe and PCI-IOV standards. However, the principles described herein apply generally to virtualised systems and I/O devices and are not limited to systems configured according to the PCIe architecture.
The applicant hereby discloses in isolation each individual feature described herein and any combination of two or more such features, to the extent that such features or combinations are capable of being carried out based on the present specification as a whole in the light of the common general knowledge of a person skilled in the art, irrespective of whether such features or combinations of features solve any problems disclosed herein, and without limitation to the scope of the claims. The applicant indicates that aspects of the present invention may consist of any such individual feature or combination of features. In view of the foregoing description it will be evident to a person skilled in the art that various modifications may be made within the scope of the invention.

## Claims

1. A data processing system comprising:
a memory addressable by a range of physical memory addresses;
at least one first software domain having a first privilege level and supporting a trusted I/O management entity;
a plurality of second software domains each having a privilege level which is below the first privilege level and each having a virtual memory address space;
a memory management unit configured to perform virtual address translation of a virtual memory address into a physical memory address; and
an input and/or output device supporting a plurality of virtualised interfaces, each virtualised interface being associated with a respective one of the non-privileged software domains, the input and/or output device further comprising an address translation data store maintained up-to-date by the trusted I/O management entity and at least one operation management unit having access to the address translation data store and being configured to perform virtual address translation in one or more of the virtual memory address spaces;
wherein, for I/O operations requested by a virtualised interface of the input and/or output device, the input and/or output device is configured to invoke the operation management unit to perform virtual address translation for those I/O operations meeting one or more predefined first criteria and to invoke the memory management unit to perform virtual address translation for those I/O operations which do not meet the one or more predefined first criteria.

2. The data processing system as claimed in claim 1, wherein each virtualised interface of the input and/or output device is assigned a unique identifier, and an I/O operation requested by a particular virtualised interface uses the identifier of that interface.

3. The data processing system as claimed in claim 2, wherein the input and/or output device provides a physical interface having a unique identifier.

4. The data processing system as claimed in claim 1, wherein each virtualised interface of the input and/or output device is assigned a unique identifier,
wherein the input and/or output device provides a physical interface having a unique identifier,
and wherein the input and/or output device is configured to use the identifier of its physical interface for those I/O operations which meet the one or more predefined first criteria.

5. The data processing system as claimed in claim 1, wherein the operation management unit is further configured to perform memory protection by preventing I/O operations requested by a particular virtualised interface of the Input and/or output device from accessing areas of the memory which the software domain associated with that virtualised interface is not permitted to access, and the input and/or output device is further configured to invoke the operation management unit to perform memory protection for the said input and/or output operations meeting one or more predefined second criteria.

6. The data processing system as claimed in claim 5, wherein the memory management unit is further configured to perform memory protection by preventing I/O operations requested by a particular virtualised interface of the input and/or output device from accessing areas of the memory which the software domain associated with that virtualised interface is not permitted to access, and the input and/or output device is further configured to invoke the memory management unit to perform memory protection for the said input and/or output operations which do not meet the one or more predefined second criteria.

7. The data processing system as claimed in claim 5, wherein the predefined first and second criteria are the same criteria.

8. The data processing system as claimed in claim 1, wherein the memory management unit is further configured to perform memory protection by preventing I/O operations requested by a particular virtualised interface of the input and/or output device from accessing areas of the memory which the software domain associated with that virtualised interface is not permitted to access,
and wherein the predefined first criteria are chosen such that the operation management unit is configured to perform virtual address translation for all I/O operations requested by at least one virtualised interface of the input and/or output device and the memory management unit is configured to perform memory protection for all those I/O operations.

9. The data processing system as claimed in claim 1, wherein the operation management unit is further configured to perform memory protection by preventing I/O operations requested by a particular virtualised interface of the Input and/or output device from accessing areas of the memory which the software domain associated with that virtualised interface is not permitted to access,
and wherein the predefined first and second criteria are chosen such that the operation management unit is configured to perform memory protection for all I/O operations requested by at least one virtualised interface of the input and/or output device and the memory management unit is configured to perform virtual address translation for all those I/O operations.

10. The data processing system as claimed in claim 5, wherein each virtualised interface of the input and/or output device is assigned a unique identifier, and wherein the input and/or output device further provides a physical interface having a unique identifier, and wherein the input and/or output device is configured to use the identifier of its physical interface for those I/O operations which meet the one or more predefined first criteria and the one or more predefined second criteria.

11. The data processing system as claimed in claim 10, wherein the input and/or output device is configured to use the identifier of the virtualised interface requesting the I/O operation for those I/O operations which do not meet either the one or more predefined first criteria or the one or more predefined second criteria.

12. The data processing system as claimed in claim 5, wherein each virtualised interface of the input and/or output device is assigned a unique identifier,
and wherein the one or more predefined second criteria include the identifier of the virtualised interface such that memory protection for a particular I/O operation is selectively performed at the memory management unit or the operation management unit in dependence on which virtualised interface is requesting the I/O operation.

13. The data processing system as claimed in claim 1, wherein the one or more predefined first criteria include the identifier of the virtualised interface such that virtual address translation for a particular I/O operation is selectively performed at the memory management unit or the operation management unit in dependence on which virtualised interface is requesting the I/O operation.

14. The data processing system as claimed in claim 1, wherein the one or more predefined first criteria includes the type of I/O operation.

15. The data processing system as claimed in claim 5, wherein the one or more predefined second criteria includes the type of I/O operation.

16. The data processing system as claimed claim 1, wherein the input and/or output device is a network interface device.

17. The data processing system as claimed in claim 15, wherein the input and/or output device is a network interface device,
and wherein the I/O operation types include DMA reads, DMA writes, control path operations, data path operations and an interrupts.

18. The data processing system as claimed in claim 16, wherein the one or more predefined first criteria are chosen such that virtual address translation for I/O operations belonging to a control path are performed at the memory management unit and virtual address translation for I/O operations belonging to the data path are performed at the operation management unit.

19. The data processing system as claimed in claim 18, wherein I/O operations belonging to the control path include descriptor fetches, interrupts, configuration operations and notification operations.

20. The data processing system as claimed in claim 16, wherein the one or more predefined first criteria are chosen such that virtual address translation for data transmission operations and interrupts are performed at the memory management unit and virtual address translation for data reception operations, descriptor operations and completion operations are performed at the operation management unit.

21. The data processing system as claimed in claim 1, wherein at least one of the second software domains supports at least one application having a lower privilege level than its supporting domain, each application being granted access to the virtualised interface associated with its supporting domain and to an application memory address space within the address space of the supporting domain.

22. The data processing system as claimed in claim 21, wherein, for I/O operations requested on behalf of an application, the input and/or output device is configured to:
(i) at the operation management unit, perform translation of an application memory address into a virtual memory address of the supporting domain; and
(ii) subsequently, invoke the memory management unit to perform virtual address translation of the virtual memory address into a physical memory address.

23. The data processing system as claimed in claim 21, wherein each application is granted direct access to a sub-interface of the virtualised interface of the supporting domain and each sub-interface is assigned a unique identifier.

24. The data processing system as claimed in claim 22, wherein the one or more predefined first criteria are chosen such that the memory management unit performs virtual address translation of the virtual memory address into a physical memory address.

25. The data processing system as claimed in claim 1, wherein the predefined criteria are stored at the input and/or output device.

26. The data processing system as claimed in claim 25, wherein a device driver supported at the first software domain is configured to maintain the predefined criteria stored at the input and/or output device.

27. The data processing system as claimed in claim 1, wherein the input and/or output device comprises a plurality of the said operation management units, each operation management unit being supported at a respective one of the virtualised interfaces, and, on invoking the operation management unit, the input and/or output device is configured to invoke the instance of the operation management unit supported at the virtualised interface requesting the I/O operation.

28. The data processing system as claimed in claim 1, wherein the first software domain maintains a memory address translation table.

29. The data processing system as claimed in claim 28, wherein the input and/or output device maintains a copy of the translation table.

30. The data processing system as claimed in claim 1, wherein the first software domain is a hypervisor and the second software domains are guest operating systems supported by the hypervisor.

31. The data processing system as claimed in claim 1, wherein the first software domain is an operating system kernel and the second software domains are user level entities supported by the kernel.

32. The data processing system as claimed in claim 1, wherein the input and/or output device is a PCI Express device and the virtualised interfaces of the input and/or output device are provided in accordance with the PCI-IOV specification.

33. The data processing system as claimed in claim 2, wherein each identifier is a PCI Requester ID.

34. The data processing system as claimed in claim 6, wherein the predefined first and second criteria are the same criteria.

35. The data processing system as claimed in claim 5, wherein the predefined criteria are stored at the input and/or output device.

36. The data processing system as claimed in claim 5, wherein the input and/or output device comprises a plurality of the said operation management units, each operation management unit being supported at a respective one of the virtualised interfaces, and, on invoking the operation management unit, the input and/or output device is configured to invoke the instance of the operation management unit supported at the virtualised interface requesting the I/O operation.

37. A method for handling virtual memory addresses at a data processing system comprising a memory and an input and/or output device, the data processing system supporting (a) at least one privileged software domain and (b) a plurality of non-privileged software domains each having a virtual memory address space and each being associated with a respective virtualised interface of the input and/or output device, the method comprising:
receiving at a virtualised interface of the input and/or output device at least one virtual memory address from the respective one of the non-privileged software domains;
the virtualised interface requesting an I/O operation using the at least one virtual memory address;
determining at the input and/or output device whether the I/O operation request meets one or more predefined first criteria;
and:
if the one or more first criteria are met, performing translation of the virtual memory address into a physical memory address at an operation management unit of the input and/or output device, the operation management unit having access to an address translation data store of the input and/or output device which is maintained up-to-date by a trusted I/O management entity of the privileged software domain;
otherwise, invoking a memory management unit of the data processing system to perform translation of the virtual memory address into a physical memory address.

38. The method as claimed in claim 37, further comprising:
determining at the input and/or output device whether the I/O operation request meets one or more predefined second criteria;
and:
if the one or more predefined second criteria are met, the input and/or output device preventing the I/O operation requested by the virtualised interface from accessing areas of the memory which the non-privileged software domain associated with the virtualised interface is not permitted to access;
otherwise, invoking a memory management unit of the data processing system to perform memory protection for the I/O operation.