From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Simon Richter <Simon.Richter@hogyros.de>,
intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Mark xe driver as BROKEN if kernel page size is not 4kB
Date: Fri, 01 Aug 2025 16:56:50 +0200 [thread overview]
Message-ID: <37abb9a1a4fde174a54a9d7868d31b2615df0e47.camel@linux.intel.com> (raw)
In-Reply-To: <274fefe9b46bb856e5968431ed524ebe1b8e8cd4.camel@linux.intel.com>
On Fri, 2025-08-01 at 16:39 +0200, Thomas Hellström wrote:
> On Fri, 2025-08-01 at 19:19 +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.
> >
> > Signed-off-by: Simon Richter <Simon.Richter@hogyros.de>
> > Cc: stable@vger.kernel.org
>
> Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> I will add a Fixes: tag and push this.
>
> Thanks,
> Thomas
Actually, I see that the patch in its current form will cause grief
when backporting since that depends line has changed during driver
lifetime. I noticed that when trying to find a good Fixes: tag.
Would you mind if we did the following:
>
>
> > ---
> > 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..ea12ff033439 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 || COMPILE_TEST ||
> > BROKEN)
Scratch this change
> > depends on KUNIT || !KUNIT
> > depends on INTEL_VSEC || !INTEL_VSEC
> > depends on X86_PLATFORM_DEVICES || !(X86 && ACPI)
And instead here add
depends on PAGE_SIZE_4KB || COMPILE_TEST || BROKEN
Thanks,
Thomas
>
>
next prev parent reply other threads:[~2025-08-01 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 7:04 [PATCH v2 0/1] " Simon Richter
2025-07-27 7:04 ` [PATCH v2 1/1] " Simon Richter
2025-08-01 9:20 ` Thomas Hellström
2025-08-01 10:19 ` [PATCH v3] " Simon Richter
2025-08-01 14:39 ` Thomas Hellström
2025-08-01 14:56 ` Thomas Hellström [this message]
2025-08-01 15:13 ` Simon Richter
2025-08-02 2:40 ` [PATCH v4] " Simon Richter
2025-08-04 9:40 ` Thomas Hellström
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=37abb9a1a4fde174a54a9d7868d31b2615df0e47.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=Simon.Richter@hogyros.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®