mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: David Laight <david.laight.linux@gmail.com>
Cc: Willy Tarreau <w@1wt.eu>, Daniel Palmer <daniel@thingy.jp>,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] tools/nolibc: handle 64-bit system call arguments on MIPS N32
Date: Mon, 20 Apr 2026 17:58:07 +0200	[thread overview]
Message-ID: <00d91bf0-b01e-473e-a48c-d944ce0a3d86@t-8ch.de> (raw)
In-Reply-To: <20260419223507.1dc5554a@pumpkin>

Hi David,

On 2026-04-19 22:35:07+0100, David Laight wrote:
> On Sun, 19 Apr 2026 17:30:13 +0200
> Willy Tarreau <w@1wt.eu> wrote:
> > On Sat, Apr 18, 2026 at 01:54:55PM +0200, Thomas Weißschuh wrote:

(...)

> I would suggest using "+r" for the in-out registers; and [arg5] for the
> ones that get pushed, reliably counting to 7 is hard :-)

Yeah, we could do this. As the code barely changes I am not convinced it
makes a big difference, though. It wouldn't be part of this patchset
anyways. If you want to send a patch, please go ahead :-)

> Related to one of the other patches, I can't imagine how N32 getting
> a 64bit value truncated would be a qemu bug.
> Just seems wrong - isn't the cpu just running in 64bit mode ?

That is true for QEMU "system" mode. And there everything works
correctly. But the bug exists in QEMU "user" mode. This does not
simulate a CPU. Instead a single executable is executed on the host by
converting code and system calls on demand. That translation is
architectures/ABI-specific and the N32 implementation uses 32-bit
variables.

(...)


Thomas

  reply	other threads:[~2026-04-20 15:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-18 10:19 [PATCH 0/7] tools/nolibc: large file support Thomas Weißschuh
2026-04-18 10:19 ` [PATCH 1/7] tools/nolibc: also handle _llseek system call Thomas Weißschuh
2026-04-18 11:23   ` David Laight
2026-04-18 11:56     ` Thomas Weißschuh
2026-04-18 16:03       ` David Laight
2026-04-19 15:22         ` Willy Tarreau
2026-04-19 15:38           ` Thomas Weißschuh
2026-04-19 16:10             ` Willy Tarreau
2026-04-18 10:19 ` [PATCH 2/7] tools/nolibc: add __nolibc_arg_to_reg() Thomas Weißschuh
2026-04-18 10:19 ` [PATCH 3/7] tools/nolibc: cast pointers returned from system calls through integers Thomas Weißschuh
2026-04-18 10:19 ` [PATCH 4/7] tools/nolibc: handle 64-bit system call arguments on x32 Thomas Weißschuh
2026-04-18 10:20 ` [PATCH 5/7] tools/nolibc: handle 64-bit system call arguments on MIPS N32 Thomas Weißschuh
2026-04-18 11:14   ` David Laight
2026-04-18 11:54     ` Thomas Weißschuh
2026-04-18 16:32       ` David Laight
2026-04-19 15:30       ` Willy Tarreau
2026-04-19 21:35         ` David Laight
2026-04-20 15:58           ` Thomas Weißschuh [this message]
2026-04-18 10:20 ` [PATCH 6/7] tools/nolibc: open files with O_LARGEFILE Thomas Weißschuh
2026-04-18 10:20 ` [PATCH 7/7] selftests/nolibc: test large file support Thomas Weißschuh
2026-04-18 14:01 ` [PATCH 0/7] tools/nolibc: " Daniel Palmer
2026-04-19 15:31 ` Willy Tarreau

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=00d91bf0-b01e-473e-a48c-d944ce0a3d86@t-8ch.de \
    --to=linux@weissschuh.net \
    --cc=daniel@thingy.jp \
    --cc=david.laight.linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=w@1wt.eu \
    /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®