ff662b5c98
o Add support for backend devices (e.g. blkback) o Implement extensions to the Xen para-virtualized block API to allow for larger and more outstanding I/Os. o Import a completely rewritten block back driver with support for fronting I/O to both raw devices and files. o General cleanup and documentation of the XenBus and XenStore support code. o Robustness and performance updates for the block front driver. o Fixes to the netfront driver. Sponsored by: Spectra Logic Corporation sys/xen/xenbus/init.txt: Deleted: This file explains the Linux method for XenBus device enumeration and thus does not apply to FreeBSD's NewBus approach. sys/xen/xenbus/xenbus_probe_backend.c: Deleted: Linux version of backend XenBus service routines. It was never ported to FreeBSD. See xenbusb.c, xenbusb_if.m, xenbusb_front.c xenbusb_back.c for details of FreeBSD's XenBus support. sys/xen/xenbus/xenbusvar.h: sys/xen/xenbus/xenbus_xs.c: sys/xen/xenbus/xenbus_comms.c: sys/xen/xenbus/xenbus_comms.h: sys/xen/xenstore/xenstorevar.h: sys/xen/xenstore/xenstore.c: Split XenStore into its own tree. XenBus is a software layer built on top of XenStore. The old arrangement and the naming of some structures and functions blurred these lines making it difficult to discern what services are provided by which layer and at what times these services are available (e.g. during system startup and shutdown). sys/xen/xenbus/xenbus_client.c: sys/xen/xenbus/xenbus.c: sys/xen/xenbus/xenbus_probe.c: sys/xen/xenbus/xenbusb.c: sys/xen/xenbus/xenbusb.h: Split up XenBus code into methods available for use by client drivers (xenbus.c) and code used by the XenBus "bus code" to enumerate, attach, detach, and service bus drivers. sys/xen/reboot.c: sys/dev/xen/control/control.c: Add a XenBus front driver for handling shutdown, reboot, suspend, and resume events published in the XenStore. Move all PV suspend/reboot support from reboot.c into this driver. sys/xen/blkif.h: New file from Xen vendor with macros and structures used by a block back driver to service requests from a VM running a different ABI (e.g. amd64 back with i386 front). sys/conf/files: Adjust kernel build spec for new XenBus/XenStore layout and added Xen functionality. sys/dev/xen/balloon/balloon.c: sys/dev/xen/netfront/netfront.c: sys/dev/xen/blkfront/blkfront.c: sys/xen/xenbus/... sys/xen/xenstore/... o Rename XenStore APIs and structures from xenbus_* to xs_*. o Adjust to use of M_XENBUS and M_XENSTORE malloc types for allocation of objects returned by these APIs. o Adjust for changes in the bus interface for Xen drivers. sys/xen/xenbus/... sys/xen/xenstore/... Add Doxygen comments for these interfaces and the code that implements them. sys/dev/xen/blkback/blkback.c: o Rewrite the Block Back driver to attach properly via newbus, operate correctly in both PV and HVM mode regardless of domain (e.g. can be in a DOM other than 0), and to deal with the latest metadata available in XenStore for block devices. o Allow users to specify a file as a backend to blkback, in addition to character devices. Use the namei lookup of the backend path to automatically configure, based on file type, the appropriate backend method. The current implementation is limited to a single outstanding I/O at a time to file backed storage. sys/dev/xen/blkback/blkback.c: sys/xen/interface/io/blkif.h: sys/xen/blkif.h: sys/dev/xen/blkfront/blkfront.c: sys/dev/xen/blkfront/block.h: Extend the Xen blkif API: Negotiable request size and number of requests. This change extends the information recorded in the XenStore allowing block front/back devices to negotiate for optimal I/O parameters. This has been achieved without sacrificing backward compatibility with drivers that are unaware of these protocol enhancements. The extensions center around the connection protocol which now includes these additions: o The back-end device publishes its maximum supported values for, request I/O size, the number of page segments that can be associated with a request, the maximum number of requests that can be concurrently active, and the maximum number of pages that can be in the shared request ring. These values are published before the back-end enters the XenbusStateInitWait state. o The front-end waits for the back-end to enter either the InitWait or Initialize state. At this point, the front end limits it's own capabilities to the lesser of the values it finds published by the backend, it's own maximums, or, should any back-end data be missing in the store, the values supported by the original protocol. It then initializes it's internal data structures including allocation of the shared ring, publishes its maximum capabilities to the XenStore and transitions to the Initialized state. o The back-end waits for the front-end to enter the Initalized state. At this point, the back end limits it's own capabilities to the lesser of the values it finds published by the frontend, it's own maximums, or, should any front-end data be missing in the store, the values supported by the original protocol. It then initializes it's internal data structures, attaches to the shared ring and transitions to the Connected state. o The front-end waits for the back-end to enter the Connnected state, transitions itself to the connected state, and can commence I/O. Although an updated front-end driver must be aware of the back-end's InitWait state, the back-end has been coded such that it can tolerate a front-end that skips this step and transitions directly to the Initialized state without waiting for the back-end. sys/xen/interface/io/blkif.h: o Increase BLKIF_MAX_SEGMENTS_PER_REQUEST to 255. This is the maximum number possible without changing the blkif request header structure (nr_segs is a uint8_t). o Add two new constants: BLKIF_MAX_SEGMENTS_PER_HEADER_BLOCK, and BLKIF_MAX_SEGMENTS_PER_SEGMENT_BLOCK. These respectively indicate the number of segments that can fit in the first ring-buffer entry of a request, and for each subsequent (sg element only) ring-buffer entry associated with the "header" ring-buffer entry of the request. o Add the blkif_request_segment_t typedef for segment elements. o Add the BLKRING_GET_SG_REQUEST() macro which wraps the RING_GET_REQUEST() macro and returns a properly cast pointer to an array of blkif_request_segment_ts. o Add the BLKIF_SEGS_TO_BLOCKS() macro which calculates the number of ring entries that will be consumed by a blkif request with the given number of segments. sys/xen/blkif.h: o Update for changes in interface/io/blkif.h macros. o Update the BLKIF_MAX_RING_REQUESTS() macro to take the ring size as an argument to allow this calculation on multi-page rings. o Add a companion macro to BLKIF_MAX_RING_REQUESTS(), BLKIF_RING_PAGES(). This macro determines the number of ring pages required in order to support a ring with the supplied number of request blocks. sys/dev/xen/blkback/blkback.c: sys/dev/xen/blkfront/blkfront.c: sys/dev/xen/blkfront/block.h: o Negotiate with the other-end with the following limits: Reqeust Size: MAXPHYS Max Segments: (MAXPHYS/PAGE_SIZE) + 1 Max Requests: 256 Max Ring Pages: Sufficient to support Max Requests with Max Segments. o Dynamically allocate request pools and segemnts-per-request. o Update ring allocation/attachment code to support a multi-page shared ring. o Update routines that access the shared ring to handle multi-block requests. sys/dev/xen/blkfront/blkfront.c: o Track blkfront allocations in a blkfront driver specific malloc pool. o Strip out XenStore transaction retry logic in the connection code. Transactions only need to be used when the update to multiple XenStore nodes must be atomic. That is not the case here. o Fully disable blkif_resume() until it can be fixed properly (it didn't work before this change). o Destroy bus-dma objects during device instance tear-down. o Properly handle backend devices with powef-of-2 sector sizes larger than 512b. sys/dev/xen/blkback/blkback.c: Advertise support for and implement the BLKIF_OP_WRITE_BARRIER and BLKIF_OP_FLUSH_DISKCACHE blkif opcodes using BIO_FLUSH and the BIO_ORDERED attribute of bios. sys/dev/xen/blkfront/blkfront.c: sys/dev/xen/blkfront/block.h: Fix various bugs in blkfront. o gnttab_alloc_grant_references() returns 0 for success and non-zero for failure. The check for < 0 is a leftover Linuxism. o When we negotiate with blkback and have to reduce some of our capabilities, print out the original and reduced capability before changing the local capability. So the user now gets the correct information. o Fix blkif_restart_queue_callback() formatting. Make sure we hold the mutex in that function before calling xb_startio(). o Fix a couple of KASSERT()s. o Fix a check in the xb_remove_* macro to be a little more specific. sys/xen/gnttab.h: sys/xen/gnttab.c: Define GNTTAB_LIST_END publicly as GRANT_REF_INVALID. sys/dev/xen/netfront/netfront.c: Use GRANT_REF_INVALID instead of driver private definitions of the same constant. sys/xen/gnttab.h: sys/xen/gnttab.c: Add the gnttab_end_foreign_access_references() API. This API allows a client to batch the release of an array of grant references, instead of coding a private for loop. The implementation takes advantage of this batching to reduce lock overhead to one acquisition and release per-batch instead of per-freed grant reference. While here, reduce the duration the gnttab_list_lock is held during gnttab_free_grant_references() operations. The search to find the tail of the incoming free list does not rely on global state and so can be performed without holding the lock. sys/dev/xen/xenpci/evtchn.c: sys/dev/xen/evtchn/evtchn.c: sys/xen/xen_intr.h: o Implement the bind_interdomain_evtchn_to_irqhandler API for HVM mode. This allows an HVM domain to serve back end devices to other domains. This API is already implemented for PV mode. o Synchronize the API between HVM and PV. sys/dev/xen/xenpci/xenpci.c: o Scan the full region of CPUID space in which the Xen VMM interface may be implemented. On systems using SuSE as a Dom0 where the Viridian API is also exported, the VMM interface is above the region we used to search. o Pass through bus_alloc_resource() calls so that XenBus drivers attaching on an HVM system can allocate unused physical address space from the nexus. The block back driver makes use of this facility. sys/i386/xen/xen_machdep.c: Use the correct type for accessing the statically mapped xenstore metadata. sys/xen/interface/hvm/params.h: sys/xen/xenstore/xenstore.c: Move hvm_get_parameter() to the correct global header file instead of as a private method to the XenStore. sys/xen/interface/io/protocols.h: Sync with vendor. sys/xeninterface/io/ring.h: Add macro for calculating the number of ring pages needed for an N deep ring. To avoid duplication within the macros, create and use the new __RING_HEADER_SIZE() macro. This macro calculates the size of the ring book keeping struct (producer/consumer indexes, etc.) that resides at the head of the ring. Add the __RING_PAGES() macro which calculates the number of shared ring pages required to support a ring with the given number of requests. These APIs are used to support the multi-page ring version of the Xen block API. sys/xeninterface/io/xenbus.h: Add Comments. sys/xen/xenbus/... o Refactor the FreeBSD XenBus support code to allow for both front and backend device attachments. o Make use of new config_intr_hook capabilities to allow front and back devices to be probed/attached in parallel. o Fix bugs in probe/attach state machine that could cause the system to hang when confronted with a failure either in the local domain or in a remote domain to which one of our driver instances is attaching. o Publish all required state to the XenStore on device detach and failure. The majority of the missing functionality was for serving as a back end since the typical "hot-plug" scripts in Dom0 don't handle the case of cleaning up for a "service domain" that is not itself. o Add dynamic sysctl nodes exposing the generic ivars of XenBus devices. o Add doxygen style comments to the majority of the code. o Cleanup types, formatting, etc. sys/xen/xenbus/xenbusb.c: Common code used by both front and back XenBus busses. sys/xen/xenbus/xenbusb_if.m: Method definitions for a XenBus bus. sys/xen/xenbus/xenbusb_front.c: sys/xen/xenbus/xenbusb_back.c: XenBus bus specialization for front and back devices. MFC after: 1 month
434 lines
16 KiB
C
434 lines
16 KiB
C
/******************************************************************************
|
|
* grant_table.h
|
|
*
|
|
* Interface for granting foreign access to page frames, and receiving
|
|
* page-ownership transfers.
|
|
*
|
|
* Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
* of this software and associated documentation files (the "Software"), to
|
|
* deal in the Software without restriction, including without limitation the
|
|
* rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
|
|
* sell copies of the Software, and to permit persons to whom the Software is
|
|
* furnished to do so, subject to the following conditions:
|
|
*
|
|
* The above copyright notice and this permission notice shall be included in
|
|
* all copies or substantial portions of the Software.
|
|
*
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
|
|
* FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
|
|
* DEALINGS IN THE SOFTWARE.
|
|
*
|
|
* Copyright (c) 2004, K A Fraser
|
|
*/
|
|
|
|
#ifndef __XEN_PUBLIC_GRANT_TABLE_H__
|
|
#define __XEN_PUBLIC_GRANT_TABLE_H__
|
|
|
|
|
|
/***********************************
|
|
* GRANT TABLE REPRESENTATION
|
|
*/
|
|
|
|
/* Some rough guidelines on accessing and updating grant-table entries
|
|
* in a concurrency-safe manner. For more information, Linux contains a
|
|
* reference implementation for guest OSes (arch/xen/kernel/grant_table.c).
|
|
*
|
|
* NB. WMB is a no-op on current-generation x86 processors. However, a
|
|
* compiler barrier will still be required.
|
|
*
|
|
* Introducing a valid entry into the grant table:
|
|
* 1. Write ent->domid.
|
|
* 2. Write ent->frame:
|
|
* GTF_permit_access: Frame to which access is permitted.
|
|
* GTF_accept_transfer: Pseudo-phys frame slot being filled by new
|
|
* frame, or zero if none.
|
|
* 3. Write memory barrier (WMB).
|
|
* 4. Write ent->flags, inc. valid type.
|
|
*
|
|
* Invalidating an unused GTF_permit_access entry:
|
|
* 1. flags = ent->flags.
|
|
* 2. Observe that !(flags & (GTF_reading|GTF_writing)).
|
|
* 3. Check result of SMP-safe CMPXCHG(&ent->flags, flags, 0).
|
|
* NB. No need for WMB as reuse of entry is control-dependent on success of
|
|
* step 3, and all architectures guarantee ordering of ctrl-dep writes.
|
|
*
|
|
* Invalidating an in-use GTF_permit_access entry:
|
|
* This cannot be done directly. Request assistance from the domain controller
|
|
* which can set a timeout on the use of a grant entry and take necessary
|
|
* action. (NB. This is not yet implemented!).
|
|
*
|
|
* Invalidating an unused GTF_accept_transfer entry:
|
|
* 1. flags = ent->flags.
|
|
* 2. Observe that !(flags & GTF_transfer_committed). [*]
|
|
* 3. Check result of SMP-safe CMPXCHG(&ent->flags, flags, 0).
|
|
* NB. No need for WMB as reuse of entry is control-dependent on success of
|
|
* step 3, and all architectures guarantee ordering of ctrl-dep writes.
|
|
* [*] If GTF_transfer_committed is set then the grant entry is 'committed'.
|
|
* The guest must /not/ modify the grant entry until the address of the
|
|
* transferred frame is written. It is safe for the guest to spin waiting
|
|
* for this to occur (detect by observing GTF_transfer_completed in
|
|
* ent->flags).
|
|
*
|
|
* Invalidating a committed GTF_accept_transfer entry:
|
|
* 1. Wait for (ent->flags & GTF_transfer_completed).
|
|
*
|
|
* Changing a GTF_permit_access from writable to read-only:
|
|
* Use SMP-safe CMPXCHG to set GTF_readonly, while checking !GTF_writing.
|
|
*
|
|
* Changing a GTF_permit_access from read-only to writable:
|
|
* Use SMP-safe bit-setting instruction.
|
|
*/
|
|
|
|
/*
|
|
* A grant table comprises a packed array of grant entries in one or more
|
|
* page frames shared between Xen and a guest.
|
|
* [XEN]: This field is written by Xen and read by the sharing guest.
|
|
* [GST]: This field is written by the guest and read by Xen.
|
|
*/
|
|
struct grant_entry {
|
|
/* GTF_xxx: various type and flag information. [XEN,GST] */
|
|
uint16_t flags;
|
|
/* The domain being granted foreign privileges. [GST] */
|
|
domid_t domid;
|
|
/*
|
|
* GTF_permit_access: Frame that @domid is allowed to map and access. [GST]
|
|
* GTF_accept_transfer: Frame whose ownership transferred by @domid. [XEN]
|
|
*/
|
|
uint32_t frame;
|
|
};
|
|
typedef struct grant_entry grant_entry_t;
|
|
|
|
/*
|
|
* Type of grant entry.
|
|
* GTF_invalid: This grant entry grants no privileges.
|
|
* GTF_permit_access: Allow @domid to map/access @frame.
|
|
* GTF_accept_transfer: Allow @domid to transfer ownership of one page frame
|
|
* to this guest. Xen writes the page number to @frame.
|
|
*/
|
|
#define GTF_invalid (0U<<0)
|
|
#define GTF_permit_access (1U<<0)
|
|
#define GTF_accept_transfer (2U<<0)
|
|
#define GTF_type_mask (3U<<0)
|
|
|
|
/*
|
|
* Subflags for GTF_permit_access.
|
|
* GTF_readonly: Restrict @domid to read-only mappings and accesses. [GST]
|
|
* GTF_reading: Grant entry is currently mapped for reading by @domid. [XEN]
|
|
* GTF_writing: Grant entry is currently mapped for writing by @domid. [XEN]
|
|
* GTF_PAT, GTF_PWT, GTF_PCD: (x86) cache attribute flags for the grant [GST]
|
|
*/
|
|
#define _GTF_readonly (2)
|
|
#define GTF_readonly (1U<<_GTF_readonly)
|
|
#define _GTF_reading (3)
|
|
#define GTF_reading (1U<<_GTF_reading)
|
|
#define _GTF_writing (4)
|
|
#define GTF_writing (1U<<_GTF_writing)
|
|
#define _GTF_PWT (5)
|
|
#define GTF_PWT (1U<<_GTF_PWT)
|
|
#define _GTF_PCD (6)
|
|
#define GTF_PCD (1U<<_GTF_PCD)
|
|
#define _GTF_PAT (7)
|
|
#define GTF_PAT (1U<<_GTF_PAT)
|
|
|
|
/*
|
|
* Subflags for GTF_accept_transfer:
|
|
* GTF_transfer_committed: Xen sets this flag to indicate that it is committed
|
|
* to transferring ownership of a page frame. When a guest sees this flag
|
|
* it must /not/ modify the grant entry until GTF_transfer_completed is
|
|
* set by Xen.
|
|
* GTF_transfer_completed: It is safe for the guest to spin-wait on this flag
|
|
* after reading GTF_transfer_committed. Xen will always write the frame
|
|
* address, followed by ORing this flag, in a timely manner.
|
|
*/
|
|
#define _GTF_transfer_committed (2)
|
|
#define GTF_transfer_committed (1U<<_GTF_transfer_committed)
|
|
#define _GTF_transfer_completed (3)
|
|
#define GTF_transfer_completed (1U<<_GTF_transfer_completed)
|
|
|
|
|
|
/***********************************
|
|
* GRANT TABLE QUERIES AND USES
|
|
*/
|
|
|
|
/*
|
|
* Reference to a grant entry in a specified domain's grant table.
|
|
*/
|
|
typedef uint32_t grant_ref_t;
|
|
|
|
#define GRANT_REF_INVALID 0xffffffff
|
|
|
|
/*
|
|
* Handle to track a mapping created via a grant reference.
|
|
*/
|
|
typedef uint32_t grant_handle_t;
|
|
|
|
/*
|
|
* GNTTABOP_map_grant_ref: Map the grant entry (<dom>,<ref>) for access
|
|
* by devices and/or host CPUs. If successful, <handle> is a tracking number
|
|
* that must be presented later to destroy the mapping(s). On error, <handle>
|
|
* is a negative status code.
|
|
* NOTES:
|
|
* 1. If GNTMAP_device_map is specified then <dev_bus_addr> is the address
|
|
* via which I/O devices may access the granted frame.
|
|
* 2. If GNTMAP_host_map is specified then a mapping will be added at
|
|
* either a host virtual address in the current address space, or at
|
|
* a PTE at the specified machine address. The type of mapping to
|
|
* perform is selected through the GNTMAP_contains_pte flag, and the
|
|
* address is specified in <host_addr>.
|
|
* 3. Mappings should only be destroyed via GNTTABOP_unmap_grant_ref. If a
|
|
* host mapping is destroyed by other means then it is *NOT* guaranteed
|
|
* to be accounted to the correct grant reference!
|
|
*/
|
|
#define GNTTABOP_map_grant_ref 0
|
|
struct gnttab_map_grant_ref {
|
|
/* IN parameters. */
|
|
uint64_t host_addr;
|
|
uint32_t flags; /* GNTMAP_* */
|
|
grant_ref_t ref;
|
|
domid_t dom;
|
|
/* OUT parameters. */
|
|
int16_t status; /* GNTST_* */
|
|
grant_handle_t handle;
|
|
uint64_t dev_bus_addr;
|
|
};
|
|
typedef struct gnttab_map_grant_ref gnttab_map_grant_ref_t;
|
|
DEFINE_XEN_GUEST_HANDLE(gnttab_map_grant_ref_t);
|
|
|
|
/*
|
|
* GNTTABOP_unmap_grant_ref: Destroy one or more grant-reference mappings
|
|
* tracked by <handle>. If <host_addr> or <dev_bus_addr> is zero, that
|
|
* field is ignored. If non-zero, they must refer to a device/host mapping
|
|
* that is tracked by <handle>
|
|
* NOTES:
|
|
* 1. The call may fail in an undefined manner if either mapping is not
|
|
* tracked by <handle>.
|
|
* 3. After executing a batch of unmaps, it is guaranteed that no stale
|
|
* mappings will remain in the device or host TLBs.
|
|
*/
|
|
#define GNTTABOP_unmap_grant_ref 1
|
|
struct gnttab_unmap_grant_ref {
|
|
/* IN parameters. */
|
|
uint64_t host_addr;
|
|
uint64_t dev_bus_addr;
|
|
grant_handle_t handle;
|
|
/* OUT parameters. */
|
|
int16_t status; /* GNTST_* */
|
|
};
|
|
typedef struct gnttab_unmap_grant_ref gnttab_unmap_grant_ref_t;
|
|
DEFINE_XEN_GUEST_HANDLE(gnttab_unmap_grant_ref_t);
|
|
|
|
/*
|
|
* GNTTABOP_setup_table: Set up a grant table for <dom> comprising at least
|
|
* <nr_frames> pages. The frame addresses are written to the <frame_list>.
|
|
* Only <nr_frames> addresses are written, even if the table is larger.
|
|
* NOTES:
|
|
* 1. <dom> may be specified as DOMID_SELF.
|
|
* 2. Only a sufficiently-privileged domain may specify <dom> != DOMID_SELF.
|
|
* 3. Xen may not support more than a single grant-table page per domain.
|
|
*/
|
|
#define GNTTABOP_setup_table 2
|
|
struct gnttab_setup_table {
|
|
/* IN parameters. */
|
|
domid_t dom;
|
|
uint32_t nr_frames;
|
|
/* OUT parameters. */
|
|
int16_t status; /* GNTST_* */
|
|
XEN_GUEST_HANDLE(ulong) frame_list;
|
|
};
|
|
typedef struct gnttab_setup_table gnttab_setup_table_t;
|
|
DEFINE_XEN_GUEST_HANDLE(gnttab_setup_table_t);
|
|
|
|
/*
|
|
* GNTTABOP_dump_table: Dump the contents of the grant table to the
|
|
* xen console. Debugging use only.
|
|
*/
|
|
#define GNTTABOP_dump_table 3
|
|
struct gnttab_dump_table {
|
|
/* IN parameters. */
|
|
domid_t dom;
|
|
/* OUT parameters. */
|
|
int16_t status; /* GNTST_* */
|
|
};
|
|
typedef struct gnttab_dump_table gnttab_dump_table_t;
|
|
DEFINE_XEN_GUEST_HANDLE(gnttab_dump_table_t);
|
|
|
|
/*
|
|
* GNTTABOP_transfer_grant_ref: Transfer <frame> to a foreign domain. The
|
|
* foreign domain has previously registered its interest in the transfer via
|
|
* <domid, ref>.
|
|
*
|
|
* Note that, even if the transfer fails, the specified page no longer belongs
|
|
* to the calling domain *unless* the error is GNTST_bad_page.
|
|
*/
|
|
#define GNTTABOP_transfer 4
|
|
struct gnttab_transfer {
|
|
/* IN parameters. */
|
|
xen_pfn_t mfn;
|
|
domid_t domid;
|
|
grant_ref_t ref;
|
|
/* OUT parameters. */
|
|
int16_t status;
|
|
};
|
|
typedef struct gnttab_transfer gnttab_transfer_t;
|
|
DEFINE_XEN_GUEST_HANDLE(gnttab_transfer_t);
|
|
|
|
|
|
/*
|
|
* GNTTABOP_copy: Hypervisor based copy
|
|
* source and destinations can be eithers MFNs or, for foreign domains,
|
|
* grant references. the foreign domain has to grant read/write access
|
|
* in its grant table.
|
|
*
|
|
* The flags specify what type source and destinations are (either MFN
|
|
* or grant reference).
|
|
*
|
|
* Note that this can also be used to copy data between two domains
|
|
* via a third party if the source and destination domains had previously
|
|
* grant appropriate access to their pages to the third party.
|
|
*
|
|
* source_offset specifies an offset in the source frame, dest_offset
|
|
* the offset in the target frame and len specifies the number of
|
|
* bytes to be copied.
|
|
*/
|
|
|
|
#define _GNTCOPY_source_gref (0)
|
|
#define GNTCOPY_source_gref (1<<_GNTCOPY_source_gref)
|
|
#define _GNTCOPY_dest_gref (1)
|
|
#define GNTCOPY_dest_gref (1<<_GNTCOPY_dest_gref)
|
|
|
|
#define GNTTABOP_copy 5
|
|
typedef struct gnttab_copy {
|
|
/* IN parameters. */
|
|
struct {
|
|
union {
|
|
grant_ref_t ref;
|
|
xen_pfn_t gmfn;
|
|
} u;
|
|
domid_t domid;
|
|
uint16_t offset;
|
|
} source, dest;
|
|
uint16_t len;
|
|
uint16_t flags; /* GNTCOPY_* */
|
|
/* OUT parameters. */
|
|
int16_t status;
|
|
} gnttab_copy_t;
|
|
DEFINE_XEN_GUEST_HANDLE(gnttab_copy_t);
|
|
|
|
/*
|
|
* GNTTABOP_query_size: Query the current and maximum sizes of the shared
|
|
* grant table.
|
|
* NOTES:
|
|
* 1. <dom> may be specified as DOMID_SELF.
|
|
* 2. Only a sufficiently-privileged domain may specify <dom> != DOMID_SELF.
|
|
*/
|
|
#define GNTTABOP_query_size 6
|
|
struct gnttab_query_size {
|
|
/* IN parameters. */
|
|
domid_t dom;
|
|
/* OUT parameters. */
|
|
uint32_t nr_frames;
|
|
uint32_t max_nr_frames;
|
|
int16_t status; /* GNTST_* */
|
|
};
|
|
typedef struct gnttab_query_size gnttab_query_size_t;
|
|
DEFINE_XEN_GUEST_HANDLE(gnttab_query_size_t);
|
|
|
|
/*
|
|
* GNTTABOP_unmap_and_replace: Destroy one or more grant-reference mappings
|
|
* tracked by <handle> but atomically replace the page table entry with one
|
|
* pointing to the machine address under <new_addr>. <new_addr> will be
|
|
* redirected to the null entry.
|
|
* NOTES:
|
|
* 1. The call may fail in an undefined manner if either mapping is not
|
|
* tracked by <handle>.
|
|
* 2. After executing a batch of unmaps, it is guaranteed that no stale
|
|
* mappings will remain in the device or host TLBs.
|
|
*/
|
|
#define GNTTABOP_unmap_and_replace 7
|
|
struct gnttab_unmap_and_replace {
|
|
/* IN parameters. */
|
|
uint64_t host_addr;
|
|
uint64_t new_addr;
|
|
grant_handle_t handle;
|
|
/* OUT parameters. */
|
|
int16_t status; /* GNTST_* */
|
|
};
|
|
typedef struct gnttab_unmap_and_replace gnttab_unmap_and_replace_t;
|
|
DEFINE_XEN_GUEST_HANDLE(gnttab_unmap_and_replace_t);
|
|
|
|
|
|
/*
|
|
* Bitfield values for update_pin_status.flags.
|
|
*/
|
|
/* Map the grant entry for access by I/O devices. */
|
|
#define _GNTMAP_device_map (0)
|
|
#define GNTMAP_device_map (1<<_GNTMAP_device_map)
|
|
/* Map the grant entry for access by host CPUs. */
|
|
#define _GNTMAP_host_map (1)
|
|
#define GNTMAP_host_map (1<<_GNTMAP_host_map)
|
|
/* Accesses to the granted frame will be restricted to read-only access. */
|
|
#define _GNTMAP_readonly (2)
|
|
#define GNTMAP_readonly (1<<_GNTMAP_readonly)
|
|
/*
|
|
* GNTMAP_host_map subflag:
|
|
* 0 => The host mapping is usable only by the guest OS.
|
|
* 1 => The host mapping is usable by guest OS + current application.
|
|
*/
|
|
#define _GNTMAP_application_map (3)
|
|
#define GNTMAP_application_map (1<<_GNTMAP_application_map)
|
|
|
|
/*
|
|
* 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.
|
|
*/
|
|
#define _GNTMAP_contains_pte (4)
|
|
#define GNTMAP_contains_pte (1<<_GNTMAP_contains_pte)
|
|
|
|
/*
|
|
* Values for error status returns. All errors are -ve.
|
|
*/
|
|
#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_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. */
|
|
#define GNTST_bad_dev_addr (-6) /* Inappropriate device address to unmap.*/
|
|
#define GNTST_no_device_space (-7) /* Out of space in I/O MMU. */
|
|
#define GNTST_permission_denied (-8) /* Not enough privilege for operation. */
|
|
#define GNTST_bad_page (-9) /* Specified page was invalid for op. */
|
|
#define GNTST_bad_copy_arg (-10) /* copy arguments cross page boundary. */
|
|
#define GNTST_address_too_big (-11) /* transfer page address too large. */
|
|
|
|
#define GNTTABOP_error_msgs { \
|
|
"okay", \
|
|
"undefined error", \
|
|
"unrecognised domain id", \
|
|
"invalid grant reference", \
|
|
"invalid mapping handle", \
|
|
"invalid virtual address", \
|
|
"invalid device address", \
|
|
"no spare translation slot in the I/O MMU", \
|
|
"permission denied", \
|
|
"bad page", \
|
|
"copy arguments cross page boundary", \
|
|
"page address size too large" \
|
|
}
|
|
|
|
#endif /* __XEN_PUBLIC_GRANT_TABLE_H__ */
|
|
|
|
/*
|
|
* Local variables:
|
|
* mode: C
|
|
* c-set-style: "BSD"
|
|
* c-basic-offset: 4
|
|
* tab-width: 4
|
|
* indent-tabs-mode: nil
|
|
* End:
|
|
*/
|