On 31.10.2022 19:37, Andrew Cooper wrote: > On 31/10/2022 15:55, Jan Beulich wrote: >> Of course I'm yet to figure out how IRR bit 0x13 ends up being set in >> the first place. > > 0x13 is a legal vector for incoming interrupts (for reasons of Windows > using 0x1f for self-IPI.)
I was wrong here, mislead by the way Linux logs the IRR and ISR: About any other separator than comma (and perhaps a blank) would likely have made me check the order of elements. With commas it was pretty natural to assume the logged items are in array element order. Turns out they are not, so the bit in question corresponds to vector 0xf3. Which then pretty cleanly connects to a new feature in 6.0 - see https://lists.xen.org/archives/html/xen-devel/2022-11/msg00199.html. Jan
