From: Jiri Olsa <jolsa@redhat.com>
To: Kan Liang <kan.liang@intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, ak@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 2/2] perf,test: test cpu topology
Date: Sat, 29 Aug 2015 12:47:49 +0200 [thread overview]
Message-ID: <20150829104749.GE1787@krava.brq.redhat.com> (raw)
In-Reply-To: <1440769419-48409-2-git-send-email-kan.liang@intel.com>
On Fri, Aug 28, 2015 at 09:43:39AM -0400, Kan Liang wrote:
SNIP
> + TEST_ASSERT_VAL("failed to get system cpumap", !(map == NULL));
> +
> + file.mode = PERF_DATA_MODE_READ;
> + session = perf_session__new(&file, false, NULL);
> + TEST_ASSERT_VAL("can't get session", session);
> +
> + for (i = 0; i < session->header.env.nr_cpus_online; i++) {
> + pr_debug("CPU %d, core %d, socket %d\n", i,
> + session->header.env.cpu[i].core_id,
> + session->header.env.cpu[i].socket_id);
> + }
> +
> + for (i = 0; i < map->nr; i++) {
> + TEST_ASSERT_VAL("Core ID doesn't match",
> + (session->header.env.cpu[map->map[i]].core_id == (cpu_map__get_core(map, i) & 0xffff)));
> +
> + TEST_ASSERT_VAL("Socket ID doesn't match",
> + (session->header.env.cpu[map->map[i]].socket_id == cpu_map__get_socket(map, i)));
> + }
> +
> + perf_session__delete(session);
> + cpu_map__put(map);
unlink(path);
> +
> + return 0;
> +}
> --
> 1.8.3.1
>
next prev parent reply other threads:[~2015-08-29 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-28 13:43 [PATCH V2 1/2] perf,tools: store cpu socket_id and core_id in perf.date Kan Liang
2015-08-28 13:43 ` [PATCH V2 2/2] perf,test: test cpu topology Kan Liang
2015-08-29 10:47 ` Jiri Olsa [this message]
2015-08-29 10:47 ` [PATCH V2 1/2] perf,tools: store cpu socket_id and core_id in perf.date Jiri Olsa
2015-08-31 17:19 ` Liang, Kan
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=20150829104749.GE1787@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox