All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@ghostprotocols.net, LKML <linux-kernel@vger.kernel.org>,
	namhyung@gmail.com
Subject: Re: [PATCH 1/4 v2] perf: Allow ability to map cpus to nodes easily
Date: Thu, 10 Apr 2014 09:54:33 -0400	[thread overview]
Message-ID: <20140410135433.GH8488@redhat.com> (raw)
In-Reply-To: <20140410132458.GB13001@krava.brq.redhat.com>

On Thu, Apr 10, 2014 at 03:24:58PM +0200, Jiri Olsa wrote:
> On Thu, Apr 10, 2014 at 09:15:15AM -0400, Don Zickus wrote:
> > On Thu, Apr 10, 2014 at 11:31:46AM +0200, Jiri Olsa wrote:
> > > On Mon, Apr 07, 2014 at 02:55:21PM -0400, Don Zickus wrote:
> > > 
> > > SNIP
> > > 
> > > > +static int init_cpunode_map(void)
> > > > +{
> > > > +	int i;
> > > > +
> > > > +	set_max_cpu_num();
> > > > +	set_max_node_num();
> > > > +
> > > > +	cpunode_map = calloc(max_cpu_num, sizeof(int));
> > > > +	if (!cpunode_map) {
> > > > +		pr_err("%s: calloc failed\n", __func__);
> > > > +		goto out;
> > > shuld probably be ^^^:
> > > 
> > > 		return -1;
> > > 
> > > > +	}
> > > > +
> > > > +	for (i = 0; i < max_cpu_num; i++)
> > > > +		cpunode_map[i] = -1;
> > > > +
> > > > +	return 0;
> > > > +out:
> > > > +	return -1;
> > > 
> > > and remove 'out' label code
> > 
> > Sorry, probably leftover code that after snipping and changing didn't get
> > noticed.  Thanks.
> > 
> > > 
> > > other than that, it seems ok.. I'll queue it
> > 
> > I assume you are making the changes locally or should I resubmit?
> 
> yes, I'll do that localy

Thanks!

Cheers,
Don

  reply	other threads:[~2014-04-10 13:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 18:55 [PATCH 0/4 v2] perf: Make some functions generic Don Zickus
2014-04-07 18:55 ` [PATCH 1/4 v2] perf: Allow ability to map cpus to nodes easily Don Zickus
2014-04-10  9:31   ` Jiri Olsa
2014-04-10 13:15     ` Don Zickus
2014-04-10 13:24       ` Jiri Olsa
2014-04-10 13:54         ` Don Zickus [this message]
2014-04-22 18:34   ` [tip:perf/core] perf tools: " tip-bot for Don Zickus
2014-04-07 18:55 ` [PATCH 2/4 v2] perf: Use cpu/possible instead of cpu/kernel_max Don Zickus
2014-04-22 18:34   ` [tip:perf/core] perf tools: Use cpu/possible instead of cpu/ kernel_max tip-bot for Don Zickus
2014-04-07 18:55 ` [PATCH 3/4 v2] perf, kmem: Utilize the new generic cpunode_map Don Zickus
2014-04-22 18:34   ` [tip:perf/core] perf " tip-bot for Don Zickus
2014-04-07 18:55 ` [PATCH 4/4 v2] perf, callchain: Add generic report parse callchain callback function Don Zickus
2014-04-22 18:34   ` [tip:perf/core] perf " tip-bot for Don Zickus
2014-04-09  0:31 ` [PATCH 0/4 v2] perf: Make some functions generic Namhyung Kim

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=20140410135433.GH8488@redhat.com \
    --to=dzickus@redhat.com \
    --cc=acme@ghostprotocols.net \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@gmail.com \
    /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.