From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Demi Marie Obenour <demi@invisiblethingslab.com>
Cc: Andrew Cooper <Andrew.Cooper3@citrix.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Jan Beulich <jbeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>, Wei Liu <wl@xen.org>,
George Dunlap <George.Dunlap@citrix.com>,
"Tim (Xen.org)" <tim@xen.org>, Juergen Gross <jgross@suse.com>
Subject: Re: [RFC PATCH 8/8] Use Linux's PAT
Date: Tue, 6 Dec 2022 19:12:06 +0100 [thread overview]
Message-ID: <Y4+F9iujzOmoOAVe@mail-itl> (raw)
In-Reply-To: <Y4+Die8lcZUwwGmK@itl-email>
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
On Tue, Dec 06, 2022 at 01:01:41PM -0500, Demi Marie Obenour wrote:
> On Tue, Dec 06, 2022 at 11:38:03AM +0000, Andrew Cooper wrote:
> > On 06/12/2022 04:33, Demi Marie Obenour wrote:
> > > This is purely for testing, to see if it works around a bug in i915. It
> > > is not intended to be merged.
> > >
> > > NOT-signed-off-by: DO NOT MERGE
> >
> > Following up on Marek's report on IRC/Matrix, you're saying that this
> > change does actually fix screen corruption issues on AlderLake, and
> > something on TigerLake too?
>
> Correct
>
> > If that is actually the case, then one of two things is happening. Either,
> >
> > 1) Drivers in Linux are bypassing the regular caching APIs, or
>
> This would not surprise me at all.
>
> > 2) The translation logic between Linux's idea of cacheability and Xen's
> > PAT values is buggy.
>
> How could I check for this?
See Andy's unit test idea on #xendevel:
as a pretty simple "unit" test in dom0, it might be a good idea to
have a module which watches the PTE in question, and cycles through
various of the memremap_*() APIs and checks the raw PTE that gets
written after Linux and Xen are done fighting with it
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-12-06 18:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 4:33 [PATCH 0/8] Make PAT handling less brittle Demi Marie Obenour
2022-12-06 4:33 ` [PATCH 1/8] x86/mm: Avoid hard-coding PAT in get_page_from_l1e() Demi Marie Obenour
2022-12-06 10:42 ` Andrew Cooper
2022-12-06 11:07 ` Jan Beulich
2022-12-06 11:05 ` Jan Beulich
2022-12-06 4:33 ` [PATCH 2/8] p2m-pt: Avoid hard-coding Xen's PAT Demi Marie Obenour
2022-12-06 10:59 ` Andrew Cooper
2022-12-06 11:10 ` Jan Beulich
2022-12-06 4:33 ` [PATCH 3/8] x86/mm/shadow: avoid assuming a specific Xen PAT Demi Marie Obenour
2022-12-06 11:00 ` Andrew Cooper
2022-12-06 4:33 ` [PATCH 4/8] efi: Avoid hard-coding the various PAT constants Demi Marie Obenour
2022-12-06 11:15 ` Jan Beulich
2022-12-06 11:17 ` Andrew Cooper
2022-12-06 11:40 ` Jan Beulich
2022-12-06 17:38 ` Demi Marie Obenour
2022-12-06 4:33 ` [PATCH 5/8] x86/mm/shadow: do not open-code PAGE_CACHE_ATTRS Demi Marie Obenour
2022-12-06 11:17 ` Jan Beulich
2022-12-06 4:33 ` [PATCH 6/8] x86: Derive XEN_MSR_PAT from its individual entries Demi Marie Obenour
2022-12-06 11:32 ` Andrew Cooper
2022-12-06 11:43 ` Jan Beulich
2022-12-06 17:44 ` Demi Marie Obenour
2022-12-06 22:51 ` Demi Marie Obenour
2022-12-06 11:35 ` Jan Beulich
2022-12-06 4:33 ` [PATCH 7/8] x86/mm: make code robust to future PAT changes Demi Marie Obenour
2022-12-06 12:01 ` Jan Beulich
2022-12-06 12:06 ` Andrew Cooper
2022-12-06 17:55 ` Demi Marie Obenour
2022-12-07 9:41 ` Jan Beulich
2022-12-07 12:14 ` Andrew Cooper
2022-12-06 4:33 ` [RFC PATCH 8/8] Use Linux's PAT Demi Marie Obenour
2022-12-06 11:38 ` Andrew Cooper
2022-12-06 18:01 ` Demi Marie Obenour
2022-12-06 18:12 ` Marek Marczykowski-Górecki [this message]
2022-12-06 19:47 ` Demi Marie Obenour
2022-12-06 20:53 ` Marek Marczykowski-Górecki
2022-12-13 1:31 ` Demi Marie Obenour
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=Y4+F9iujzOmoOAVe@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=George.Dunlap@citrix.com \
--cc=demi@invisiblethingslab.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--cc=tim@xen.org \
--cc=wl@xen.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.