<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/x86/include/asm/trace/exceptions.h, branch linux-4.12.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.12.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.12.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2016-12-09T14:13:30Z</updated>
<entry>
<title>tracing: Have the reg function allow to fail</title>
<updated>2016-12-09T14:13:30Z</updated>
<author>
<name>Steven Rostedt (Red Hat)</name>
</author>
<published>2016-11-28T18:03:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8cf868affdc459beee1a941df0cfaba1673740e3'/>
<id>urn:sha1:8cf868affdc459beee1a941df0cfaba1673740e3</id>
<content type='text'>
Some tracepoints have a registration function that gets enabled when the
tracepoint is enabled. There may be cases that the registraction function
must fail (for example, can't allocate enough memory). In this case, the
tracepoint should also fail to register, otherwise the user would not know
why the tracepoint is not working.

Cc: David Howells &lt;dhowells@redhat.com&gt;
Cc: Seiji Aguchi &lt;seiji.aguchi@hds.com&gt;
Cc: Anton Blanchard &lt;anton@samba.org&gt;
Cc: Mathieu Desnoyers &lt;mathieu.desnoyers@efficios.com&gt;
Signed-off-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;
</content>
</entry>
<entry>
<title>x86, trace: Change user|kernel_page_fault to page_fault_user|kernel</title>
<updated>2013-11-11T16:15:40Z</updated>
<author>
<name>H. Peter Anvin</name>
</author>
<published>2013-11-11T16:15:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a4f61dec55c1bdebb84ba77212ebf98f7247736c'/>
<id>urn:sha1:a4f61dec55c1bdebb84ba77212ebf98f7247736c</id>
<content type='text'>
Tracepoints are named hierachially, and it makes more sense to keep a
general flow of information level from general to specific from left
to right, i.e.

	x86_exceptions.page_fault_user|kernel

rather than

	x86_exceptions.user|kernel_page_fault

Suggested-by: Ingo Molnar &lt;mingo@kernel.org&gt;
Acked-by: Seiji Aguchi &lt;seiji.aguchi@hds.com&gt;
Signed-off-by: H. Peter Anvin &lt;hpa@zytor.com&gt;
Link: http://lkml.kernel.org/r/20131111082955.GB12405@gmail.com
</content>
</entry>
<entry>
<title>x86, trace: Add page fault tracepoints</title>
<updated>2013-11-08T22:15:49Z</updated>
<author>
<name>Seiji Aguchi</name>
</author>
<published>2013-10-30T20:39:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d34603b07c4255b2b00a546d34f297ccd50ae4c6'/>
<id>urn:sha1:d34603b07c4255b2b00a546d34f297ccd50ae4c6</id>
<content type='text'>
This patch introduces page fault tracepoints to x86 architecture
by switching IDT.

  Two events, for user and kernel spaces, are introduced at the beginning
  of page fault handler for tracing.

  - User space event
    There is a request of page fault event for user space as below.

    https://lkml.kernel.org/r/1368079520-11015-2-git-send-email-fdeslaur+()+gmail+!+com
    https://lkml.kernel.org/r/1368079520-11015-1-git-send-email-fdeslaur+()+gmail+!+com

  - Kernel space event:
    When we measure an overhead in kernel space for investigating performance
    issues, we can check if it comes from the page fault events.

Signed-off-by: Seiji Aguchi &lt;seiji.aguchi@hds.com&gt;
Link: http://lkml.kernel.org/r/52716E67.6090705@hds.com
Signed-off-by: H. Peter Anvin &lt;hpa@linux.intel.com&gt;
</content>
</entry>
</feed>
