From: Christoph Hellwig <hch@infradead.org>
To: Rodrigo Vivi <rodrigo.vivi@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: Wed, 21 Jul 2021 16:43:32 +0100 [thread overview]
Message-ID: <YPhApJo1o6yBYUh2@infradead.org> (raw)
In-Reply-To: <YPgD/8Y3/te/Hsu3@intel.com>
On Wed, Jul 21, 2021 at 07:24:47AM -0400, Rodrigo Vivi wrote:
> On Wed, Jul 21, 2021 at 01:10:49PM +0200, Christoph Hellwig wrote:
> > Hi all,
> >
> > 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.
_______________________________________________
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 15:48 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 [this message]
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
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=YPhApJo1o6yBYUh2@infradead.org \
--to=hch@infradead.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-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 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).