From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.BAT: warning for kernfs: Move faulting copy_user operations outside of the mutex (rev2)
Date: Tue, 29 Mar 2016 15:45:48 +0300 [thread overview]
Message-ID: <1459255548.8043.7.camel@linux.intel.com> (raw)
In-Reply-To: <20160329123818.GE27742@nuc-i3427.alporthouse.com>
On ti, 2016-03-29 at 13:38 +0100, Chris Wilson wrote:
> On Tue, Mar 29, 2016 at 03:31:24PM +0300, Joonas Lahtinen wrote:
> >
> > On to, 2016-03-24 at 17:03 +0000, Chris Wilson wrote:
> > >
> > > On Thu, Mar 24, 2016 at 04:34:01PM -0000, Patchwork wrote:
> > > >
> > > >
> > > > == Series Details ==
> > > >
> > > > Series: kernfs: Move faulting copy_user operations outside of the mutex (rev2)
> > > > URL : https://patchwork.freedesktop.org/series/3722/
> > > > State : warning
> > > >
> > > > == Summary ==
> > > >
> > > > Series 3722v2 kernfs: Move faulting copy_user operations outside of the mutex
> > > > http://patchwork.freedesktop.org/api/1.0/series/3722/revisions/2/mbox/
> > > >
> > > > Test pm_rpm:
> > > > Subgroup basic-rte:
> > > > pass -> DMESG-WARN (bsw-nuc-2)
> > This WARN is about Unclaimed access detected, which we have an open bug
> > for.
> >
> > >
> > > >
> > > > dmesg-warn -> PASS (byt-nuc) UNSTABLE
> > > Something is notable by its absence here!
> > Other tests were fine in the run.
> >
> > >
> > >
> > > Would someone do the honours and see if the suspend tests pass without
> > > lockdep WARNs on Brasweel?
> > To me it seems it worked just fine. OK if I merge this (and rebase if
> > needed)?
> I was expecting to see a fair few dmesg-warn -> PASS (bsw) since the
> purpose of this patch is to cut down on the CI noise. If they are
> passing without the patch, this patch is not required, right?
The problem with the lockdep issues that are plaguing the CI is they
only appear every now and then. So we would only notice after applying,
when the amount of noise reduces. I would use the above as a reference
that the patch will not make things worse.
You can take a look at /archive/results/CI_IGT_test/bsw-nuc-2.html to
see for yourself a long-term history.
Regards, Joonas
> -Chris
>
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2016-03-29 12:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 14:38 [PATCH] kernfs: Move faulting copy_user operations outside of the mutex Chris Wilson
2016-03-24 15:01 ` Joonas Lahtinen
2016-03-24 16:34 ` ✗ Fi.CI.BAT: warning for kernfs: Move faulting copy_user operations outside of the mutex (rev2) Patchwork
2016-03-24 17:03 ` Chris Wilson
2016-03-29 12:31 ` Joonas Lahtinen
2016-03-29 12:38 ` Chris Wilson
2016-03-29 12:45 ` Joonas Lahtinen [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=1459255548.8043.7.camel@linux.intel.com \
--to=joonas.lahtinen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox