| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Even if microseconds being -1 is enough, better not leak uninitialized
values.
|
|
|
|
| |
That was a remnant of manual port lookup.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
In case the new task notification gets late, the task may have terminated
already, and thus a dead name gets provided in the notification. We should
just ignore this, otherwise the task hashing would get collisions on all
such dead tasks ports.
|
|
|
|
|
| |
The error handling code would already deallocate them, thus leading to
duplicate deallocation, spurious destroy, and later on port mixup.
|
|
|
|
|
| |
In case the task dies very early and thus the notification arrives very
early.
|
|
|
|
|
| |
mach_port_t are mach_port_name_t and thus require %u instead of %lu.
Message-Id: <Y42RELMbulK4xaKM@reue>
|
|
|
|
|
| |
instead of just exiting: better print a backtrace so we get to know what
happened.
|
|
|
|
|
|
|
|
| |
Whenever a Hurd essential task crashes, startup just reboots the system
since there's not much that can be done at that point. When we have a
kernel debugger, however, we could at least get crashing information, so
let's make Hurd's startup tell the kernel which tasks are essential, so
it can trigger the debugger whenever they crash.
|
|
|
|
|
| |
So we get to know why the system gets stuck if mach-defpager happens to
die.
|
|
|
|
|
|
| |
true structs
Message-Id: <Y3BpLsrddifLOR1z@viriathus>
|
|
|
|
|
| |
hurd/hurd_types.defs is already included through ioctl_types.defs.
Message-Id: <Y3HUZ3KzKnCchYvI@viriathus>
|
|
|
|
|
| |
Also change type srtentry_t to use the new struct format.
Message-Id: <Y3CKiDS3wszn0G4a@viriathus>
|
|
|
|
|
|
|
|
|
|
| |
mig is incorrectly initializing basic types twice (init_type) for kernel
user and kernel server definitions. To fix this bug, we should
initialize the types during a subsystem directive only. This commit
ensures all hurd definitions have subsystem at the very start so that
these definitions work correctly with a patched mig.
Message-Id: <Y3B/9ZCdqYCcd/zf@viriathus>
|
|
|
|
| |
Message-Id: <Y23Sua0dRTrqcxZl@viriathus>
|
|
|
|
| |
Message-Id: <Y2s/UPSCuGap3cv6@viriathus>
|
|
|
|
| |
Message-Id: <Y2NNAegVOKg/X7OC@viriathus>
|
|
|
|
| |
Message-Id: <20221105141505.4684-1-rbraun@sceen.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As explained on
https://www.gnu.org/software/automake/manual/html_node/Multiple-Outputs.html
a b: c
foo -o a -o b
is actually equivalent to
a: c
foo -o a -o b
b: c
foo -o a -o b
and can thus break in parallel builds, since the foo command may then be
called twice. Also, we are here using pattern rules. The automake manual
contains various levels of fixing this, using a mere stamp file should
be enough for us.
|
|
|
|
| |
To allow cross-builds which cannot use AC_LINK_IFELSE at all.
|
|
|
|
| |
To allow cross-builds which cannot use AC_CHECK_LIB at all.
|
|
|
|
| |
* sutils/fstab.c (fstab_find_device): Do not realpath "procfs" pseudo-device.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Message-Id: <20220922004105.961869-1-damien@zamaudio.com>
|
|
|
|
| |
Message-Id: <20220922004018.961808-1-damien@zamaudio.com>
|
|
|
|
|
|
| |
Unfortunately the Linux source also uses <net/route.h>, so we have to
both make that include the glibc-provided one, and avoid making it emit
Linuxish definitions when they would conflict with glibc definitions.
|
| |
|
|
|
|
|
| |
This makes acpi usable as a bootstrap translator.
Message-Id: <20220920030035.931113-1-damien@zamaudio.com>
|
|
|
|
| |
Message-Id: <20220912103837.556815-5-damien@zamaudio.com>
|
|
|
|
|
|
|
| |
This allows clean shutdown of all modern x86 machines
(not just qemu) by using the acpi translator to call
into libacpica code.
Message-Id: <20220912103837.556815-3-damien@zamaudio.com>
|
|
|
|
|
|
|
|
|
| |
Provides two new acpi RPCs to sleep the machine and
to get the irq of any pci device. ACPI mode is enabled
by default when the translator is started.
NB: Merging this commit means libacpica is a build dep.
Message-Id: <20220912103837.556815-2-damien@zamaudio.com>
|
|
|
|
|
|
|
|
| |
This fixes a known race condition in bootstrapping by
separating the fsys_startup call from the server demuxer loop
into two separate functions that the caller can decide
when to call.
Message-Id: <20220908093229.499494-1-damien@zamaudio.com>
|
|
|
|
| |
Message-Id: <20220908093034.499415-1-damien@zamaudio.com>
|
|
|
|
| |
Message-Id: <20220909094234.517165-1-damien@zamaudio.com>
|
|
|
|
|
|
| |
After much digging this fixes the new routing ioctls
Message-Id: <20220831143032.401732-1-damien@zamaudio.com>
|