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: <4B7D6503.9040904@redhat.com>
Date:	Thu, 18 Feb 2010 11:04:19 -0500
From:	Masami Hiramatsu <mhiramat@...hat.com>
To:	Mike Frysinger <vapier.adi@...il.com>
CC:	Heiko Carstens <heiko.carstens@...ibm.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	"David S . Miller" <davem@...emloft.net>,
	Paul Mundt <lethal@...ux-sh.org>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH 2/3] tracing/kprobes: Make Kconfig dependencies generic

Mike Frysinger wrote:
>>
>>  config HAVE_REGS_AND_STACK_ACCESS_API
>>        bool
>> +       help
>> +         This symbol should be selected by an architecure if it supports
>> +         the API needed to access registers and stack entries from pt_regs.
>> +         For example the kprobes-based event tracer needs this API.
> 
> a bit vague ... arent there headers/functions people could look at ?
> perhaps you're talking about the regset functions (which is an API to
> access registers in pt_regs) ?  or you're talking about asm/syscall.h
> (which is an API to access registers in pt_regs) ?

We're talking about new API which was introduced by b1cf540f
(regs_get_argument_nth has been dropped on -tip tree anyway)

> i'm not asking to be a pain, i'm asking because i really havent a
> clue.  if i wanted to add support for this stuff to the Blackfin arch,
> i wouldnt know where to start.  even after reading this help i'd fall
> back to grepping arch/x86/ and trying to divine a starting point from
> there.

yeah, I think the comment might be better to refer that APIs are
in arch/*/include/asm/ptrace.h :)

Thank you,

-- 
Masami Hiramatsu

Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division

e-mail: mhiramat@...hat.com

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