From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: Florian Weimer <fweimer@redhat.com>,
Helge Deller <deller@kernel.org>,
John David Anglin <dave.anglin@bell.net>,
libc-alpha@sourceware.org, linux-parisc@vger.kernel.org
Cc: Helge Deller <deller@gmx.de>
Subject: Re: [PATCH] hppa: Wire up cacheflush syscall
Date: Mon, 08 Jul 2024 18:00:25 +0200 [thread overview]
Message-ID: <2572286.PYKUYFuaPT@kona> (raw)
In-Reply-To: <a6a933be-9795-4614-a925-25049736d3c1@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]
Am Montag, 8. Juli 2024, 10:58:35 CEST schrieb Helge Deller:
> On 7/8/24 10:13, Florian Weimer wrote:
> > * Helge Deller:
> >
> >> diff --git a/sysdeps/unix/sysv/linux/hppa/sys/cachectl.h b/sysdeps/unix/sysv/linux/hppa/sys/cachectl.h
> >> new file mode 100644
> >> index 0000000000..16e47d1329
> >> --- /dev/null
> >> +++ b/sysdeps/unix/sysv/linux/hppa/sys/cachectl.h
> >> @@ -0,0 +1,36 @@
> >
> >> +#ifndef _SYS_CACHECTL_H
> >> +#define _SYS_CACHECTL_H 1
> >> +
> >> +#include <features.h>
> >> +
> >> +/* Get the kernel definition for the op bits. */
> >> +#include <asm/cachectl.h>
> >
> > This makes this header (<sys/cachectl.h>) unusable with older kernel
> > headers. I think it also results in a test failure with older headers.
> > Is this a problem?
>
> hppa lives in debian unstable, so basically you should always use
> the latest kernel & kernel headers when upgrading glibc.
Ahem.
https://www.gentoo.org/downloads/#hppa
> So, personally I think it's ok to ask people to upgrade.
> Dave, any opinion on this?
>
> > In similar cases, we use LINUX_VERSION_CODE checks (for older compilers)
> > and __has_include to support backports.
>
> I'd prefer to not add additional checks.
> Another (maybe easier) possibility is to simply backport the kernel asm/cachectl.h
> file (just the header, not the implementation, so the syscall will return -ENOSYS on
> older kernels):
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c6d96328fecdda16e12f3b3c33f3677f4bcef89f
>
> Helge
>
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2024-07-08 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 1:10 [PATCH] hppa: Wire up cacheflush syscall Helge Deller
2024-07-08 8:13 ` Florian Weimer
2024-07-08 8:58 ` Helge Deller
2024-07-08 16:00 ` Andreas K. Huettel [this message]
2024-07-08 18:26 ` Helge Deller
2024-07-09 13:41 ` Sam James
2024-08-03 8:57 ` John David Anglin
2024-09-26 19:08 ` Sam James
2024-09-27 7:16 ` Helge Deller
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=2572286.PYKUYFuaPT@kona \
--to=dilfridge@gentoo.org \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=deller@kernel.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-parisc@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