From: Helge Deller <deller@gmx.de>
To: Mikulas Patocka <mpatocka@redhat.com>, Helge Deller <deller@kernel.org>
Cc: linux-parisc@vger.kernel.org, John David Anglin <dave.anglin@bell.net>
Subject: Re: [PATCH 1/5] parisc: Avoid compat syscalls when COMPAT=n
Date: Wed, 8 Apr 2026 20:15:13 +0200 [thread overview]
Message-ID: <6c8d6fbb-fee8-48a3-b05d-41e1f50bf9ec@gmx.de> (raw)
In-Reply-To: <89d620a0-f6b8-60ea-d423-77b0094756d6@redhat.com>
Hi Mikulas,
On 4/8/26 19:42, Mikulas Patocka wrote:
> On Wed, 8 Apr 2026, Helge Deller wrote:
>> From: Helge Deller <deller@gmx.de>
>>
>> Drop unnecessary code and syscall tables when we run a 64-bit
>> kernel with conpat mode disabled.
>
> Where can I download 64-bit parisc userspace? I am interested in trying it.
Sorry, there is none (yet).
Static binaries do work already, but userspace with shared libraries is being
worked on by Dave. Various patches have been submitted to gcc/glibc during
the last few weeks and progress was made, but it's not finished yet.
Helge
next prev parent reply other threads:[~2026-04-08 18:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 22:27 [PATCH 1/5] parisc: Avoid compat syscalls when COMPAT=n Helge Deller
2026-04-07 22:27 ` [PATCH 2/5] parisc: let is_compat_task() return false for COMPAT=n Helge Deller
2026-04-07 22:27 ` [PATCH 3/5] parisc: Fix signal code to depend on CONFIG_COMPAT instead of CONFIG_64BIT Helge Deller
2026-04-07 22:27 ` [PATCH 4/5] parisc: Fix default stack size when COMPAT=n Helge Deller
2026-04-07 22:27 ` [PATCH 5/5] parisc: Allow to disable COMPAT mode on 64-bit kernel Helge Deller
2026-04-08 15:22 ` [PATCH 1/5] parisc: Avoid compat syscalls when COMPAT=n Thomas Weißschuh
2026-04-08 15:40 ` Helge Deller
2026-04-08 17:42 ` Mikulas Patocka
2026-04-08 18:15 ` Helge Deller [this message]
2026-04-08 19:47 ` John David Anglin
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=6c8d6fbb-fee8-48a3-b05d-41e1f50bf9ec@gmx.de \
--to=deller@gmx.de \
--cc=dave.anglin@bell.net \
--cc=deller@kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mpatocka@redhat.com \
/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