From: "Lis, Tomasz" <tomasz.lis@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
"Kumar Valsan, Prathap" <prathap.kumar.valsan@intel.com>
Cc: igt-dev@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v2] i915/gem_mocs_settings: Add mocs table for icelake
Date: Mon, 25 Feb 2019 14:17:00 +0100 [thread overview]
Message-ID: <84f4e5e9-1c3f-0f7f-a7d3-5a69e8bcb3f8@intel.com> (raw)
In-Reply-To: <155087208515.3867.11044853795144124216@skylake-alporthouse-com>
On 2019-02-22 22:48, Chris Wilson wrote:
> Quoting Kumar Valsan, Prathap (2019-02-22 21:32:55)
>> On Fri, Feb 22, 2019 at 03:21:18PM +0000, Chris Wilson wrote:
>>> Quoting Lis, Tomasz (2019-02-22 15:17:34)
>>>>
>>>> On 2019-02-22 15:17, Prathap Kumar Valsan wrote:
>>>>> From: "Kumar Valsan, Prathap" <prathap.kumar.valsan@intel.com>
>>>>>
>>>>> This patch adds mocs table for icelake with expected L3 and eDRAM
>>>>> control values.
>>>>>
>>>>> Signed-off-by: Kumar Valsan, Prathap <prathap.kumar.valsan@intel.com>
>>>>> ---
>>>>> Changes in v2:
>>>>> - Cleaned up the code based on review comments from Lucas and Chris
>>>>> tests/i915/gem_mocs_settings.c | 96 ++++++++++++++++++++++++++--------
>>>>> 1 file changed, 73 insertions(+), 23 deletions(-)
>>>>>
>>>>> diff --git a/tests/i915/gem_mocs_settings.c b/tests/i915/gem_mocs_settings.c
>>>>> index 5b3b6bc1..6d111076 100644
>>>>> --- a/tests/i915/gem_mocs_settings.c
>>>>> +++ b/tests/i915/gem_mocs_settings.c
>>>>> @@ -33,6 +33,9 @@
>>>>> #include "igt_sysfs.h"
>>>>>
>>>>> #define MAX_NUMBER_MOCS_REGISTERS (64)
>>>>> +#define GEN9_NUM_MOCS_ENTRIES 62 /* 62 out of 64 - 63 & 64 are reserved. */
>>>>> +#define GEN11_NUM_MOCS_ENTRIES 64 /* 63-64 are reserved, but configured. */
>>>>> +
>>>>> enum {
>>>>> NONE,
>>>>> RESET,
>>>>> @@ -72,36 +75,66 @@ struct mocs_table {
>>>>> const struct mocs_entry *table;
>>>>> };
>>>>>
>>>>> +static const struct mocs_entry icelake_mocs_pte = {0x00000004, 0x0030};
>>>>> +static const struct mocs_entry mocs_pte = {0x00000038, 0x0030};
>>>>> +
>>>>> /* The first entries in the MOCS tables are defined by uABI */
>>>>> -static const struct mocs_entry skylake_mocs_table[] = {
>>>>> - { 0x00000009, 0x0010 },
>>>>> - { 0x00000038, 0x0030 },
>>>>> - { 0x0000003b, 0x0030 },
>>>>> +static const struct mocs_entry icelake_mocs_table[GEN11_NUM_MOCS_ENTRIES] = {
>>>>> + [0 ... GEN11_NUM_MOCS_ENTRIES - 1] = icelake_mocs_pte,
>>>>> + [0] = { 0x00000005, 0x0010},
>>>>> + [1] = { 0x00000004, 0x0030},
>>>>> + [2] = { 0x00000037, 0x0030},
>>>>> + [3] = { 0x00000005, 0x0010},
>>>>> + [4] = { 0x00000005, 0x0030},
>>>>> + [5] = { 0x00000037, 0x0010},
>>>>> + [6] = { 0x00000017, 0x0010},
>>>>> + [7] = { 0x00000017, 0x0030},
>>>>> + [8] = { 0x00000027, 0x0010},
>>>>> + [9] = { 0x00000027, 0x0030},
>>>>> + [10] = { 0x00000077, 0x0010},
>>>>> + [11] = { 0x00000077, 0x0030},
>>>>> + [12] = { 0x00000057, 0x0010},
>>>>> + [13] = { 0x00000057, 0x0030},
>>>>> + [14] = { 0x00000067, 0x0010},
>>>>> + [15] = { 0x00000067, 0x0030},
>>>>> + [18] = { 0x00060037, 0x0030},
>>>>> + [19] = { 0x00000737, 0x0030},
>>>>> + [20] = { 0x00000337, 0x0030},
>>>>> + [21] = { 0x00000137, 0x0030},
>>>>> + [22] = { 0x000003b7, 0x0030},
>>>>> + [23] = { 0x000007b7, 0x0030},
>>>>> + [62] = { 0x00000037, 0x0010},
>>>>> + [63] = { 0x00000037, 0x0010},
>>>>> +};
>>>>> +
>>>>> +static const struct mocs_entry dirty_icelake_mocs_table[GEN11_NUM_MOCS_ENTRIES] = {
>>>>> + [0 ... GEN11_NUM_MOCS_ENTRIES - 1] = { 0x0007FFFF, 0x003F },
>>>>> };
>>>>>
>>>>> -static const struct mocs_entry dirty_skylake_mocs_table[] = {
>>>>> - { 0x00003FFF, 0x003F }, /* no snoop bit */
>>>>> - { 0x00003FFF, 0x003F },
>>>>> - { 0x00003FFF, 0x003F },
>>>>> +static const struct mocs_entry skylake_mocs_table[GEN9_NUM_MOCS_ENTRIES] = {
>>>>> + [0 ... GEN9_NUM_MOCS_ENTRIES - 1] = mocs_pte,
>>>>> + [0] = { 0x00000009, 0x0010},
>>>>> + [1] = { 0x00000038, 0x0030},
>>>>> + [2] = { 0x0000003b, 0x0030},
>>>>> };
>>>>>
>>>>> -static const struct mocs_entry broxton_mocs_table[] = {
>>>>> - { 0x00000009, 0x0010 },
>>>>> - { 0x00000038, 0x0030 },
>>>>> - { 0x00000039, 0x0030 },
>>>>> +static const struct mocs_entry dirty_skylake_mocs_table[GEN9_NUM_MOCS_ENTRIES] = {
>>>>> + [0 ... GEN9_NUM_MOCS_ENTRIES - 1] = { 0x00003FFF, 0x003F },
>>>>> };
>>>>>
>>>>> -static const struct mocs_entry dirty_broxton_mocs_table[] = {
>>>>> - { 0x00007FFF, 0x003F },
>>>>> - { 0x00007FFF, 0x003F },
>>>>> - { 0x00007FFF, 0x003F },
>>>>> +static const struct mocs_entry broxton_mocs_table[GEN9_NUM_MOCS_ENTRIES] = {
>>>>> + [0 ... GEN9_NUM_MOCS_ENTRIES - 1] = mocs_pte,
>>>>> + [0] = { 0x00000009, 0x0010},
>>>>> + [1] = { 0x00000038, 0x0030},
>>>>> + [2] = { 0x00000039, 0x0030},
>>>>> };
>>>>>
>>>>> -static const uint32_t write_values[] = {
>>>>> - 0xFFFFFFFF,
>>>>> - 0xFFFFFFFF,
>>>>> - 0xFFFFFFFF,
>>>>> - 0xFFFFFFFF
>>>>> +static const struct mocs_entry dirty_broxton_mocs_table[GEN9_NUM_MOCS_ENTRIES] = {
>>>>> + [0 ... GEN9_NUM_MOCS_ENTRIES - 1] = { 0x00007FFF, 0x003F },
>>>>> +};
>>>>> +
>>>>> +static const uint32_t write_values[MAX_NUMBER_MOCS_REGISTERS] = {
>>>>> + [0 ... MAX_NUMBER_MOCS_REGISTERS - 1] = 0xFFFFFFFF,
>>>>> };
>>>>>
>>>>> static bool get_mocs_settings(int fd, struct mocs_table *table, bool dirty)
>>>>> @@ -127,6 +160,15 @@ static bool get_mocs_settings(int fd, struct mocs_table *table, bool dirty)
>>>>> table->table = broxton_mocs_table;
>>>>> }
>>>>> result = true;
>>>>> + } else if (IS_ICELAKE(devid)) {
>>>>> + if (dirty) {
>>>>> + table->size = ARRAY_SIZE(dirty_icelake_mocs_table);
>>>>> + table->table = dirty_icelake_mocs_table;
>>>>> + } else {
>>>>> + table->size = ARRAY_SIZE(icelake_mocs_table);
>>>>> + table->table = icelake_mocs_table;
>>>>> + }
>>>>> + result = true;
>>>>> }
>>>>>
>>>>> return result;
>>>>> @@ -374,13 +416,21 @@ static void check_mocs_values(int fd, unsigned engine, uint32_t ctx_id, bool dir
>>>>>
>>>>> static void write_dirty_mocs(int fd, unsigned engine, uint32_t ctx_id)
>>>>> {
>>>>> + uint32_t devid = intel_get_drm_devid(fd);
>>>>> + int num_of_mocs_entries;
>>>>> +
>>>>> + if (IS_ICELAKE(devid))
>>>>> + num_of_mocs_entries = GEN11_NUM_MOCS_ENTRIES;
>>>>> + else
>>>>> + num_of_mocs_entries = GEN9_NUM_MOCS_ENTRIES;
>>>>> +
>>>>> write_registers(fd, ctx_id, get_engine_base(engine),
>>>>> - write_values, ARRAY_SIZE(write_values),
>>>>> + write_values, num_of_mocs_entries,
>>>>> engine);
>>>>>
>>>>> if (engine == I915_EXEC_RENDER)
>>>>> write_registers(fd, ctx_id, GEN9_LNCFCMOCS0,
>>>>> - write_values, ARRAY_SIZE(write_values),
>>>>> + write_values, num_of_mocs_entries/2,
>>>>> engine);
>>>>> }
>>>>>
>>>> The "-dirty" subcase of the test doesn't seem suitable to current hardware..
>>>>
>>>> The table is now global. So writing it from one context and checking if
>>>> another context is unaffected is bound to fail.
>> As you pointed out On Gen11, "-dirty" subcases are failing.
>> Test is not able to write to registers.
>>> We shouldn't be able to do nonpriv writes to it then. Hopefully those
>>> writes are already being dropped?
>> So probably on latest hardware, test should still try to write and call
>> it pass if the dirty values are not being written?
> Yes, that would be useful confirmation that one context can't shoot
> another in the back, and that our global MOCS table remain invariant.
> -Chris
Don't we have a separate test for privileged registers? I'm not very
familiar with all the tests, but I remember someone told me that.
The scope of this test, as written at its beginning, is:
/** @file gem_mocs_settings.c
*
* Check that the MOCs cache settings are valid.
*/
If we already write to MOCS instead of only checking, the scope should
be expanded.
If we're going to check privileged operations, this should also be
included in the scope.
-Tomasz
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-02-25 13:17 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 21:46 [igt-dev] [PATCH i-g-t] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan via igt-dev
2019-02-15 22:48 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/gem_mocs_settings: Add mocs table for icelake (rev3) Patchwork
2019-02-16 6:07 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-02-20 8:33 ` [igt-dev] [PATCH i-g-t] i915/gem_mocs_settings: Add mocs table for icelake Szwichtenberg, Radoslaw
2019-02-21 22:48 ` Lucas De Marchi
2019-02-21 23:42 ` Chris Wilson
2019-02-22 17:49 ` Lucas De Marchi
2019-02-22 14:05 ` [igt-dev] ✗ Fi.CI.BAT: failure for i915/gem_mocs_settings: Add mocs table for icelake (rev4) Patchwork
2019-02-22 14:17 ` [igt-dev] [PATCH i-g-t v2] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan
2019-02-22 15:17 ` Lis, Tomasz
2019-02-22 15:21 ` Chris Wilson
2019-02-22 21:32 ` Kumar Valsan, Prathap
2019-02-22 21:48 ` Chris Wilson
2019-02-25 13:17 ` Lis, Tomasz [this message]
2019-02-25 0:26 ` Kumar Valsan, Prathap
2019-02-22 21:16 ` [igt-dev] ✗ Fi.CI.BAT: failure for i915/gem_mocs_settings: Add mocs table for icelake (rev5) Patchwork
2019-02-22 21:20 ` [igt-dev] [PATCH i-g-t v3] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan
2019-03-04 20:27 ` [igt-dev] [PATCH i-g-t v4] " Prathap Kumar Valsan
2019-03-04 20:37 ` Kumar Valsan, Prathap
2019-03-04 21:01 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/gem_mocs_settings: Add mocs table for icelake (rev6) Patchwork
2019-03-05 2:11 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-03-12 15:14 ` [igt-dev] [PATCH i-g-t v5] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan
2019-03-13 13:58 ` Kalamarz, Lukasz
2019-03-14 9:18 ` Chris Wilson
2019-03-14 11:03 ` Kalamarz, Lukasz
2019-03-13 12:12 ` [igt-dev] ✗ Fi.CI.BAT: failure for i915/gem_mocs_settings: Add mocs table for icelake (rev7) Patchwork
2019-03-14 0:12 ` [igt-dev] [PATCH i-g-t v5] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan
2019-03-14 0:47 ` [igt-dev] ✗ Fi.CI.BAT: failure for i915/gem_mocs_settings: Add mocs table for icelake (rev8) Patchwork
2019-03-14 17:28 ` [igt-dev] [PATCH i-g-t v6] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan
2019-03-15 8:46 ` Chris Wilson
2019-03-15 19:28 ` Kumar Valsan, Prathap
2019-03-15 21:11 ` Chris Wilson
2019-03-14 18:07 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/gem_mocs_settings: Add mocs table for icelake (rev9) Patchwork
2019-03-15 2:54 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-03-15 19:15 ` [igt-dev] [PATCH i-g-t v7] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan
2019-03-18 13:10 ` Kumar Valsan, Prathap
2019-03-18 13:06 ` Chris Wilson
2019-03-18 13:31 ` Kumar Valsan, Prathap
2019-03-18 13:27 ` Chris Wilson
2019-03-18 10:21 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/gem_mocs_settings: Add mocs table for icelake (rev11) Patchwork
2019-03-18 12:37 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-02-09 19:50 [igt-dev] [PATCH i-g-t] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan
2019-02-14 15:46 ` [igt-dev] [PATCH i-g-t v2] " Prathap Kumar Valsan via igt-dev
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=84f4e5e9-1c3f-0f7f-a7d3-5a69e8bcb3f8@intel.com \
--to=tomasz.lis@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=prathap.kumar.valsan@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