linux-kernel - Re: debugctl msr

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]

Date:	Fri, 21 Nov 2008 17:33:07 +0100
From:	"stephane eranian" <eranian@...glemail.com>
To:	"Metzger, Markus T" <markus.t.metzger@...el.com>
Cc:	"Markus Metzger" <markus.t.metzger@...glemail.com>,
	"Ingo Molnar" <mingo@...e.hu>, "Andi Kleen" <andi@...stfloor.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: debugctl msr

On Fri, Nov 21, 2008 at 5:10 PM, Metzger, Markus T
<markus.t.metzger@...el.com> wrote:
>>-----Original Message-----
>>From: stephane eranian [mailto:eranian@...glemail.com]
>>Sent: Freitag, 21. November 2008 16:27
>>To: Metzger, Markus T
>>Cc: Markus Metzger; Ingo Molnar; Andi Kleen; Andrew Morton;
>>linux-kernel@...r.kernel.org
>>Subject: Re: debugctl msr
>
>>The absolute maximum MUST be at buffer+size+1 but the
>>threshold can be anywhere
>>between the start of the buffer and buffer+size. You had it set past
>>the end of the buffer (at +1),
>>therefore PEBS was not generating any interrupts.
>
> The default is cyclic mode, which requires the interrupt threshold
> to be outside of the buffer.
>
That's not what I need.

> A request for interrupt mode should have got you -EOPNOTSUPP.

I did not try that.

>
> Absolute max should be one byte beyond the buffer, which
> is base + size.
>
My bad ;-<
--
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/