linux-kernel - Re: [PATCH v2 05/13] x86/irq: Reserve a per CPU IDT vector for posted MSIs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Fri, 12 Apr 2024 07:27:30 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Kevin Tian <kevin.tian@...el.com>
Cc: Jacob Pan <jacob.jun.pan@...ux.intel.com>, LKML <linux-kernel@...r.kernel.org>, 
	X86 Kernel <x86@...nel.org>, Peter Zijlstra <peterz@...radead.org>, 
	"iommu@...ts.linux.dev" <iommu@...ts.linux.dev>, Thomas Gleixner <tglx@...utronix.de>, 
	Lu Baolu <baolu.lu@...ux.intel.com>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>, 
	Dave Hansen <dave.hansen@...el.com>, Joerg Roedel <joro@...tes.org>, Peter Anvin <hpa@...or.com>, 
	Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...hat.com>, Paul E Luse <paul.e.luse@...el.com>, 
	Dan Williams <dan.j.williams@...el.com>, Jens Axboe <axboe@...nel.dk>, 
	Ashok Raj <ashok.raj@...el.com>, "maz@...nel.org" <maz@...nel.org>, 
	Robin Murphy <robin.murphy@....com>, "jim.harris@...sung.com" <jim.harris@...sung.com>, 
	"a.manzanares@...sung.com" <a.manzanares@...sung.com>, Bjorn Helgaas <helgaas@...nel.org>, 
	Guang Zeng <guang.zeng@...el.com>, 
	"robert.hoo.linux@...il.com" <robert.hoo.linux@...il.com>
Subject: Re: [PATCH v2 05/13] x86/irq: Reserve a per CPU IDT vector for posted MSIs

On Fri, Apr 12, 2024, Kevin Tian wrote:
> > From: Jacob Pan <jacob.jun.pan@...ux.intel.com>
> > Sent: Saturday, April 6, 2024 6:31 AM
> > 
> > +/*
> > + * Posted interrupt notification vector for all device MSIs delivered to
> > + * the host kernel.
> > + */
> > +#define POSTED_MSI_NOTIFICATION_VECTOR	0xeb
> >  #define NR_VECTORS			 256
> > 
> 
> Every interrupt is kind of a notification.

FWIW, I find value in having "notification" in the name to differentiate between
the IRQ that is notifying the CPU that there's a posted IRQ to be processed, and
the posted IRQ itself.