From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
LKML <linux-kernel@vger.kernel.org>,
libc-alpha@sourceware.org, linux-arch@vger.kernel.org
Subject: Re: Metalanguage for the Linux UAPI
Date: Thu, 15 May 2025 14:42:01 -0700 [thread overview]
Message-ID: <425880dd-e694-4428-999e-a787a666de5f@zytor.com> (raw)
In-Reply-To: <CAHk-=wi7sLm+zHUkyFO8V6QNghLQn0yiWsHfm8WU=V15K7K07Q@mail.gmail.com>
On 5/15/25 14:20, Linus Torvalds wrote:
>
> If you _really_ want to do a Metalanguage for these things, and want
> to support lots of different namespace issues, several different
> languages etc, I have a very practical suggestion: make that
> metalanguage have a very strict and traditional syntax. Make it look
> like C with the C pre-processor.
>
> There are lots of libraries and tools to parse C, and turn it into
> other forms. Making up a new language when we already *have* a good
> language is all kinds of silly. Just use the language it already is
> in, and take advantage of the fact that there's lots of infrastructure
> for that language.
>
Yes, and I looked at using sparse for this purpose. It is not a bad
choice all things considered, but there is definitely metadata that we
simply don't provide.
Building it on top of sparse might still very well be The Right Thing.
It doesn't just affect libc, either; it also affects tools like strace,
sanitizer, and so on. The situation with ioctls is by far the worst.
-hpa
next prev parent reply other threads:[~2025-05-15 21:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 20:04 H. Peter Anvin
2025-05-15 20:26 ` enh
2025-05-15 21:24 ` H. Peter Anvin
2025-05-16 3:42 ` Willy Tarreau
2025-05-16 4:17 ` H. Peter Anvin
2025-05-16 4:22 ` Willy Tarreau
2025-05-16 4:35 ` H. Peter Anvin
2025-05-16 17:27 ` enh
2025-05-15 21:20 ` Linus Torvalds
2025-05-15 21:42 ` H. Peter Anvin [this message]
2025-05-15 22:06 ` Linus Torvalds
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=425880dd-e694-4428-999e-a787a666de5f@zytor.com \
--to=hpa@zytor.com \
--cc=arnd@arndb.de \
--cc=libc-alpha@sourceware.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®