From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Remove nonpriv flags when srm/lrm
Date: Thu, 24 Oct 2019 18:23:01 +0300 [thread overview]
Message-ID: <ecc5965d-71d8-c716-253e-dd54d7a06e18@intel.com> (raw)
In-Reply-To: <157191707108.2725.12035547014609265414@skylake-alporthouse-com>
On 24/10/2019 14:37, Chris Wilson wrote:
> Quoting Mika Kuoppala (2019-10-24 12:03:31)
>> On testing the whitelists, using any of the nonpriv
>> flags when trying to access the register offset will lead
>> to failure.
>>
>> Define address mask to get the mmio offset in order
>> to guard against any current and future flag usage.
>>
>> v2: apply also on scrub_whitelisted_registers (Lionel)
>>
>> Cc: Tapani Pälli <tapani.palli@intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>> Signed-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris
>
Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
_______________________________________________
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: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915: Remove nonpriv flags when srm/lrm
Date: Thu, 24 Oct 2019 18:23:01 +0300 [thread overview]
Message-ID: <ecc5965d-71d8-c716-253e-dd54d7a06e18@intel.com> (raw)
Message-ID: <20191024152301.oVDVnxrFBDVcA36Dd_vdP1Cr5qX5vVDAbn10SOL2xHA@z> (raw)
In-Reply-To: <157191707108.2725.12035547014609265414@skylake-alporthouse-com>
On 24/10/2019 14:37, Chris Wilson wrote:
> Quoting Mika Kuoppala (2019-10-24 12:03:31)
>> On testing the whitelists, using any of the nonpriv
>> flags when trying to access the register offset will lead
>> to failure.
>>
>> Define address mask to get the mmio offset in order
>> to guard against any current and future flag usage.
>>
>> v2: apply also on scrub_whitelisted_registers (Lionel)
>>
>> Cc: Tapani Pälli <tapani.palli@intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>> Signed-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris
>
Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-10-24 15:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 10:38 [PATCH 1/2] drm/i915: Remove nonpriv flags when srm/lrm Mika Kuoppala
2019-10-24 10:38 ` [Intel-gfx] " Mika Kuoppala
2019-10-24 10:38 ` [PATCH 2/2] drm/i915/tgl: whitelist PS_(DEPTH|INVOCATION)_COUNT Mika Kuoppala
2019-10-24 10:38 ` [Intel-gfx] " Mika Kuoppala
2019-10-24 10:52 ` [PATCH 1/2] drm/i915: Remove nonpriv flags when srm/lrm Lionel Landwerlin
2019-10-24 10:52 ` [Intel-gfx] " Lionel Landwerlin
2019-10-24 11:03 ` Mika Kuoppala
2019-10-24 11:03 ` [Intel-gfx] " Mika Kuoppala
2019-10-24 11:37 ` Chris Wilson
2019-10-24 11:37 ` [Intel-gfx] " Chris Wilson
2019-10-24 15:23 ` Lionel Landwerlin [this message]
2019-10-24 15:23 ` Lionel Landwerlin
2019-10-24 22:36 ` Chris Wilson
2019-10-24 22:36 ` [Intel-gfx] " Chris Wilson
2019-10-24 15:29 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915: Remove nonpriv flags when srm/lrm (rev2) Patchwork
2019-10-24 15:29 ` [Intel-gfx] " Patchwork
2019-10-24 15:58 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-24 15:58 ` [Intel-gfx] " Patchwork
2019-10-25 23:17 ` ✓ Fi.CI.IGT: " Patchwork
2019-10-25 23:17 ` [Intel-gfx] " Patchwork
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=ecc5965d-71d8-c716-253e-dd54d7a06e18@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox