From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH igt] igt: Add a test to precheck status of kernel taints
Date: Fri, 11 Aug 2017 17:33:10 +0300 [thread overview]
Message-ID: <87bmnmdvix.fsf@nikula.org> (raw)
In-Reply-To: <150245743773.23791.14995561922863507578@mail.alporthouse.com>
On Fri, 11 Aug 2017, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2017-08-11 14:15:50)
>> On Fri, 11 Aug 2017, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>> > Many times an error may occur before the start of igt, leaving the
>> > system in a less-than-optimal debugging state (e.g. an oops turning off
>> > lockdep). Flag such occasions by checking /proc/sys/kernel/tainted.
>>
>> Hmm, which flag is set for unsafe module params?
>
> That is
>
> CHECK(6, "Tainted by user request", WARN);
>
> I left it as WARN because imo we shouldn't be using those to drive
> tests.
Agreed... but i915.alpha_support, i915.inject_load_failure, what else?
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-08-11 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 12:46 [PATCH igt] igt: Add a test to precheck status of kernel taints Chris Wilson
2017-08-11 13:15 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-08-11 13:15 ` [PATCH igt] " Jani Nikula
2017-08-11 13:17 ` Chris Wilson
2017-08-11 14:33 ` Jani Nikula [this message]
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=87bmnmdvix.fsf@nikula.org \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.