linux-kernel - Re: [page fault tracepoint 1/2] Add page fault trace event definitions

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 09 May 2013 06:48:14 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"zhangwei(Jovi)" <jovi.zhangwei@...wei.com>
CC:	Francis Deslauriers <fdeslaur@...il.com>, linux-mm@...ck.org,
	tglx@...utronix.de, mingo@...hat.com, x86@...nel.org,
	rostedt@...dmis.org, fweisbec@...il.com,
	raphael.beamonte@...il.com, mathieu.desnoyers@...icios.com,
	linux-kernel@...r.kernel.org
Subject: Re: [page fault tracepoint 1/2] Add page fault trace event definitions

On 05/08/2013 11:46 PM, zhangwei(Jovi) wrote:
> On 2013/5/9 14:05, Francis Deslauriers wrote:
>> Add page_fault_entry and page_fault_exit event definitions. It will
>> allow each architecture to instrument their page faults.
> 
> I'm wondering if this tracepoint could handle other page faults,
> like faults in kernel memory(vmalloc, kmmio, etc...)
> 
> And if we decide to support those faults, add a type annotate in TP_printk
> would be much helpful for user, to let user know what type of page faults happened.
> 

The plan for x86 was to switch the IDT so that any exception could get a
trace event without any overhead in normal operation.  This has been in
the process for quite some time but looks like it was getting very close.

	-hpa


--
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/