From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [patch V4 04/15] entry: Provide generic interrupt entry/exit code Date: Wed, 29 Jul 2020 14:18:22 +0200 Message-ID: <87sgdaa50x.fsf@nanos.tec.linutronix.de> References: <20200721105706.030914876@linutronix.de> <20200721110808.671110583@linutronix.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from Galois.linutronix.de ([193.142.43.55]:41764 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726054AbgG2MSY (ORCPT ); Wed, 29 Jul 2020 08:18:24 -0400 In-Reply-To: Sender: linux-arch-owner@vger.kernel.org List-ID: To: Andy Lutomirski Cc: LKML , X86 ML , linux-arch , Will Deacon , Arnd Bergmann , Mark Rutland , Kees Cook , Keno Fischer , Paolo Bonzini , kvm list , Gabriel Krisman Bertazi Andy Lutomirski writes: > On Tue, Jul 21, 2020 at 4:08 AM Thomas Gleixner wrote: >> >> From: Thomas Gleixner >> >> Like the syscall entry/exit code interrupt/exception entry after the real >> low level ASM bits should not be different accross architectures. >> >> Provide a generic version based on the x86 code. > > I don't like the name. Sure, idtentry is ugly and x86-specific, but > irq gives the wrong impression. This is an entry path suitable for > any entry that is guaranteed not to hit during entry/exit handling. > Syscalls, page faults, etc are not "irqs". Yeah, it's exceptions and interrupts, but I did not come up with a better name so far. Thanks, tglx