linux-kernel - Re: [PATCH 1/4] perf_counter: Default to higher paranoia level

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]

Message-Id: <1251098962.7538.143.camel@twins>
Date:	Mon, 24 Aug 2009 09:29:22 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Paul Mackerras <paulus@...ba.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Mike Galbraith <efault@....de>, linux-kernel@...r.kernel.org,
	Jens Axboe <jens.axboe@...cle.com>,
	James Morris <jmorris@...ei.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 1/4] perf_counter: Default to higher paranoia level

On Fri, 2009-08-21 at 16:21 +0200, Ingo Molnar wrote:
> * Peter Zijlstra <peterz@...radead.org> wrote:

> > diff --git a/include/linux/perf_counter.h b/include/linux/perf_counter.h
> > index 9ba1822..2b0528f 100644
> > --- a/include/linux/perf_counter.h
> > +++ b/include/linux/perf_counter.h
> > @@ -439,6 +439,7 @@ enum perf_callchain_context {
> >  struct perf_callchain_entry {
> >  	__u64				nr;
> >  	__u64				ip[PERF_MAX_STACK_DEPTH];
> > +	int				restricted;
> >  };
> 
> i'd love to have something more specific here - i.e. a context type 
> ID that identifies these basic types:
> 
>  - process
>  - softirq
>  - hardirq
>  - NMI
> 
> and then let it be up to upper layers to decide what they do with a 
> restricted entry, and how to further process this information.
> 
> And it's not just security: for example it would be interesting to 
> sample pure, non-irq overhead - as IRQ overhead is often unrelated 
> to the process being measured.

Yes it is, this is purely about not showing some data. If you don't want
to sample IRQ stuff that's something else, we'd have to grow that
capability in hardware (like the OS/USR bits) or put perf enable/disable
hooks into the irq entry/exit hooks (which doesn't sound all too hot an
idea to me).

Simply not showing the call-trace is something all-together different
from not profiling it.
--
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/