Andy Lutomirski <[email protected]> writes:
> On Tue, Jul 21, 2020 at 4:08 AM Thomas Gleixner <[email protected]> wrote:
>>
>> From: Thomas Gleixner <[email protected]>
>>
>> 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
