From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/5] i915: Start putting the mmio_base to wider use
Date: Fri, 28 Feb 2020 23:27:19 +0200 [thread overview]
Message-ID: <20200228212719.GL1514@intel.intel> (raw)
In-Reply-To: <20200228104340.2895082-1-chris@chris-wilson.co.uk>
Hi Chris,
On Fri, Feb 28, 2020 at 10:43:36AM +0000, Chris Wilson wrote:
> Several tests depend upon the implicit engine->mmio_base but have no
> means of determining the physical layout. Since the kernel has started
> providing this information, start putting it to use.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Looks good!
Reviewed-by: Andi Shyti <andi.shyti@intel.com>
Andi
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
WARNING: multiple messages have this Message-ID (diff)
From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t 1/5] i915: Start putting the mmio_base to wider use
Date: Fri, 28 Feb 2020 23:27:19 +0200 [thread overview]
Message-ID: <20200228212719.GL1514@intel.intel> (raw)
In-Reply-To: <20200228104340.2895082-1-chris@chris-wilson.co.uk>
Hi Chris,
On Fri, Feb 28, 2020 at 10:43:36AM +0000, Chris Wilson wrote:
> Several tests depend upon the implicit engine->mmio_base but have no
> means of determining the physical layout. Since the kernel has started
> providing this information, start putting it to use.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Looks good!
Reviewed-by: Andi Shyti <andi.shyti@intel.com>
Andi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-02-28 21:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 10:43 [igt-dev] [PATCH i-g-t 1/5] i915: Start putting the mmio_base to wider use Chris Wilson
2020-02-28 10:43 ` [Intel-gfx] " Chris Wilson
2020-02-28 10:43 ` [Intel-gfx] [PATCH i-g-t 2/5] i915/gem_ctx_isolation: Check engine relative registers Chris Wilson
2020-02-28 19:46 ` [igt-dev] " Stimson, Dale B
2020-02-28 19:46 ` Stimson, Dale B
2020-02-28 10:43 ` [igt-dev] [PATCH i-g-t 3/5] i915: Exercise preemption timeout controls in sysfs Chris Wilson
2020-02-28 10:43 ` [Intel-gfx] " Chris Wilson
2020-02-28 23:27 ` Andi Shyti
2020-02-28 23:32 ` [igt-dev] " Chris Wilson
2020-02-28 23:32 ` Chris Wilson
2020-02-28 23:51 ` Andi Shyti
2020-02-29 10:21 ` [igt-dev] " Chris Wilson
2020-02-29 10:21 ` Chris Wilson
2020-02-29 12:45 ` Andi Shyti
2020-02-29 18:34 ` [igt-dev] " Chris Wilson
2020-02-29 18:34 ` Chris Wilson
2020-02-29 18:39 ` Chris Wilson
2020-02-28 10:43 ` [Intel-gfx] [PATCH i-g-t 4/5] i915: Exercise sysfs heartbeat controls Chris Wilson
2020-02-28 23:34 ` Andi Shyti
2020-02-28 23:37 ` [igt-dev] " Chris Wilson
2020-02-28 23:37 ` Chris Wilson
2020-02-28 10:43 ` [igt-dev] [PATCH i-g-t 5/5] i915: Exercise timeslice sysfs property Chris Wilson
2020-02-28 10:43 ` [Intel-gfx] " Chris Wilson
2020-02-28 11:15 ` [igt-dev] ✗ GitLab.Pipeline: failure for series starting with [i-g-t,1/5] i915: Start putting the mmio_base to wider use Patchwork
2020-02-28 11:52 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-02-28 19:45 ` [igt-dev] [PATCH i-g-t 1/5] " Stimson, Dale B
2020-02-28 19:45 ` [Intel-gfx] " Stimson, Dale B
2020-02-28 21:27 ` Andi Shyti [this message]
2020-02-28 21:27 ` [Intel-gfx] " Andi Shyti
2020-03-01 1:09 ` [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/5] " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2020-01-27 12:18 [igt-dev] [PATCH i-g-t 1/5] " Chris Wilson
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=20200228212719.GL1514@intel.intel \
--to=andi.shyti@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--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.