HV_X64_IO_PORT_INTERCEPT_MESSAGE structure
The HV_X64_IO_PORT_INTERCEPT_MESSAGE structure describes an I/O access intercept message.
Syntax
typedef struct _HV_X64_IO_PORT_INTERCEPT_MESSAGE { HV_X64_INTERCEPT_MESSAGE_HEADER Header; UINT16 PortNumber; HV_X64_IO_PORT_ACCESS_INFO AccessInfo; UINT8 InstructionByteCount; UINT32 Reserved; UINT64 Rax; UINT8 InstructionBytes[16]; HV_X64_SEGMENT_REGISTER DsSegment; HV_X64_SEGMENT_REGISTER EsSegment; UINT64 Rcx; UINT64 Rsi; UINT64 Rdi; } HV_X64_IO_PORT_INTERCEPT_MESSAGE, *PHV_X64_IO_PORT_INTERCEPT_MESSAGE;
Members
- Header
-
An HV_X64_INTERCEPT_MESSAGE_HEADER structure that describes the header for the I/O access intercept message.
- PortNumber
-
The number of the I/O port that is being accessed.
- AccessInfo
-
An HV_X64_IO_PORT_ACCESS_INFO union that indicates the size of the access, whether the intercepted instruction was a string operation, and whether a "rep" prefix was specified.
- InstructionByteCount
-
An 8-bit value that specifies the number of instruction bytes that are provided in the InstructionBytes member.
- Reserved
-
Reserved. Do not use.
- Rax
-
The value for the virtual processor's 64-bit RAX general-purpose register.
- InstructionBytes
-
An array of bytes that make up the instruction stream for the I/O access intercept message. The number of valid bytes is specified by the InstructionByteCount member.
- DsSegment
-
An HV_X64_SEGMENT_REGISTER structure that describes the selector, base, limit, and flags for the current data segment (DS).
- EsSegment
-
An HV_X64_SEGMENT_REGISTER structure that describes the selector, base, limit, and flags for the current extended segment (ES).
- Rcx
-
The value for the virtual processor's 64-bit RCX general-purpose register.
- Rsi
-
The value for the virtual processor's 64-bit RSI general-purpose register.
- Rdi
-
The value for the virtual processor's 64-bit RDI general-purpose register.
Remarks
For more information about how I/O access intercept messages are encoded, see I/O Port Intercept Message.
Requirements
Header |
|
---|
See also
Send comments about this topic to Microsoft
Build date: 11/16/2013