Em Thu, Dec 26, 2013 at 09:11:22AM -0500, David Ahern escreveu:
> On 12/24/13, 8:30 AM, Arnaldo Carvalho de Melo wrote:
> >Em Tue, Dec 24, 2013 at 09:53:42AM -0300, Arnaldo Carvalho de Melo escreveu:
> >>>The thing to check is perf_evlist__{prepare,start}_workload notification
> >>>errors using SIG
Em Thu, Dec 26, 2013 at 09:18:17AM -0500, David Ahern escreveu:
> On 12/26/13, 9:15 AM, Arnaldo Carvalho de Melo wrote:
> >Right, but I can't apply that patch, as it makes 'perf stat
> >whatever-workload' to fail, as I realized when doing a demo to someone
> >interested in using perf ;-\
> >
> >So
Em Thu, Dec 26, 2013 at 09:18:17AM -0500, David Ahern escreveu:
> On 12/26/13, 9:15 AM, Arnaldo Carvalho de Melo wrote:
> >Right, but I can't apply that patch, as it makes 'perf stat
> >whatever-workload' to fail, as I realized when doing a demo to someone
> >interested in using perf ;-\
> >
> >So
On 12/26/13, 9:15 AM, Arnaldo Carvalho de Melo wrote:
Right, but I can't apply that patch, as it makes 'perf stat
whatever-workload' to fail, as I realized when doing a demo to someone
interested in using perf ;-\
So for now I'm not applying that one.
right, so you want one with < 0 check or w
Em Thu, Dec 26, 2013 at 09:11:22AM -0500, David Ahern escreveu:
> On 12/24/13, 8:30 AM, Arnaldo Carvalho de Melo wrote:
> >Em Tue, Dec 24, 2013 at 09:53:42AM -0300, Arnaldo Carvalho de Melo escreveu:
> >>>The thing to check is perf_evlist__{prepare,start}_workload notification
> >>>errors using SIG
On 12/24/13, 8:30 AM, Arnaldo Carvalho de Melo wrote:
Em Tue, Dec 24, 2013 at 09:53:42AM -0300, Arnaldo Carvalho de Melo escreveu:
>The thing to check is perf_evlist__{prepare,start}_workload notification
>errors using SIGUSR1, that we need to check for in the caller, and emit
>the message, no?
Em Tue, Dec 24, 2013 at 09:53:42AM -0300, Arnaldo Carvalho de Melo escreveu:
> The thing to check is perf_evlist__{prepare,start}_workload notification
> errors using SIGUSR1, that we need to check for in the caller, and emit
> the message, no?
Something like this:
1. We tell perf_evlist__prepare
Em Mon, Dec 23, 2013 at 07:29:54PM -0500, David Ahern escreveu:
> On 12/23/13, 2:37 PM, Arnaldo Carvalho de Melo wrote:
> >int perf_evlist__start_workload(struct perf_evlist *evlist)
> >{
> > if (evlist->workload.cork_fd > 0) {
> > char bf = 0;
> > /* Remove
On 12/23/13, 2:37 PM, Arnaldo Carvalho de Melo wrote:
int perf_evlist__start_workload(struct perf_evlist *evlist)
{
if (evlist->workload.cork_fd > 0) {
char bf = 0;
int ret;
/*
* Remove the cork, let it rip!
Em Fri, Dec 20, 2013 at 08:57:59AM +0100, Ingo Molnar escreveu:
> * David Ahern wrote:
>
> > Currently perf-stat attempts to show counter stats even if the workload
> > is bogus:
> >
> > $ perf stat -- foo
> > foo: No such file or directory
> >
> > Performance counter stats for 'foo':
> >
> >
* David Ahern wrote:
> Currently perf-stat attempts to show counter stats even if the workload
> is bogus:
>
> $ perf stat -- foo
> foo: No such file or directory
>
> Performance counter stats for 'foo':
>
>task-clock
>context-switches
>cpu-migrations
>
11 matches
Mail list logo
