From: Chris Wilson <chris@chris-wilson.co.uk>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/selftests: Take rpm wakeref around GGTT lowlevel tests
Date: Tue, 07 Nov 2017 20:22:17 +0000 [thread overview]
Message-ID: <151008613797.14125.956545373047138982@mail.alporthouse.com> (raw)
In-Reply-To: <CAM0jSHMzvguNVeWpUGpsM0zR-VFpHLYR+6Bzfe65vJ4aJ_yfbQ@mail.gmail.com>
Quoting Matthew Auld (2017-11-07 16:20:23)
> On 7 November 2017 at 11:40, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > The vma routines are responsible for acquiring the device rpm wakeref
> > before they poke the HW. However, some of the selftests bypass the
> > higher level vma routines in order to poke directly at the lowlevel GGTT
> > functions; these are then responsible for managing rpm themselves.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Pushed, thanks for the review.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-11-07 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 11:40 [PATCH] drm/i915/selftests: Take rpm wakeref around GGTT lowlevel tests Chris Wilson
2017-11-07 12:27 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-11-07 13:46 ` ✓ Fi.CI.IGT: " Patchwork
2017-11-07 16:20 ` [PATCH] " Matthew Auld
2017-11-07 20:22 ` Chris Wilson [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=151008613797.14125.956545373047138982@mail.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.william.auld@gmail.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 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.