From: kajoljain <kjain@linux.ibm.com>
To: John Garry <john.garry@huawei.com>,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org, irogers@google.com,
yao.jin@linux.intel.com, yeyunfeng@huawei.com
Cc: linux-kernel@vger.kernel.org, linuxarm@huawei.com
Subject: Re: [PATCH v2 1/2] perf jevents: Tidy error handling
Date: Fri, 23 Oct 2020 13:19:27 +0530 [thread overview]
Message-ID: <58c219e5-78a9-be21-4942-b6ba9d21d467@linux.ibm.com> (raw)
In-Reply-To: <1603364547-197086-2-git-send-email-john.garry@huawei.com>
On 10/22/20 4:32 PM, John Garry wrote:
> There is much duplication in the error handling for directory transvering
> for prcessing JSONs.
>
> Factor out the common code to tidy a bit.
>
Patch looks good to me.
Reviewed-By: Kajol Jain<kjain@linux.ibm.com>
Thanks,
Kajol Jain
> Signed-off-by: John Garry <john.garry@huawei.com>
> ---
> tools/perf/pmu-events/jevents.c | 83 ++++++++++++++-------------------
> 1 file changed, 35 insertions(+), 48 deletions(-)
>
> diff --git a/tools/perf/pmu-events/jevents.c b/tools/perf/pmu-events/jevents.c
> index e47644cab3fa..7326c14c4623 100644
> --- a/tools/perf/pmu-events/jevents.c
> +++ b/tools/perf/pmu-events/jevents.c
> @@ -1100,12 +1100,13 @@ static int process_one_file(const char *fpath, const struct stat *sb,
> */
> int main(int argc, char *argv[])
> {
> - int rc, ret = 0;
> + int rc, ret = 0, empty_map = 0;
> int maxfds;
> char ldirname[PATH_MAX];
> const char *arch;
> const char *output_file;
> const char *start_dirname;
> + char *err_string_ext = "";
> struct stat stbuf;
>
> prog = basename(argv[0]);
> @@ -1133,7 +1134,8 @@ int main(int argc, char *argv[])
> /* If architecture does not have any event lists, bail out */
> if (stat(ldirname, &stbuf) < 0) {
> pr_info("%s: Arch %s has no PMU event lists\n", prog, arch);
> - goto empty_map;
> + empty_map = 1;
> + goto err_close_eventsfp;
> }
>
> /* Include pmu-events.h first */
> @@ -1150,75 +1152,60 @@ int main(int argc, char *argv[])
> */
>
> maxfds = get_maxfds();
> - mapfile = NULL;
> rc = nftw(ldirname, preprocess_arch_std_files, maxfds, 0);
> - if (rc && verbose) {
> - pr_info("%s: Error preprocessing arch standard files %s\n",
> - prog, ldirname);
> - goto empty_map;
> - } else if (rc < 0) {
> - /* Make build fail */
> - fclose(eventsfp);
> - free_arch_std_events();
> - return 1;
> - } else if (rc) {
> - goto empty_map;
> - }
> + if (rc)
> + goto err_processing_std_arch_event_dir;
>
> rc = nftw(ldirname, process_one_file, maxfds, 0);
> - if (rc && verbose) {
> - pr_info("%s: Error walking file tree %s\n", prog, ldirname);
> - goto empty_map;
> - } else if (rc < 0) {
> - /* Make build fail */
> - fclose(eventsfp);
> - free_arch_std_events();
> - ret = 1;
> - goto out_free_mapfile;
> - } else if (rc) {
> - goto empty_map;
> - }
> + if (rc)
> + goto err_processing_dir;
>
> sprintf(ldirname, "%s/test", start_dirname);
>
> rc = nftw(ldirname, process_one_file, maxfds, 0);
> - if (rc && verbose) {
> - pr_info("%s: Error walking file tree %s rc=%d for test\n",
> - prog, ldirname, rc);
> - goto empty_map;
> - } else if (rc < 0) {
> - /* Make build fail */
> - free_arch_std_events();
> - ret = 1;
> - goto out_free_mapfile;
> - } else if (rc) {
> - goto empty_map;
> - }
> + if (rc)
> + goto err_processing_dir;
>
> if (close_table)
> print_events_table_suffix(eventsfp);
>
> if (!mapfile) {
> pr_info("%s: No CPU->JSON mapping?\n", prog);
> - goto empty_map;
> + empty_map = 1;
> + goto err_close_eventsfp;
> }
>
> - if (process_mapfile(eventsfp, mapfile)) {
> + rc = process_mapfile(eventsfp, mapfile);
> + fclose(eventsfp);
> + if (rc) {
> pr_info("%s: Error processing mapfile %s\n", prog, mapfile);
> /* Make build fail */
> - fclose(eventsfp);
> - free_arch_std_events();
> ret = 1;
> + goto err_out;
> }
>
> + free_arch_std_events();
> + free(mapfile);
> + return 0;
>
> - goto out_free_mapfile;
> -
> -empty_map:
> +err_processing_std_arch_event_dir:
> + err_string_ext = " for std arch event";
> +err_processing_dir:
> + if (verbose) {
> + pr_info("%s: Error walking file tree %s%s\n", prog, ldirname,
> + err_string_ext);
> + empty_map = 1;
> + } else if (rc < 0) {
> + ret = 1;
> + } else {
> + empty_map = 1;
> + }
> +err_close_eventsfp:
> fclose(eventsfp);
> - create_empty_mapping(output_file);
> + if (empty_map)
> + create_empty_mapping(output_file);
> +err_out:
> free_arch_std_events();
> -out_free_mapfile:
> free(mapfile);
> return ret;
> }
>
next prev parent reply other threads:[~2020-10-23 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 11:02 [PATCH v2 0/2] perf PMU events test: Add scenario for arch std events John Garry
2020-10-22 11:02 ` [PATCH v2 1/2] perf jevents: Tidy error handling John Garry
2020-10-23 7:49 ` kajoljain [this message]
2020-10-22 11:02 ` [PATCH v2 2/2] perf jevents: Add test for arch std events John Garry
2020-10-23 7:57 ` kajoljain
2020-10-27 16:34 ` [PATCH v2 0/2] perf PMU events test: Add scenario " 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=58c219e5-78a9-be21-4942-b6ba9d21d467@linux.ibm.com \
--to=kjain@linux.ibm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yao.jin@linux.intel.com \
--cc=yeyunfeng@huawei.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 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®