Lines Matching refs:I
3 I/O request handling
6 An I/O request of a User VM, which is constructed by the hypervisor, is
7 distributed by the ACRN Hypervisor Service Module to an I/O client
8 corresponding to the address range of the I/O request. Details of I/O request
11 1. I/O request
14 For each User VM, there is a shared 4-KByte memory region used for I/O requests
15 communication between the hypervisor and Service VM. An I/O request is a
17 an I/O handler of the hypervisor when a trapped I/O access happens in a User
20 used as an array of 16 I/O request slots with each I/O request slot being 256
23 2. I/O clients
26 An I/O client is responsible for handling User VM I/O requests whose accessed
27 GPA falls in a certain range. Multiple I/O clients can be associated with each
29 default client, that handles all I/O requests that do not fit into the range of
33 Below illustration shows the relationship between I/O requests shared buffer,
34 I/O requests and I/O clients.
45 || | | | +-----------------+ | I/O client | | | |
54 || | | | I/O clients | | | |
63 | | I/O handler | ACRN Hypervisor |
67 3. I/O request state transition
70 The state transitions of an ACRN I/O request are as follows.
76 - FREE: this I/O request slot is empty
77 - PENDING: a valid I/O request is pending in this slot
78 - PROCESSING: the I/O request is being processed
79 - COMPLETE: the I/O request has been processed
81 An I/O request in COMPLETE or FREE state is owned by the hypervisor. HSM and
84 4. Processing flow of I/O requests
87 a. The I/O handler of the hypervisor will fill an I/O request with PENDING
88 state when a trapped I/O access happens in a User VM.
91 c. The upcall handler schedules a worker to dispatch I/O requests.
92 d. The worker looks for the PENDING I/O requests, assigns them to different
93 registered clients based on the address of the I/O accesses, updates
95 e. The notified client handles the assigned I/O requests.
96 f. The HSM updates I/O requests states to COMPLETE and notifies the hypervisor