From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: allow DG1 autoprobe for CONFIG_BROKEN
Date: Mon, 14 Jun 2021 11:31:28 +0200 [thread overview]
Message-ID: <326d55b2-d7e2-8707-e1ad-85167f125193@linux.intel.com> (raw)
In-Reply-To: <20210614092227.97421-1-matthew.auld@intel.com>
On 6/14/21 11:22 AM, Matthew Auld wrote:
> Purely for CI so we can get some pre-merge results for DG1. This is
> especially useful for cross driver TTM changes where CI can hopefully
> catch regressions. This is similar to how we already handle the DG1
> specific uAPI, which are also hidden behind CONFIG_BROKEN.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Dave Airlie <airlied@gmail.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
+ CC: Christian König,
With this in place, I think The mock memory_region and hugepages
selftests will be sensitive to changes in TTM on most intel platforms,
as well as all DG1 selftests, and any passing DG1 igt tests.
/Thomas
_______________________________________________
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: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: allow DG1 autoprobe for CONFIG_BROKEN
Date: Mon, 14 Jun 2021 11:31:28 +0200 [thread overview]
Message-ID: <326d55b2-d7e2-8707-e1ad-85167f125193@linux.intel.com> (raw)
In-Reply-To: <20210614092227.97421-1-matthew.auld@intel.com>
On 6/14/21 11:22 AM, Matthew Auld wrote:
> Purely for CI so we can get some pre-merge results for DG1. This is
> especially useful for cross driver TTM changes where CI can hopefully
> catch regressions. This is similar to how we already handle the DG1
> specific uAPI, which are also hidden behind CONFIG_BROKEN.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Dave Airlie <airlied@gmail.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
+ CC: Christian König,
With this in place, I think The mock memory_region and hugepages
selftests will be sensitive to changes in TTM on most intel platforms,
as well as all DG1 selftests, and any passing DG1 igt tests.
/Thomas
next prev parent reply other threads:[~2021-06-14 9:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 9:22 [Intel-gfx] [PATCH] drm/i915: allow DG1 autoprobe for CONFIG_BROKEN Matthew Auld
2021-06-14 9:22 ` Matthew Auld
2021-06-14 9:31 ` Thomas Hellström [this message]
2021-06-14 9:31 ` Thomas Hellström
2021-06-14 9:41 ` [Intel-gfx] " Maarten Lankhorst
2021-06-14 9:41 ` Maarten Lankhorst
2021-06-14 16:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-06-14 20:14 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-06-16 14:29 ` [Intel-gfx] [PATCH] " Matthew Auld
2021-06-16 14:29 ` Matthew Auld
2021-06-17 17:20 ` [Intel-gfx] " Daniel Vetter
2021-06-17 17:20 ` Daniel Vetter
2021-06-23 13:03 ` [Intel-gfx] " Jani Nikula
2021-06-23 13:03 ` Jani Nikula
2021-06-18 19:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: allow DG1 autoprobe for CONFIG_BROKEN (rev2) Patchwork
2021-06-18 22:51 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=326d55b2-d7e2-8707-e1ad-85167f125193@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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 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.