[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <SA1PR11MB673422CC60B9A9C4F875AA76A85CA@SA1PR11MB6734.namprd11.prod.outlook.com>
Date: Tue, 20 Jun 2023 00:16:38 +0000
From: "Li, Xin3" <xin3.li@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>
CC: "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>,
"peterz@...radead.org" <peterz@...radead.org>,
"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>,
"jiangshanlai@...il.com" <jiangshanlai@...il.com>,
"Kang, Shan" <shan.kang@...el.com>
Subject: RE: [PATCH v8 05/33] x86/traps: add external_interrupt() to dispatch
external interrupts
> That's not the point. Your changelog says:
>
> If an external interrupt is a system interrupt...
>
> It's either an external interrupt which goes through common_interrupt()
> or it is a system interrupt which goes through it's very own handler,
> no?
Ah, then it looks more of a problem in the way how I described it.
What I wanted to describe is the dispatch logic _inside_ the new function
external_interrupt(), what about:
external_interrupt() dispatches all external interrupts: it checks if an
external interrupt is a system interrupt, if yes it dipatches it through
the system_interrupt_handlers table, otherwise to dispatch_common_interrupt().
Thanks!
Xin
Powered by blists - more mailing lists