From: Dave Hansen <dave.hansen@intel.com>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>,
Borislav Petkov <bp@alien8.de>
Cc: Juergen Gross <jgross@suse.com>,
x86@kernel.org, intel-gfx@lists.freedesktop.org,
Dave Hansen <dave.hansen@linux.intel.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Intel-gfx] [PATCH v2] x86/mm: Fix PAT bit missing from page protection modify mask
Date: Wed, 7 Jun 2023 08:31:24 -0700 [thread overview]
Message-ID: <a20344fd-8130-013e-e773-acae81aad55a@intel.com> (raw)
In-Reply-To: <20230607152308.125787-2-janusz.krzysztofik@linux.intel.com>
On 6/7/23 08:23, Janusz Krzysztofik wrote:
>
> Extend bitmask used by pgprot_modify() for selecting bits to be preserved
> with _PAGE_PAT bit. However, since that bit can be reused as _PAGE_PSE,
> and the _PAGE_CHG_MASK symbol, primarly used by pte_modify(), is likely
> intentionally defined with that bit not set, keep that symbol unchanged.
I'm really having a hard time parsing what that last sentence is saying.
Could you try again, please?
next prev parent reply other threads:[~2023-06-07 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 15:23 [Intel-gfx] [PATCH v2] x86/mm: Fix PAT bit missing from page protection modify mask Janusz Krzysztofik
2023-06-07 15:31 ` Dave Hansen [this message]
2023-06-07 17:11 ` Janusz Krzysztofik
2023-06-07 21:12 ` Edgecombe, Rick P
2023-06-07 21:33 ` Janusz Krzysztofik
2023-06-07 22:47 ` Edgecombe, Rick P
2023-06-08 13:19 ` Janusz Krzysztofik
2023-06-08 5:15 ` Juergen Gross
2023-06-07 23:38 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for x86/mm: Fix PAT bit missing from page protection modify mask (rev2) Patchwork
2023-06-07 23:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-08 17:47 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=a20344fd-8130-013e-e773-acae81aad55a@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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