From: "Tang, CQ" <cq.tang@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check engine relative registers
Date: Thu, 21 Nov 2019 23:56:05 +0000 [thread overview]
Message-ID: <1D440B9B88E22A4ABEF89F9F1F81BC29E94A74D9@FMSMSX106.amr.corp.intel.com> (raw)
In-Reply-To: <157437988036.2524.15103838845430811433@skylake-alporthouse-com>
> -----Original Message-----
> From: Chris Wilson <chris@chris-wilson.co.uk>
> Sent: Thursday, November 21, 2019 3:45 PM
> To: Tang, CQ <cq.tang@intel.com>; intel-gfx@lists.freedesktop.org
> Cc: igt-dev@lists.freedesktop.org
> Subject: RE: [Intel-gfx] [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check
> engine relative registers
>
> Quoting Tang, CQ (2019-11-21 21:07:13)
> >
> >
> > > -----Original Message-----
> > > From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf
> > > Of Chris Wilson
> > > Sent: Wednesday, November 13, 2019 4:53 AM
> > > To: intel-gfx@lists.freedesktop.org
> > > Cc: igt-dev@lists.freedesktop.org
> > > Subject: [Intel-gfx] [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check
> > > engine @@ -248,6 +238,7 @@ static void tmpl_regs(int fd, {
> > > const unsigned int gen_bit = 1 <<
> > > intel_gen(intel_get_drm_devid(fd));
> > > const unsigned int engine_bit = ENGINE(e->class, e->instance);
> > > + const uint32_t mmio_base = gem_engine_mmio_base(fd, e->name);
> >
> > Chris, I tried to test this patch, but "gem_engine_mmio_base()" above is
> not defined.
> > Can you check?
>
> Did you perchance look at patch 4?
Thanks, find this one:
[i-g-t,4/9] i915: Start putting the mmio_base to wider use
--CQ
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: "Tang, CQ" <cq.tang@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check engine relative registers
Date: Thu, 21 Nov 2019 23:56:05 +0000 [thread overview]
Message-ID: <1D440B9B88E22A4ABEF89F9F1F81BC29E94A74D9@FMSMSX106.amr.corp.intel.com> (raw)
Message-ID: <20191121235605.4pl2v-roxV5AIzz4eRM6NA_Adb_79Ob23RtGu0K2KNk@z> (raw)
In-Reply-To: <157437988036.2524.15103838845430811433@skylake-alporthouse-com>
> -----Original Message-----
> From: Chris Wilson <chris@chris-wilson.co.uk>
> Sent: Thursday, November 21, 2019 3:45 PM
> To: Tang, CQ <cq.tang@intel.com>; intel-gfx@lists.freedesktop.org
> Cc: igt-dev@lists.freedesktop.org
> Subject: RE: [Intel-gfx] [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check
> engine relative registers
>
> Quoting Tang, CQ (2019-11-21 21:07:13)
> >
> >
> > > -----Original Message-----
> > > From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf
> > > Of Chris Wilson
> > > Sent: Wednesday, November 13, 2019 4:53 AM
> > > To: intel-gfx@lists.freedesktop.org
> > > Cc: igt-dev@lists.freedesktop.org
> > > Subject: [Intel-gfx] [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check
> > > engine @@ -248,6 +238,7 @@ static void tmpl_regs(int fd, {
> > > const unsigned int gen_bit = 1 <<
> > > intel_gen(intel_get_drm_devid(fd));
> > > const unsigned int engine_bit = ENGINE(e->class, e->instance);
> > > + const uint32_t mmio_base = gem_engine_mmio_base(fd, e->name);
> >
> > Chris, I tried to test this patch, but "gem_engine_mmio_base()" above is
> not defined.
> > Can you check?
>
> Did you perchance look at patch 4?
Thanks, find this one:
[i-g-t,4/9] i915: Start putting the mmio_base to wider use
--CQ
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: "Tang, CQ" <cq.tang@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check engine relative registers
Date: Thu, 21 Nov 2019 23:56:05 +0000 [thread overview]
Message-ID: <1D440B9B88E22A4ABEF89F9F1F81BC29E94A74D9@FMSMSX106.amr.corp.intel.com> (raw)
In-Reply-To: <157437988036.2524.15103838845430811433@skylake-alporthouse-com>
> -----Original Message-----
> From: Chris Wilson <chris@chris-wilson.co.uk>
> Sent: Thursday, November 21, 2019 3:45 PM
> To: Tang, CQ <cq.tang@intel.com>; intel-gfx@lists.freedesktop.org
> Cc: igt-dev@lists.freedesktop.org
> Subject: RE: [Intel-gfx] [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check
> engine relative registers
>
> Quoting Tang, CQ (2019-11-21 21:07:13)
> >
> >
> > > -----Original Message-----
> > > From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf
> > > Of Chris Wilson
> > > Sent: Wednesday, November 13, 2019 4:53 AM
> > > To: intel-gfx@lists.freedesktop.org
> > > Cc: igt-dev@lists.freedesktop.org
> > > Subject: [Intel-gfx] [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check
> > > engine @@ -248,6 +238,7 @@ static void tmpl_regs(int fd, {
> > > const unsigned int gen_bit = 1 <<
> > > intel_gen(intel_get_drm_devid(fd));
> > > const unsigned int engine_bit = ENGINE(e->class, e->instance);
> > > + const uint32_t mmio_base = gem_engine_mmio_base(fd, e->name);
> >
> > Chris, I tried to test this patch, but "gem_engine_mmio_base()" above is
> not defined.
> > Can you check?
>
> Did you perchance look at patch 4?
Thanks, find this one:
[i-g-t,4/9] i915: Start putting the mmio_base to wider use
--CQ
> -Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-11-21 23:56 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 12:52 [PATCH i-g-t 1/9] i915/gem_exec_schedule: Split pi-ringfull into two tests Chris Wilson
2019-11-13 12:52 ` [Intel-gfx] " Chris Wilson
2019-11-13 12:52 ` [PATCH i-g-t 2/9] i915/gem_exec_schedule: Exercise priority inversion from resource contention Chris Wilson
2019-11-13 12:52 ` [igt-dev] " Chris Wilson
2019-11-13 12:52 ` [Intel-gfx] " Chris Wilson
2019-11-13 12:52 ` [PATCH i-g-t 3/9] i915/gem_exec_schedule: Beware priority inversion from iova faults Chris Wilson
2019-11-13 12:52 ` [igt-dev] " Chris Wilson
2019-11-13 12:52 ` [Intel-gfx] " Chris Wilson
2019-11-13 12:52 ` [PATCH i-g-t 4/9] i915: Start putting the mmio_base to wider use Chris Wilson
2019-11-13 12:52 ` [igt-dev] " Chris Wilson
2019-11-13 12:52 ` [Intel-gfx] " Chris Wilson
2019-11-21 12:04 ` [igt-dev] " Lionel Landwerlin
2019-11-21 12:04 ` Lionel Landwerlin
2019-11-21 12:04 ` [Intel-gfx] " Lionel Landwerlin
2019-11-21 12:11 ` Chris Wilson
2019-11-21 12:11 ` Chris Wilson
2019-11-21 12:11 ` [Intel-gfx] " Chris Wilson
2019-11-21 13:11 ` Lionel Landwerlin
2019-11-21 13:11 ` Lionel Landwerlin
2019-11-21 13:11 ` [Intel-gfx] " Lionel Landwerlin
2019-11-13 12:52 ` [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check engine relative registers Chris Wilson
2019-11-13 12:52 ` [Intel-gfx] " Chris Wilson
2019-11-21 21:07 ` Tang, CQ
2019-11-21 21:07 ` [igt-dev] [Intel-gfx] " Tang, CQ
2019-11-21 21:07 ` Tang, CQ
2019-11-21 23:44 ` Chris Wilson
2019-11-21 23:44 ` [igt-dev] [Intel-gfx] " Chris Wilson
2019-11-21 23:44 ` Chris Wilson
2019-11-21 23:56 ` Tang, CQ [this message]
2019-11-21 23:56 ` [igt-dev] " Tang, CQ
2019-11-21 23:56 ` Tang, CQ
2019-11-25 19:13 ` Tang, CQ
2019-11-25 19:13 ` [Intel-gfx] " Tang, CQ
2019-11-13 12:52 ` [PATCH i-g-t 6/9] i915: Exercise preemption timeout controls in sysfs Chris Wilson
2019-11-13 12:52 ` [Intel-gfx] " Chris Wilson
2019-11-13 12:52 ` [PATCH i-g-t 7/9] i915: Exercise sysfs heartbeat controls Chris Wilson
2019-11-13 12:52 ` [igt-dev] " Chris Wilson
2019-11-13 12:52 ` [Intel-gfx] " Chris Wilson
2019-11-13 12:52 ` [PATCH i-g-t 8/9] i915: Exercise timeslice sysfs property Chris Wilson
2019-11-13 12:52 ` [igt-dev] " Chris Wilson
2019-11-13 12:52 ` [Intel-gfx] " Chris Wilson
2019-11-13 12:52 ` [PATCH i-g-t 9/9] i915: Exercise I915_CONTEXT_PARAM_RINGSIZE Chris Wilson
2019-11-13 12:52 ` [igt-dev] " Chris Wilson
2019-11-13 12:52 ` [Intel-gfx] " Chris Wilson
2019-12-02 14:42 ` [igt-dev] " Janusz Krzysztofik
2019-12-02 14:42 ` Janusz Krzysztofik
2019-12-02 14:42 ` [Intel-gfx] " Janusz Krzysztofik
2019-12-02 14:59 ` Chris Wilson
2019-12-02 14:59 ` Chris Wilson
2019-12-02 14:59 ` [Intel-gfx] " Chris Wilson
2020-02-20 15:57 ` Janusz Krzysztofik
2020-02-20 15:57 ` Janusz Krzysztofik
2020-02-20 16:00 ` [Intel-gfx] " Chris Wilson
2020-02-20 16:00 ` Chris Wilson
2019-11-13 14:30 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/9] i915/gem_exec_schedule: Split pi-ringfull into two tests Patchwork
2019-11-13 14:40 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
2019-11-14 2:10 ` [igt-dev] ✓ Fi.CI.IGT: success " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-10-24 10:54 [PATCH i-g-t 1/9] i915_drm.h sync Chris Wilson
2019-10-24 10:54 ` [PATCH i-g-t 5/9] i915/gem_ctx_isolation: Check engine relative registers 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=1D440B9B88E22A4ABEF89F9F1F81BC29E94A74D9@FMSMSX106.amr.corp.intel.com \
--to=cq.tang@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.