linux-kernel - Access to local APIC registers during an interrupt handler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4DF389D1.4090909@xaipete.org>
Date:	Sat, 11 Jun 2011 17:29:21 +0200
From:	Robert Uhl <ruhl@...pete.org>
To:	linux-kernel@...r.kernel.org
Subject: Access to local APIC registers during an interrupt handler

Hi,

I wrote a small interrupt handler (for a 64 bit system) which is 
installed by a kernel module in the IDT. My handler just increments a 
global variable and then jumps to the original interrupt handler. So 
Linux does (hopefully ;-) not notice my handler. With sysfs I can read 
the value of these interrupt counter and know exactly how often a 
specific interrupt occured.
Of course on a multicore system the interrupts of all cores are counted 
together, but I want to separate between the cores. On newer CPUs I can 
use the instruction RDTSCP to get the CPU number in ECX, but on older 
CPUs it's unsupported.
So I had the idea to use the local APIC ID to check on which core my 
handler is executed, even though sometimes local APIC ID != core number, 
but the ID should be at least unique.
I get the address of the local APIC ID register at module init with

u64 lapic_idregister = (u64) fix_to_virt(FIX_APIC_BASE) + 0x20;

and use it in my interrupt handler (of course I push/pop all used 
registers):

movq (lapic_idregister), %rcx
movq (%rcx), %rcx

But on real hardware the last instruction seems to cause a page fault or 
something (SUSE with 2.6.37.6, Fedora with 2.6.38.6), the system simply 
reboots. Without this instruction, the handler is executed without any 
problems.
And in qemu with vanilla 2.6.37.6 and a buildroot system everything 
works fine!

I already had a look with qemu which instructions are executed at a 
local APIC timer interrupt (0xEF) until it writes 0x00 to the local APIC 
EOI register (same page), but I still can't figure out what's the 
problem with my code.

Maybe someone knows what is missing or if there is any other fast way to 
figure out on which core the handler is running?

Kind regards,
Robert
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/