TODO-list

Hello, I have been thinking about doing this for some time when seeing people start working on various things, which is nice, but perhaps missing some long-term targets. I took the time to do it: https://darnassus.sceen.net/~hurd-web/contributing/#index3h2 This is a TODO-list of mostly not-sexy

Re: [RFC PATCH 12/23] aarch64: Make cpu-features definitions not Linux-specific

Applied, thanks! Sergey Bugaev, le mer. 03 janv. 2024 20:14:45 +0300, a ecrit: > These describe generic AArch64 CPU features, and are not tied to a > kernel-specific way of determining them. We can share them between > the Linux and Hurd AArch64 ports. > > Signed-off-by: Sergey Bugaev > --- > s

Re: [RFC PATCH 11/23] hurd: Initializy _dl_pagesize early in static builds

Applied, thanks! Sergey Bugaev, le mer. 03 janv. 2024 20:14:44 +0300, a ecrit: > We fetch __vm_page_size as the very first RPC that we do, inside > __mach_init (). Propagate that to _dl_pagesize ASAP after that, > before any other initialization. > > In dynamic builds, this is already done immedi

Re: [RFC PATCH 10/23] hurd: Only init early static TLS if it's used to store stack or pointer guards

Applied, thanks! Sergey Bugaev, le mer. 03 janv. 2024 20:14:43 +0300, a ecrit: > This is the case on both x86 architectures, but not on AArch64. > > Signed-off-by: Sergey Bugaev > --- > sysdeps/mach/hurd/init-first.c | 15 +++ > 1 file changed, 11 insertions(+), 4 deletions(-) > >

Re: [RFC PATCH 09/23] hurd: Make init-first.c no longer x86-specific

Applied, thanks! Sergey Bugaev, le mer. 03 janv. 2024 20:14:42 +0300, a ecrit: > This will make it usable in other ports. > > Signed-off-by: Sergey Bugaev > --- > sysdeps/mach/hurd/{x86 => }/init-first.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > rename sysdeps/mach/hurd/{x8

Re: [RFC PATCH 08/23] hurd: Drop x86-specific assembly from init-first.c

Applied, thanks! Sergey Bugaev, le mer. 03 janv. 2024 20:14:41 +0300, a ecrit: > We already have the RETURN_TO macro for this exact use case, and it's already > used in the non-static code path. Use it here too. > > Signed-off-by: Sergey Bugaev > --- > > This was the last piece of x86 specifics

Re: [RFC PATCH 07/23] hurd: Pass the data pointer to _hurd_stack_setup explicitly

Applied, thanks! Sergey Bugaev, le mer. 03 janv. 2024 20:14:40 +0300, a ecrit: > Instead of relying on the stack frame layout to figure out where the stack > pointer was prior to the _hurd_stack_setup () call, just pass the pointer > as an argument explicitly. This is less brittle and much more po

Re: 64bit startup

Hello, Sergey Bugaev, le jeu. 04 janv. 2024 22:21:11 +0300, a ecrit: > On Thu, Jan 4, 2024 at 10:57 AM Samuel Thibault > wrote: > > Sergey Bugaev, le mer. 03 janv. 2024 21:56:54 +0300, a ecrit: > > > perhaps I need to try two of them in parallel and some I/O-heavy > > > workload in the backgroun

Re: 64bit startup

On Thu, Jan 4, 2024 at 10:57 AM Samuel Thibault wrote: > > Sergey Bugaev, le mer. 03 janv. 2024 21:56:54 +0300, a ecrit: > > perhaps I need to try two of them in parallel and some I/O-heavy > > workload in the background, as you're saying. > > Yes, that's needed to raise the probability of the bug

Re: 64bit startup

On Wed, Jan 3, 2024 at 10:07 PM Luca wrote: > Hi Sergey, Hi, > Recently I've been installing hurd-amd64 on another disk of my hurd-i386 > vm and booting from that. Basically I prepare the disk with debootstrap > --foreign, then I reuse the i386 grub install to boot the 64 bit kernel > with a cus