From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Steve Hampson <steven.t.hampson@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v2] tests/i915/gem_ctx_isolation.c : Increase MAX_REG
Date: Mon, 5 Dec 2022 15:13:03 +0100 [thread overview]
Message-ID: <Y438b77Tj0qdmec/@kamilkon-desk1> (raw)
In-Reply-To: <20221201053226.629748-1-vikas.srivastava@intel.com>
Hi,
On 2022-12-01 at 11:02:26 +0530, Vikas Srivastava wrote:
> From: Steve Hampson <steven.t.hampson@intel.com>
>
> Increase MAX_REG from 0x200000 to 0x400000 to support new large MMIO
> base addresses such as to support GEN12+ platform base addresses.
While it is ok for gen12+ this imho should be platform dependent
as now we will allow bigger regs for older platforms. It may be
something worth to fix in future, as of now
Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Small nit - do not put space "tests/i915/gem_ctx_isolation.c :"
and also cut off ".c", so it will look like:
tests/i915/gem_ctx_isolation: Increase MAX_REG
btw no need to resend this,
Regards,
Kamil
>
> Signed-off-by: Steve Hampson <steven.t.hampson@intel.com>
> Acked-by: Priyanka Dandamudi <priyanka.dandamudi@intel.com>
> ---
> tests/i915/gem_ctx_isolation.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tests/i915/gem_ctx_isolation.c b/tests/i915/gem_ctx_isolation.c
> index dc52a9a03..ec6935714 100644
> --- a/tests/i915/gem_ctx_isolation.c
> +++ b/tests/i915/gem_ctx_isolation.c
> @@ -27,7 +27,8 @@
> #include "igt_dummyload.h"
> #include "igt_types.h"
>
> -#define MAX_REG 0x200000
> +/* MAX_REG must be greater than the maximum register address. */
> +#define MAX_REG 0x400000
> #define NUM_REGS (MAX_REG / sizeof(uint32_t))
>
> #define PAGE_ALIGN(x) ALIGN(x, 4096)
> --
> 2.25.1
>
prev parent reply other threads:[~2022-12-05 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 5:32 [igt-dev] [PATCH i-g-t v2] tests/i915/gem_ctx_isolation.c : Increase MAX_REG Vikas Srivastava
2022-12-01 6:24 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/i915/gem_ctx_isolation.c : Increase MAX_REG (rev2) Patchwork
2022-12-02 7:13 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2022-12-02 21:58 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2022-12-05 12:29 ` [igt-dev] [PATCH i-g-t v2] tests/i915/gem_ctx_isolation.c : Increase MAX_REG Kumar, Sinjan
2022-12-05 12:51 ` [igt-dev] ✓ Fi.CI.IGT: success for tests/i915/gem_ctx_isolation.c : Increase MAX_REG (rev2) Patchwork
2022-12-05 14:13 ` Kamil Konieczny [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=Y438b77Tj0qdmec/@kamilkon-desk1 \
--to=kamil.konieczny@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=steven.t.hampson@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