From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] perf test: Fix dso cache testcase
Date: Fri, 30 Jan 2015 14:49:22 +0100 [thread overview]
Message-ID: <20150130134922.GB6188@krava.brq.redhat.com> (raw)
In-Reply-To: <1422585209-32742-1-git-send-email-namhyung@kernel.org>
On Fri, Jan 30, 2015 at 11:33:27AM +0900, Namhyung Kim wrote:
> The current dso cache permits to keep dso->data.fd is open under a
> half of open file limit. But test__dso_data_cache() sets dso_cnt to
> limit / 2 + 1 so it'll reach the limit in the loop even though the
> loop count is one less than the dso_cnt and it makes the final
> dso__data_fd() after the loop meaningless.
>
> I guess the intention was dsos[0]->data.fd is open before the last
> open and gets closed after it. So add an assert before the last open.
>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Acked-by: Jiri Olsa <jolsa@kernel.org>
thanks,
jirka
> ---
> tools/perf/tests/dso-data.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/tools/perf/tests/dso-data.c b/tools/perf/tests/dso-data.c
> index caaf37f079b1..22a8c428283a 100644
> --- a/tools/perf/tests/dso-data.c
> +++ b/tools/perf/tests/dso-data.c
> @@ -243,8 +243,8 @@ int test__dso_data_cache(void)
> limit = nr * 4;
> TEST_ASSERT_VAL("failed to set file limit", !set_fd_limit(limit));
>
> - /* and this is now our dso open FDs limit + 1 extra */
> - dso_cnt = limit / 2 + 1;
> + /* and this is now our dso open FDs limit */
> + dso_cnt = limit / 2;
> TEST_ASSERT_VAL("failed to create dsos\n",
> !dsos__create(dso_cnt, TEST_FILE_SIZE));
>
> @@ -268,7 +268,10 @@ int test__dso_data_cache(void)
> }
> }
>
> - /* open +1 dso over the allowed limit */
> + /* verify the first one is already open */
> + TEST_ASSERT_VAL("dsos[0] is not open", dsos[0]->data.fd != -1);
> +
> + /* open +1 dso to reach the allowed limit */
> fd = dso__data_fd(dsos[i], &machine);
> TEST_ASSERT_VAL("failed to get fd", fd > 0);
>
> --
> 2.2.2
>
next prev parent reply other threads:[~2015-01-30 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-30 2:33 Namhyung Kim
2015-01-30 2:33 ` [PATCH 2/3] perf tools: Do not rely on dso__data_read_offset() to open dso Namhyung Kim
2015-01-30 13:56 ` Jiri Olsa
2015-02-18 18:24 ` [tip:perf/core] perf tests: Do not rely on dso__data_read_offset( ) " tip-bot for Namhyung Kim
2015-01-30 2:33 ` [PATCH 3/3] perf tools: Fix a dso open fail message Namhyung Kim
2015-02-18 18:25 ` [tip:perf/core] " tip-bot for Namhyung Kim
2015-01-30 13:49 ` Jiri Olsa [this message]
2015-02-18 18:24 ` [tip:perf/core] perf test: Fix dso cache testcase tip-bot for 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=20150130134922.GB6188@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@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
all inboxes | Powered by JetHome®