From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Gupta, Anshuman" <anshuman.gupta@intel.com>
Cc: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] lib/intel_device_info: Add IS_DGFX() support
Date: Sun, 24 Apr 2022 23:54:34 -0700 [thread overview]
Message-ID: <8735i1ac0l.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <1e597a2232df4c51ac6a2ac8112784bf@intel.com>
On Sun, 24 Apr 2022 23:10:23 -0700, Gupta, Anshuman wrote:
>
> > > > On Fri, 22 Apr 2022 05:59:12 -0700, Anshuman Gupta wrote:
> > > > >
> > > > > Currently IGT is lacking IS_DGFX() macro support.
> > > > > There are some power features like D3Cold are only supported on
> > > > > discrete card. So IGT test/tools specific to D3Cold requires to
> > > > > consume IS_DGFX().
> > > > > Adding a is_dgfx field in intel_device_info and initializing it
> > > > > for DG1. All future discrete platform would require to initialize
> > > > > this field.
> > > >
> > > > #define IS_DGFX(fd) gem_has_lmem(fd) ?
> > > >
> > > > gem_has_lmem() is already pretty widely used so maybe we should not
> > > > introduce another way to achieve the same goal?
> > >
> > > Before introducing this , I thought on using gem_has_lmem.
> > > But I was not sure in case every discrete platform mandatory to have lmem
> > region.
> > > If it is guaranteed that every discrete platform will have lmem memory region
> > ?
> > > I will drop this patch.
> >
> > So not sure what will happen in the future but till now and in the forseeable
> > future all dGfx platforms have LMEM, so gem_has_lmem seems fine.
> It seems better to carry with gem_has_lmem(), as IS_DGFX() requires to populate device info fields.
> This patch spined off from series https://patchwork.freedesktop.org/series/102780/
> I will use gem_has_lmem() instead of IS_DGFX().
> @rodrigo what is your opinion about it ?
> >
> > I think if we introduce IS_DGFX() as in this patch, we should have an additional
> > patch to convert all tests using gem_has_lmem() to IS_DGFX() so that we don't
> > have multiple ways of tests deciding if something should run for dGfx.
> >
> > Or maybe both are also ok? So lmem related tests should use gem_has_lmem()
> > and non LMEM related tests should use IS_DGFX()?
>
> Actually, both of these methods even are not sufficient, if needed prior
> to open the drm_fd. Ex. igt_device_find_first_i915_discrete_card()
> checks the igpu b:d:f, which breaks on one of real time issue.
> https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/94
In that case maybe such API's which attempt to do this and don't work in
*all* cases should be deleted and something new provided? Anyway this seems
to be a different issue to what we were discussing? Thanks.
>
> >
> > So if we want to merge this let's look at other tests which are presently using
> > gem_has_lmem() and see if any need to be converted over to IS_DGFX(). Or to
> > keep things simple just use gem_has_lmem() for now?
> >
> > Thanks.
next prev parent reply other threads:[~2022-04-25 6:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 12:59 [igt-dev] [PATCH i-g-t] lib/intel_device_info: Add IS_DGFX() support Anshuman Gupta
2022-04-22 14:12 ` Kamil Konieczny
2022-04-22 16:07 ` Dixit, Ashutosh
2022-04-25 5:24 ` Gupta, Anshuman
2022-04-25 5:44 ` Dixit, Ashutosh
2022-04-25 6:10 ` Gupta, Anshuman
2022-04-25 6:54 ` Dixit, Ashutosh [this message]
2022-04-25 12:58 ` Petri Latvala
2022-04-22 16:50 ` [igt-dev] ✗ GitLab.Pipeline: warning for " Patchwork
2022-04-22 17:24 ` [igt-dev] ✗ Fi.CI.BAT: failure " 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=8735i1ac0l.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=rodrigo.vivi@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.