From: Ben Widawsky <benjamin.widawsky@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] intel_l3_parity: More helpful output in case of errors
Date: Tue, 5 Sep 2017 10:14:13 -0700 [thread overview]
Message-ID: <20170905171413.GA4520@intel.com> (raw)
In-Reply-To: <20170905161623.47zzhnacvsvm2pwa@phenom.ffwll.local>
On 17-09-05 18:16:23, Daniel Vetter wrote:
>On Tue, Sep 05, 2017 at 03:39:49PM +0300, Petri Latvala wrote:
>> When no action is specified on the command line, print the usage help
>> text and exit with failure instead of SIGABRT. Fix some typos on the
>> usage text.
>>
>> Keep the abort() call in places where they can only be reached by
>> expanding the tool and forgetting to handle new parameters, with an
>> error message printed.
>>
>> CC: Ben Widawsky <benjamin.widawsky@intel.com>
>> Signed-off-by: Petri Latvala <petri.latvala@intel.com>
>> ---
>> tools/intel_l3_parity.c | 12 +++++++++---
>> 1 file changed, 9 insertions(+), 3 deletions(-)
>>
>> diff --git a/tools/intel_l3_parity.c b/tools/intel_l3_parity.c
>> index eb00c50..1a4fae5 100644
>> --- a/tools/intel_l3_parity.c
>> +++ b/tools/intel_l3_parity.c
>> @@ -172,9 +172,9 @@ static void usage(const char *name)
>> " -l, --list List the current L3 logs\n"
>> " -a, --clear-all Clear all disabled rows\n"
>> " -e, --enable Enable row, bank, subbank (undo -d)\n"
>> - " -d, --disable=<row,bank,subbank> Disable row, bank, subbank (inline arguments are deprecated. Please use -r, -b, -s instead\n"
>> - " -i, --inject [HSW only] Cause hardware to inject a row errors\n"
>> - " -u, --uninject [HSW only] Turn off hardware error injectection (undo -i)\n"
>> + " -d, --disable=<row,bank,subbank> Disable row, bank, subbank (inline arguments are deprecated. Please use -r, -b, -s instead)\n"
>> + " -i, --inject [HSW only] Cause hardware to inject a row error\n"
>> + " -u, --uninject [HSW only] Turn off hardware error injection (undo -i)\n"
+1 for fixing the typo.
I think we should be careful about using "HSW only". In fact I'm in favor of
removing what was already there because I honestly don't know which platforms
support this feature.
>> " -L, --listen Listen for uevent errors\n",
>> name);
>> }
>> @@ -301,6 +301,7 @@ int main(int argc, char *argv[])
>> action = c;
>> break;
>> default:
>> + fprintf(stderr, "Internal error: Unhandled flag %c\n", c);
>> abort();
>> }
>> }
>> @@ -374,7 +375,12 @@ int main(int argc, char *argv[])
>> break;
>> case 'L':
>> break;
>> + case '0':
>> + /* No action given */
>> + usage(argv[0]);
>> + exit(EXIT_FAILURE);
>
>Won't this print usage once per slice? Or am I misreading how the patch
>applies ...
>-Daniel
>
Looks wrong to me as well.
>> default:
>> + fprintf(stderr, "Internal error: Unhandled action %d\n", action);
>> abort();
>> }
>> }
>> --
>> 2.9.3
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
>--
>Daniel Vetter
>Software Engineer, Intel Corporation
>http://blog.ffwll.ch
--
Ben Widawsky, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-09-05 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 12:39 [PATCH i-g-t] intel_l3_parity: More helpful output in case of errors Petri Latvala
2017-09-05 12:56 ` ✗ Fi.CI.BAT: warning for " Patchwork
2017-09-05 16:16 ` [PATCH i-g-t] " Daniel Vetter
2017-09-05 17:14 ` Ben Widawsky [this message]
2017-09-06 9:31 ` Petri Latvala
2017-09-08 6:57 ` Daniel Vetter
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=20170905171413.GA4520@intel.com \
--to=benjamin.widawsky@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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