Lines Matching refs:requests
12 /* Check if any requests are pending for VCPU @vcpu. */
38 as possible after making the request. This means most requests
67 ensure VCPU requests are seen by VCPUs (see "Ensuring Requests Are Seen"),
88 certain VCPU requests, namely KVM_REQ_TLB_FLUSH, to wait until the VCPU
94 VCPU requests are simply bit indices of the ``vcpu->requests`` bitmap.
98 clear_bit(KVM_REQ_UNHALT & KVM_REQUEST_MASK, &vcpu->requests);
102 independent requests, all additional bits are available for architecture
103 dependent requests.
142 VCPU requests should be masked by KVM_REQUEST_MASK before using them with
152 This flag is applied to requests that only need immediate attention
154 to be awaken for these requests. Sleeping VCPUs will handle the
155 requests when they are awaken later for some other reason.
159 When requests with this flag are made with kvm_make_all_cpus_request(),
165 Acknowledgements" for more information about requests with
188 When making requests to VCPUs, we want to avoid the receiving VCPU
212 this solution pairs ``vcpu->mode`` with ``vcpu->requests``. Substituting
236 As only one IPI is needed to get a VCPU to check for any/all requests,
244 Some requests, those with the KVM_REQUEST_WAIT flag set, require IPIs to
271 role of ``vcpu->requests``. When sending a posted interrupt, PIR.ON is
282 VCPU threads may need to consider requests before and/or after calling
284 do or not, and, if they do, which requests need consideration, is
287 architectures a function where requests may be checked if necessary.