From: "Souza, Jose" <jose.souza@intel.com>
To: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Cc: "Pandey, Hariom" <hariom.pandey@intel.com>,
"Ausmus, James" <james.ausmus@intel.com>,
"Nikula, Jani" <jani.nikula@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"K, SrinivasX" <srinivasx.k@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Surendrakumar Upadhyay,
TejaskumarX" <tejaskumarx.surendrakumar.upadhyay@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/ehl: Remove require_force_probe protection
Date: Tue, 6 Oct 2020 18:02:46 +0000 [thread overview]
Message-ID: <c88bc0fbc4956395324674ca202b395326208888.camel@intel.com> (raw)
In-Reply-To: <3CDB63EE-D1CD-43E4-A977-4E966CD19313@intel.com>
On Tue, 2020-10-06 at 10:55 -0700, Vivi, Rodrigo wrote:
>
> > On Oct 6, 2020, at 10:48 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> >
> > Quoting Souza, Jose (2020-10-06 18:46:45)
> > > +Rodrigo and Jani
> > >
> > > On Tue, 2020-10-06 at 14:56 +0000, Kamati Srinivas wrote:
> > > > Removing force probe protection from EHL platform. Did
> > > > not observe warnings, errors, flickering or any visual
> > > > defects while doing ordinary tasks like browsing and
> > > > editing documents in a two monitor setup.
> > >
> > > One of the requirements was also to have CI BAT all green and shards as green is possible but EHL don't show up in CI results, we actually have one
> > > single EHL machine in CI but I guess it is not able to run all tests that shards do:
> > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9097/filelist.html
> >
> > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip-alt.html
>
> we are really close to that point. We just need to fix some w/a and rc6 issues
> before applying this change.
>
> > -Chris
>
Huum okay we have drm-tip results for EHL but if someone sends a patch that breaks EHL it will not be caught in pre-merge testing.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-10-06 18:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 14:56 [PATCH] drm/i915/ehl: Remove require_force_probe protection Kamati Srinivas
2020-10-06 17:46 ` [Intel-gfx] " Souza, Jose
2020-10-06 17:48 ` Chris Wilson
2020-10-06 17:55 ` Vivi, Rodrigo
2020-10-06 18:02 ` Souza, Jose [this message]
2020-10-09 8:31 ` K, SrinivasX
2020-10-09 13:38 ` Vivi, Rodrigo
2020-10-09 18:08 ` Pandey, Hariom
2020-10-15 8:41 ` K, SrinivasX
2020-10-19 18:29 ` Rodrigo Vivi
2020-10-19 18:33 ` Chris Wilson
[not found] ` <CO1PR11MB50750A169A14FCC84C70C936F61F0@CO1PR11MB5075.namprd11.prod.outlook.com>
[not found] ` <CO1PR11MB5075AAFA3500F4A3A610FC52F6170@CO1PR11MB5075.namprd11.prod.outlook.com>
2020-10-28 11:53 ` Vivi, Rodrigo
2020-10-28 11:55 ` Pandey, Hariom
2020-11-27 20:36 ` 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=c88bc0fbc4956395324674ca202b395326208888.camel@intel.com \
--to=jose.souza@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=hariom.pandey@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=james.ausmus@intel.com \
--cc=jani.nikula@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=srinivasx.k@intel.com \
--cc=tejaskumarx.surendrakumar.upadhyay@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;
as well as URLs for NNTP newsgroup(s).