Re: [patch V4 04/15] entry: Provide generic interrupt entry/exit code

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jul 21, 2020 at 4:08 AM Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:
>
> From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
>
> 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".



[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux