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] [day] [month] [year] [list]
Date:	Wed, 25 Jun 2014 15:33:10 +0400
From:	Stanislav Fomichev <stfomichev@...dex-team.ru>
To:	Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:	a.p.zijlstra@...llo.nl, paulus@...ba.org, mingo@...hat.com,
	dsahern@...il.com, jolsa@...hat.com,
	xiaoguangrong@...ux.vnet.ibm.com, yangds.fnst@...fujitsu.com,
	adrian.hunter@...el.com, namhyung@...nel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/5] perf trace: add support for pagefault tracing

> > Also, have you considered using:
> > 
> > [root@zoo ~]# perf list exceptions:page_fault*
> >   exceptions:page_fault_user                         [Tracepoint event]
> >   exceptions:page_fault_kernel                       [Tracepoint event]
> > [root@zoo ~]#
> > 
> > Instead? I need to check if they're completely equivalent to what we
> > need here...
> Hm, didn't know there are two kinds of fault events :-/
> But it seems these are x86 only.
Maybe we can use these x86 only events to trace userspace fault duration?
It seems we can pair exceptions:page_fault_user and
context_tracking:user_enter. But it's just a theory, need to verify...
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ