From: Dave Jones <davej@redhat.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: trinity@vger.kernel.org
Subject: Re: a perf_event_open() update
Date: Fri, 17 May 2013 21:01:49 -0400 [thread overview]
Message-ID: <20130518010149.GA21455@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1305171115180.8633@vincent-weaver-1.um.maine.edu>
On Fri, May 17, 2013 at 11:18:39AM -0400, Vince Weaver wrote:
>
> Here's a patch that improves slightly the coverage in perf_event_open().
>
> It handles cache events and breakpoint events.
>
> perf_event_open() is such a complicated syscall it's fairly unlikely to
> generate a valid event randomly, even with these changes.
>
> Also a question: is there a way to easily generate a 64-bit random number?
> >From what I can tell rand() only generates a 32-bit one?
I was going to wait until I get back from vacation, but
your comment persuaded me to push out what's in my
current tree. check out rand64.
totally untested so far beyond compile testing.
more when I get back on Tuesday.
Dave
next prev parent reply other threads:[~2013-05-18 1:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 15:18 a perf_event_open() update Vince Weaver
2013-05-17 21:20 ` [patch] " Vince Weaver
2013-05-18 1:01 ` Dave Jones [this message]
2013-05-20 3:34 ` [patch] " Vince Weaver
2013-05-21 16:54 ` Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130518010149.GA21455@redhat.com \
--to=davej@redhat.com \
--cc=trinity@vger.kernel.org \
--cc=vincent.weaver@maine.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.