intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	intel-gfx@lists.freedesktop.org,
	intel-gvt-dev@lists.freedesktop.org
Subject: Re: [Intel-gfx] 5.14-rc2 warnings with kvmgvt
Date: Thu, 22 Jul 2021 08:20:34 +0100	[thread overview]
Message-ID: <YPkcQqnRGZABpmce@infradead.org> (raw)
In-Reply-To: <20210722055523.e5tdgcledznyzmxt@ldmartin-desk2>

On Thu, Jul 22, 2021 at 01:55:23AM -0400, Lucas De Marchi wrote:
> humn... PORT_F. KBL doesn't have PORT_F. We decided to keep the handling
> of DISPLAY_VER == 10 and DISPLAY_VER == 9 together and trust the VBT,
> but when the VBT is not present, DDI F will get added unconditio.
> 
> maybe best thing to do is to split that

With this and the previous patch the stack traces are gone.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2021-07-22  7:21 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
2021-07-22  4:24         ` Christoph Hellwig
2021-07-22  5:55           ` Lucas De Marchi
2021-07-22  7:20             ` Christoph Hellwig [this message]
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=YPkcQqnRGZABpmce@infradead.org \
    --to=hch@infradead.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=lucas.demarchi@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).