[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 0/9] AArch64 Mach public headers

From: Samuel Thibault
Subject: Re: [PATCH 0/9] AArch64 Mach public headers
Date: Tue, 16 Apr 2024 03:02:51 +0200
User-agent: NeoMutt/20170609 (1.8.3)



I applied the series except the patch adding the test, since it fails on
x86_64. Most probably it's the test that needs fixing.


Sergey Bugaev, le lun. 15 avril 2024 12:01:40 +0300, a ecrit:
> Hello!
> This patchset contains public headers for AArch64 support in GNU Mach,
> along with just enough buildsystem infrastructure to recognize and
> install them. It is quite similar to the "sketch" patches that I have
> posted in January of this year, but I have done a number of changes for
> two reasons. One reason is me becoming a lot more familiar with ARM and
> AArch64, in particular having done a bunch of reading of the Arm ARM.
> The other reason is there is now a real port of GNU Mach to AArch64,
> using these headers as its actual API/ABI. We got the Mach port to run
> glibc, several Hurd servers, and simple Unix programs, including things
> like fork/exec and signal delivery & handling working, which excersizes
> these architecture-specific definitions (thread state & exceptions). We
> have also managed to do some testing on real hardware; although not
> everything is working yet, we have seen thread state manipulation &
> Mach handling an unaligned SP fault work as expected.
> While the Mach port exists, I'm not proposing we merge it yet. This
> patch set only contains the headers, pulled from the AArch64 port
> branch. It is small enough, already in ready-to-be-merged state (as
> opposed to prototype/sketch state it was this January), and should be
> easy to review. At the same time, this should be enough to build glibc
> and most of the Hurd, and then the rest of the userland; this also means
> that merging this patchset should be enough to unblock merging the glibc
> port upstream, now that the GCC patches are in.
> Sergey

reply via email to

[Prev in Thread] Current Thread [Next in Thread]