linux-kernel - Re: [PATCH 2/3] perf tools: allow user to specify hardware breakpoint bp

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: <20131210162229.GB23086@redhat.com>
Date:	Tue, 10 Dec 2013 17:22:29 +0100
From:	Oleg Nesterov <oleg@...hat.com>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	suravee.suthikulpanit@....com, mingo@...nel.org, mingo@...hat.com,
	jacob.w.shin@...il.com, a.p.zijlstra@...llo.nl,
	acme@...stprotocols.net, hpa@...or.com, tgl@...ain.invalid,
	linux-kernel@...r.kernel.org, sherry.hurwitz@....com
Subject: Re: [PATCH 2/3] perf tools: allow user to specify hardware
	breakpoint bp_len

On 12/10, Frederic Weisbecker wrote:
>
> On Wed, Oct 02, 2013 at 11:11:07AM -0500, suravee.suthikulpanit@....com wrote:
> > @@ -525,14 +525,11 @@ int parse_events_add_breakpoint(struct list_head *list, int *idx,
> >  	if (parse_breakpoint_type(type, &attr))
> >  		return -EINVAL;
> >
> > -	/*
> > -	 * We should find a nice way to override the access length
> > -	 * Provide some defaults for now
> > -	 */
> > -	if (attr.bp_type == HW_BREAKPOINT_X)
> > -		attr.bp_len = sizeof(long);
> > -	else
> > -		attr.bp_len = HW_BREAKPOINT_LEN_4;
> > +	/* Provide some defaults if len is not specified */
> > +	if (!len)
> > +		len = attr.bp_type == HW_BREAKPOINT_X ? sizeof(long) :
> > +							HW_BREAKPOINT_LEN_4;
>
> Why is LEN_4 affected in the type?

Hmm, what do you mean?

Oleg.

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