From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] runner: Show why we dump the task state
Date: Tue, 07 Apr 2020 12:51:14 +0300 [thread overview]
Message-ID: <87369flj3h.fsf@intel.com> (raw)
In-Reply-To: <158624903366.6356.11697630519432451804@build.alporthouse.com>
On Tue, 07 Apr 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2020-04-07 09:42:01)
>> On Tue, 07 Apr 2020, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>> > Include the reason why we are dumping the task state (test timeout) in
>> > the kmsg log prior to the task state. Hopefully this helps when reading
>> > the dump.
>> >
>> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>> > Cc: Petri Latvala <petri.latvala@intel.com>
>> > ---
>> > runner/executor.c | 25 ++++++++++++++++---------
>> > 1 file changed, 16 insertions(+), 9 deletions(-)
>> >
>> > diff --git a/runner/executor.c b/runner/executor.c
>> > index 1b69f9c57..7061b28d3 100644
>> > --- a/runner/executor.c
>> > +++ b/runner/executor.c
>> > @@ -678,9 +678,20 @@ static bool sysrq(char cmd)
>> > return success;
>> > }
>> >
>> > -static void show_kernel_task_state(void)
>> > +static const char *show_kernel_task_state(const char *msg)
>> > {
>> > + int fd;
>> > +
>> > + fd = open("/dev/kmsg", O_WRONLY);
>> > + if (fd != -1) {
>> > + write(fd, "<4>[IGT] ", 7);
>> > + write(fd, msg, strlen(msg));
>> > + close(fd);
>> > + }
>> > +
>>
>> igt_kmsg(KMSG_WARNING "%s\n", msg);
>
> We're outside of libigt.so
Quoting yourself, "Yeah, I haven't had coffee."
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-04-07 9:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 8:31 [igt-dev] [PATCH i-g-t] runner: Show why we dump the task state Chris Wilson
2020-04-07 8:33 ` [igt-dev] ✗ Fi.CI.BUILD: failure for " Patchwork
2020-04-07 8:34 ` [igt-dev] [PATCH i-g-t] " Chris Wilson
2020-04-07 8:35 ` Chris Wilson
2020-04-07 8:42 ` Jani Nikula
2020-04-07 8:43 ` Chris Wilson
2020-04-07 9:51 ` Jani Nikula [this message]
2020-04-07 9:55 ` Petri Latvala
2020-04-07 9:58 ` Chris Wilson
2020-04-07 8:42 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2020-04-07 9:27 ` [igt-dev] ✓ Fi.CI.BAT: success for runner: Show why we dump the task state (rev2) Patchwork
2020-04-07 10:07 ` [igt-dev] [PATCH i-g-t v2] runner: Show why we dump the task state Chris Wilson
2020-04-07 10:41 ` [igt-dev] ✓ Fi.CI.BAT: success for runner: Show why we dump the task state (rev3) Patchwork
2020-04-07 16:38 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=87369flj3h.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=petri.latvala@intel.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