HvClearVirtualInterrupt function
The HvClearVirtualInterrupt function determines whether a previously-requested virtual interrupt of type HvX64InterruptTypeExtInt has been acknowledged.
Syntax
HV_STATUS HvClearVirtualInterrupt( _In_ HV_PARTITION_ID DestinationPartition );
Parameters
- DestinationPartition [in]
-
An HV_PARTITION_ID value that identifies the partition on which HvClearVirtualInterrupt clears the acknowledgment of a virtual interrupt. HV_PARTITION_ID is defined as an unsigned 64-bit (UINT64) value.
Return value
HvClearVirtualInterrupt returns one of the following values. In addition to these values, HvClearVirtualInterrupt can also return one of the values that are specified in Common Hypercall Status Codes.
Return code | Description |
---|---|
|
HvClearVirtualInterrupt successfully cleared the acknowledgment of a virtual interrupt. |
|
The caller is not the parent of the specified partition. |
|
The specified partition identifier is invalid. |
|
An external interrupt has not been asserted and acknowledged since the last call to HvClearVirtualInterrupt. |
|
The specified partition is not in the active state. |
Remarks
An external interrupt is considered "acknowledged" when it has been delivered to the boot processor.
HvClearVirtualInterrupt clears the acknowledged state of an external interrupt and allows subsequent external interrupts to be asserted. If no external interrupt has been acknowledged, HvClearVirtualInterrupt fails with a status code of HV_STATUS_NOT_ACKNOWLEDGED.
HvClearVirtualInterrupt has the following restrictions:
-
The partition that DestinationPartition specifies must be in the active state.
-
The caller must be the parent of the partition that is specified by DestinationPartition.
Native Interface
HvClearVirtualInterrupt [fast] | |
---|---|
Call Code = 0x0056 | |
Input Parameters | |
0 |
DestinationPartition (8 bytes) |
Requirements
Version | HvClearVirtualInterrupt is available in version 1.0 and later versions of the hypervisor. |
---|---|
Header |
|
IRQL | Any level |
Send comments about this topic to Microsoft
Build date: 11/16/2013