From: Jani Nikula <jani.nikula@linux.intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, chris@chris-wilson.co.uk
Subject: Re: [Intel-gfx] [PATCH v4] drm/i915: Try to guess PCH type even without ISA bridge
Date: Mon, 18 Jan 2021 11:56:53 +0200 [thread overview]
Message-ID: <87im7uo9ei.fsf@intel.com> (raw)
In-Reply-To: <20210118060406.GA15982@zhen-hp.sh.intel.com>
On Mon, 18 Jan 2021, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
> On 2021.01.15 13:01:49 +0200, Joonas Lahtinen wrote:
>> Quoting Jani Nikula (2021-01-15 12:50:54)
>> > On Thu, 14 Jan 2021, Zhenyu Wang <zhenyuw@linux.intel.com> wrote:
>> > > On 2021.01.14 08:58:19 +0800, Xiong Zhang wrote:
>> > >> From: Zhenyu Wang <zhenyuw@linux.intel.com>
>> > >>
>> > >> Some vmm like hyperv and crosvm don't supply any ISA bridge to their guest,
>> > >> when igd passthrough is equipped on these vmm, guest i915 display may
>> > >> couldn't work as guest i915 detects PCH_NONE pch type.
>> > >>
>> > >> When i915 runs as guest, this patch guess pch type through gpu type even
>> > >> without ISA bridge.
>> > >>
>> > >> v2: Fix CI warning
>> > >> v3: Add HAS_DISPLAY()= true condition beforce guessing virt pch, then
>> > >> refactori.
>> > >> v4: Fix CI warning
>> > >>
>> > >> Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
>> > >> Signed-off-by: Xiong Zhang <xiong.y.zhang@intel.com>
>> > >> ---
>> > >> drivers/gpu/drm/i915/i915_drv.h | 7 +++++-
>> > >> drivers/gpu/drm/i915/intel_pch.c | 39 ++++++++++++++++++--------------
>> > >> 2 files changed, 28 insertions(+), 18 deletions(-)
>> > >>
>> > >
>> > > Good to me, thanks! I think this should change author to you. :)
>> > >
>> > > Reviewed-by: Zhenyu Wang <zhenyuw@linux.intel.com>
>> >
>> > Pushed to drm-intel-next, thanks for the patch and review. I ended up
>> > retaining Zhenyu's authorship, and added
>> >
>> > Co-developed-by: Xiong Zhang <xiong.y.zhang@intel.com>
>>
>> This only works for the majority of SKUs which happen to use the PCH
>> that is most common. I NAKed very similar patch some years back asking
>> for a reliable means to detect the PCH type instead.
>>
>> Has there been any attempt to introduce such mechanism?
>>
>
> I think the situation is that if just passing through GPU device, as
> full device model depends on userspace VMM, we have no way to properly
> detect PCH type from device, e.g in case of one GEN device which could
> live with two or more different PCH types. It's better if either we
> have properly defined way to detect through GPU device or display arch
> always defines CPU/PCH display in pair.
>
> Currently this tries to assume PCH with best effort that fixed bunch of
> problems. On really mismatch case, how about adding i915 parameter to
> override PCH type? As that won't add dependency on other components..
In general, module parameters should not be considered a fix or a
solution.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-01-18 9:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 7:01 [Intel-gfx] [PATCH] drm/i915: Try to guess PCH type even without ISA bridge Xiong Zhang
2020-12-14 7:17 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-12-14 7:19 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-12-18 9:05 ` [Intel-gfx] [PATCH v2] " Xiong Zhang
2020-12-22 5:15 ` Zhenyu Wang
2020-12-23 8:39 ` Zhang, Xiong Y
2020-12-23 8:59 ` Jani Nikula
2020-12-24 2:42 ` Zhang, Xiong Y
2020-12-24 2:54 ` Zhang, Xiong Y
2020-12-24 4:49 ` Zhenyu Wang
2021-01-13 4:53 ` [Intel-gfx] [PATCH v3] " Xiong Zhang
2021-01-14 0:58 ` [Intel-gfx] [PATCH v4] " Xiong Zhang
2021-01-14 5:14 ` Zhenyu Wang
2021-01-15 10:50 ` Jani Nikula
2021-01-15 11:01 ` Joonas Lahtinen
2021-01-18 6:04 ` Zhenyu Wang
2021-01-18 9:56 ` Jani Nikula [this message]
2020-12-18 10:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Try to guess PCH type even without ISA bridge (rev2) Patchwork
2020-12-18 11:27 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-01-13 5:23 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Try to guess PCH type even without ISA bridge (rev3) Patchwork
2021-01-13 5:52 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-01-14 2:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Try to guess PCH type even without ISA bridge (rev4) Patchwork
2021-01-14 4:59 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-12-14 7:22 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915: Try to guess PCH type even without ISA bridge Patchwork
2020-12-14 7:47 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-12-14 9:25 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-12-14 10:10 ` [Intel-gfx] [PATCH] " kernel test robot
2020-12-14 10:10 ` [Intel-gfx] [RFC PATCH] drm/i915: intel_detect_pch_virt() can be static kernel test robot
2020-12-14 12:50 ` [Intel-gfx] [PATCH] drm/i915: Try to guess PCH type even without ISA bridge kernel test robot
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=87im7uo9ei.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=zhenyuw@linux.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