Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	intel-xe@lists.freedesktop.org
Subject: Re: Graphical glitches (not refreshing?) with Linux's xe driver + Xen 4.19
Date: Thu, 12 Feb 2026 17:22:34 +0100	[thread overview]
Message-ID: <aY3-Shto7px4M1RK@mail-itl> (raw)
In-Reply-To: <aY387XuhCEZ0JNTN@Mac.lan>

[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]

On Thu, Feb 12, 2026 at 05:16:45PM +0100, Roger Pau Monné wrote:
> On Thu, Feb 12, 2026 at 04:32:56PM +0100, Marek Marczykowski-Górecki wrote:
> > On Thu, Feb 12, 2026 at 04:11:50PM +0100, Roger Pau Monné wrote:
> > > On Tue, Feb 10, 2026 at 07:06:20PM +0100, Marek Marczykowski-Górecki wrote:
> > > > Hi,
> > > > 
> > > > Recently I started testing compatibility with Intel Lunar Lake. This is
> > > > the first one that uses "xe" instead of "i915" Linux driver for iGPU.
> > > > I test it with Qubes OS 4.3, which uses Xen 4.19.4 and PV dom0 running
> > > > Linux 6.17.9 in this test.
> > > 
> > > Not sure it's going to help a lot, but does using a PVH dom0 make any
> > > difference?
> > 
> > Yes, it makes a difference. I end up with black screen as soon as dom0
> > starts... And due to unrelated bug (in xhci console code?), I don't have
> > kernel messages :/
> 
> Hm, that's ... very helpful.  We should fix the xhci stuff so we know
> what's going on there.  Is the xhci bug also PVH only, or PV is
> equally affected?

XHCI console works just fine with PV dom0. But I just noticed I had
older Xen binary there today, will re-test on the same 4.19.4 again. And
then will submit separate bug report (even if that's likely be me fixing
it anyway).

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2026-02-12 16:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 18:06 Graphical glitches (not refreshing?) with Linux's xe driver + Xen 4.19 Marek Marczykowski-Górecki
2026-02-12 14:33 ` Rodrigo Vivi
2026-02-12 15:11 ` Roger Pau Monné
2026-02-12 15:32   ` Marek Marczykowski-Górecki
2026-02-12 16:16     ` Roger Pau Monné
2026-02-12 16:22       ` Marek Marczykowski-Górecki [this message]
2026-02-12 16:35         ` Roger Pau Monné
2026-02-13  1:23   ` Marek Marczykowski-Górecki
     [not found]     ` <a41a15ca-b26e-482a-9084-fc61645fb24e@gmail.com>
2026-02-24 15:31       ` Marek Marczykowski-Górecki
2026-02-24 15:58     ` Marek Marczykowski-Górecki
2026-03-02 11:19       ` Marek Marczykowski-Górecki

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=aY3-Shto7px4M1RK@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.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