[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: x86/HVM: Linux'es apic_pending_intr_clear() warns about stale IRR
- To: Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>
- From: Jan Beulich <jbeulich@xxxxxxxx>
- Date: Thu, 3 Nov 2022 14:48:30 +0100
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Oe54xzSNXVksQiYOAH50cmCOIBeSDqgVz6CHue0NchU=; b=Es8hYcVkSxNkwq1nEhf5E2VoMcKmVfzRuLxxGoCxCj7JuVX4NJ+Y/qoPSioS4/1A7h1X77gbQ5rOEkSySBXUWqSgrwielNc4oMw8JwLTK9T/SbNT8mUh6tfZeuj9wv0wv3HbkegGqsbBPMWPNuIjvfmji6YTUZECqq7T+jO2N2ms2fxc7unIRkC4A04/PP2NO1g8BslimT+q1An3ySkM+mzap84vTaf82vR4ft1Iuru5xMEYXNszaIlViDFjOLFrxtiKHiti9+1UM5eFWtH1YHn6qf+oNM5LOYq74wJRWGiMffq2BpbrLXj/vkeOj4UP2PF7ERoHndh/dLAHfqNMJw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JmLPJJ/eSqTPv49t9fn5VPe5PPKdQmKeHK9xFpG6AxswgTIGG343V27oYcvrbTIDzFKDN65kKTtstkDrkXqu0lko3nTqeQuUU+N4EMXSvEoyBuCL6Vlua7eEzjQx8JKqTwBrFLCbEAfWfWIbdl9EB2Aca6OF+GJ97eweEI2F1IFbvYXyoWjTMzNIy6q3Z9foYmja2hWscla4Ab25rm/sH2PQWtER7f0g+g8tYrvs1/aJfC6rHWA2UEKuV3DXLGJpuEMTw8dNVgXga8kHkc8GIxoRB45bRZ7TPItR0O9nmDDl0BbLdQCpsEIT44VwykYFCQ+BbX7Qtg5df1tcThJbBQ==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
- Cc: Roger Pau Monne <roger.pau@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
- Delivery-date: Thu, 03 Nov 2022 13:48:43 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
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
|
