On 26/09/2023 9:10 am, Nikolay Borisov wrote: > On 23.09.23 г. 12:41 ч., Xin Li wrote: >> diff --git a/arch/x86/include/asm/trapnr.h >> b/arch/x86/include/asm/trapnr.h >> index f5d2325aa0b7..8d1154cdf787 100644 >> --- a/arch/x86/include/asm/trapnr.h >> +++ b/arch/x86/include/asm/trapnr.h >> @@ -2,6 +2,18 @@ >> #ifndef _ASM_X86_TRAPNR_H >> #define _ASM_X86_TRAPNR_H >> +/* >> + * Event type codes used by FRED, Intel VT-x and AMD SVM >> + */ >> +#define EVENT_TYPE_EXTINT 0 // External interrupt >> +#define EVENT_TYPE_RESERVED 1 >> +#define EVENT_TYPE_NMI 2 // NMI >> +#define EVENT_TYPE_HWEXC 3 // Hardware originated traps, >> exceptions >> +#define EVENT_TYPE_SWINT 4 // INT n >> +#define EVENT_TYPE_PRIV_SWEXC 5 // INT1 >> +#define EVENT_TYPE_SWEXC 6 // INTO, INT3 > > nit: This turned into INTO (Oh) rather than INT0( zero) in v11 Yes, v11 corrected a bug in v10. The INTO instruction is "INT on Overflow". No zero involved. INT3 is thusly named because it generates vector 3. Similarly for INT1 although it had the unofficial name ICEBP long before INT1 got documented. If INTO were to have a number, it would need to be 4, but it's behaviour is conditional on the overflow flag, unlike INT3/1 which are unconditional exceptions. ~Andrew
