From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org
Subject: Re: [Intel-gfx] 5.14-rc2 warnings with kvmgvt
Date: Wed, 21 Jul 2021 17:18:18 -0400 [thread overview]
Message-ID: <YPiPGv/wtnjsxSZy@intel.com> (raw)
In-Reply-To: <YPiGI9tzLzGZg47j@infradead.org>
On Wed, Jul 21, 2021 at 09:40:03PM +0100, Christoph Hellwig wrote:
> On Wed, Jul 21, 2021 at 04:43:44PM +0100, Christoph Hellwig wrote:
> > > > I'm trying to test some changes for the gvt code, but even with a baseline
> > > > 5.14-rc2 host and guest the 915 driver does not seem overly happy:
> > >
> > > Is this a regression over -rc1 or over 5.13?
> > > Bisect possible?
> >
> > This was introduced somewhere between 5.12 and 5.13, still bisecting.
> > Note that it only happens for "headless" setups. Once a display is
> > added on the qemu command line it goes away.
>
> The culprit is:
>
> commit f4eb6d4906669b4285c4f49c87814d4ce63c35bb
> Author: Jani Nikula <jani.nikula@intel.com>
> Date: Wed Mar 17 18:36:45 2021 +0200
>
> drm/i915/bios: limit default outputs to ports A through F
>
could you please try this small patch?
diff --git a/drivers/gpu/drm/i915/display/intel_bios.c b/drivers/gpu/drm/i915/display/intel_bios.c
index 5b6922e28ef2..8bbeb5978bf7 100644
--- a/drivers/gpu/drm/i915/display/intel_bios.c
+++ b/drivers/gpu/drm/i915/display/intel_bios.c
@@ -2166,7 +2166,8 @@ static void
init_vbt_missing_defaults(struct drm_i915_private *i915)
{
enum port port;
- int ports = PORT_A | PORT_B | PORT_C | PORT_D | PORT_E | PORT_F;
+ int ports = BIT(PORT_A) | BIT(PORT_B) | BIT(PORT_C) | \
+ BIT(PORT_D) | BIT(PORT_E) | BIT(PORT_F);
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-07-21 21:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 11:10 [Intel-gfx] 5.14-rc2 warnings with kvmgvt Christoph Hellwig
2021-07-21 11:24 ` Rodrigo Vivi
2021-07-21 15:43 ` Christoph Hellwig
2021-07-21 20:40 ` Christoph Hellwig
2021-07-21 21:18 ` Rodrigo Vivi [this message]
2021-07-22 4:24 ` Christoph Hellwig
2021-07-22 5:55 ` Lucas De Marchi
2021-07-22 7:20 ` Christoph Hellwig
2021-07-22 16:03 ` Lucas De Marchi
2021-07-22 16:08 ` Christoph Hellwig
2021-07-21 21:47 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
2021-07-22 5:05 ` [Intel-gfx] " Zhenyu Wang
2021-07-22 5:52 ` Christoph Hellwig
2021-07-22 6:34 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for 5.14-rc2 warnings with kvmgvt (rev2) 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=YPiPGv/wtnjsxSZy@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=hch@infradead.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
/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).