From: Greg KH <gregkh@linuxfoundation.org>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
1109776@bugs.debian.org, jeffbai@aosc.io
Subject: Re: [PATCH 1/1] Mark xe driver as BROKEN if kernel page size is not 4kB
Date: Sun, 27 Jul 2025 07:28:18 +0200 [thread overview]
Message-ID: <2025072708-saxophone-watch-3020@gregkh> (raw)
In-Reply-To: <20250727042825.8560-2-Simon.Richter@hogyros.de>
On Sun, Jul 27, 2025 at 01:27:36PM +0900, Simon Richter wrote:
> This driver, for the time being, assumes that the kernel page size is 4kB,
> so it fails on loong64 and aarch64 with 16kB pages, and ppc64el with 64kB
> pages.
> ---
> drivers/gpu/drm/xe/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/Kconfig b/drivers/gpu/drm/xe/Kconfig
> index 2bb2bc052120..7c9f1de7b35f 100644
> --- a/drivers/gpu/drm/xe/Kconfig
> +++ b/drivers/gpu/drm/xe/Kconfig
> @@ -1,7 +1,7 @@
> # SPDX-License-Identifier: GPL-2.0-only
> config DRM_XE
> tristate "Intel Xe2 Graphics"
> - depends on DRM && PCI
> + depends on DRM && PCI && (PAGE_SIZE_4KB || BROKEN)
> depends on KUNIT || !KUNIT
> depends on INTEL_VSEC || !INTEL_VSEC
> depends on X86_PLATFORM_DEVICES || !(X86 && ACPI)
> --
> 2.47.2
>
>
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly.
</formletter>
prev parent reply other threads:[~2025-07-27 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 4:27 [PATCH 0/1] Mark xe driver as BROKEN until fixed Simon Richter
2025-07-27 4:27 ` [PATCH 1/1] Mark xe driver as BROKEN if kernel page size is not 4kB Simon Richter
2025-07-27 5:28 ` Greg KH [this message]
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=2025072708-saxophone-watch-3020@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=1109776@bugs.debian.org \
--cc=Simon.Richter@hogyros.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jeffbai@aosc.io \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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