[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SA1PR11MB673441665AA79735E5EA60C6A8809@SA1PR11MB6734.namprd11.prod.outlook.com>
Date: Mon, 20 Mar 2023 23:47:23 +0000
From: "Li, Xin3" <xin3.li@...el.com>
To: Peter Zijlstra <peterz@...radead.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"hpa@...or.com" <hpa@...or.com>,
"andrew.cooper3@...rix.com" <andrew.cooper3@...rix.com>,
"Christopherson,, Sean" <seanjc@...gle.com>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"Shankar, Ravi V" <ravi.v.shankar@...el.com>
Subject: RE: [PATCH v5 04/34] x86/traps: add external_interrupt() to dispatch
external interrupts
> > > + if (sysvec < NR_SYSTEM_VECTORS) {
> > > + if (system_interrupt_handlers[sysvec])
> > > + system_interrupt_handlers[sysvec](regs);
> > > + else
> > > + dispatch_spurious_interrupt(regs, vector);
> >
> > ISTR suggesting you can get rid of this branch if you stuff
> > system_interrupt_handlers[] with dispatch_spurious_interrupt instead
> > of NULL.
>
> Ah, I suggested that for another function vector, but it applies here too I suppose :-)
Of course!
We just need to use a wrapper as dispatch_spurious_interrupt() takes an extra
parameter "vector".
Thanks!
Xin
Powered by blists - more mailing lists