All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, mpe@ellerman.id.au,
	jolsa@kernel.org, maddy@linux.ibm.com,
	ravi.bangoria@linux.ibm.com, kjain@linux.ibm.com,
	kan.liang@linux.intel.com, peterz@infradead.org
Subject: Re: [PATCH] perf bench numa: Fix the condition checks for max number of numa nodes
Date: Tue, 2 Mar 2021 09:33:31 -0300	[thread overview]
Message-ID: <YD4wm2I48rXUM/1D@kernel.org> (raw)
In-Reply-To: <20210226085827.GF2028034@linux.vnet.ibm.com>

Em Fri, Feb 26, 2021 at 02:28:27PM +0530, Srikar Dronamraju escreveu:
> * Athira Rajeev <atrajeev@linux.vnet.ibm.com> [2021-02-25 11:50:02]:
> 
> > In systems having higher node numbers available like node
> > 255, perf numa bench will fail with SIGABORT.
> > 
> > <<>>
> > perf: bench/numa.c:1416: init: Assertion `!(g->p.nr_nodes > 64 || g->p.nr_nodes < 0)' failed.
> > Aborted (core dumped)
> > <<>>
> > 
> 
> Looks good to me.
> 
> Reviewed-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>

Thanks, applied.

- Arnaldo


WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
Cc: ravi.bangoria@linux.ibm.com,
	Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
	peterz@infradead.org, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, maddy@linux.ibm.com,
	jolsa@kernel.org, kjain@linux.ibm.com,
	linuxppc-dev@lists.ozlabs.org, kan.liang@linux.intel.com
Subject: Re: [PATCH] perf bench numa: Fix the condition checks for max number of numa nodes
Date: Tue, 2 Mar 2021 09:33:31 -0300	[thread overview]
Message-ID: <YD4wm2I48rXUM/1D@kernel.org> (raw)
In-Reply-To: <20210226085827.GF2028034@linux.vnet.ibm.com>

Em Fri, Feb 26, 2021 at 02:28:27PM +0530, Srikar Dronamraju escreveu:
> * Athira Rajeev <atrajeev@linux.vnet.ibm.com> [2021-02-25 11:50:02]:
> 
> > In systems having higher node numbers available like node
> > 255, perf numa bench will fail with SIGABORT.
> > 
> > <<>>
> > perf: bench/numa.c:1416: init: Assertion `!(g->p.nr_nodes > 64 || g->p.nr_nodes < 0)' failed.
> > Aborted (core dumped)
> > <<>>
> > 
> 
> Looks good to me.
> 
> Reviewed-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>

Thanks, applied.

- Arnaldo


  reply	other threads:[~2021-03-03  5:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 16:50 [PATCH] perf bench numa: Fix the condition checks for max number of numa nodes Athira Rajeev
2021-02-25 16:50 ` Athira Rajeev
2021-02-26  8:58 ` Srikar Dronamraju
2021-02-26  8:58   ` Srikar Dronamraju
2021-03-02 12:33   ` Arnaldo Carvalho de Melo [this message]
2021-03-02 12:33     ` Arnaldo Carvalho de Melo

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=YD4wm2I48rXUM/1D@kernel.org \
    --to=acme@kernel.org \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=kjain@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=srikar@linux.vnet.ibm.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.