Thank you for all the helpful information, it helps a bunch!
Sincerely,
Nathan
___
users mailing list -- users@lists.genode.org
To unsubscribe send an email to users-le...@lists.genode.org
Archived at
https://lists.genode.org/mailman3/hyperkitty/list/us
Hello,
On 2024-03-07 20:37, Nobody III wrote:
This is a bit of a tangent, but could the existing mechanisms be used to
efficiently implement memory over-provisioning for non-critical processes,
disk swapping, and copy-on-write page tables for a faster fork()
implementation?
this was indeed one
This is a bit of a tangent, but could the existing mechanisms be used to
efficiently implement memory over-provisioning for non-critical processes,
disk swapping, and copy-on-write page tables for a faster fork()
implementation?
On Thu, Mar 7, 2024, 12:11 AM Christian Helmuth <
christian.helm...@g
I have to correct myself...
On Thu, Mar 07, 2024 at 08:04:59 CET, Christian Helmuth wrote:
> and contains the current exception in 'Cpu_state::trapno' for x86
> [5], 'Cpu_state::cpu_exception' for arm v6/v7 [6], and seems to be
> missing for arm v8.
It seems ARMv8 provides an "exception syndrome"
Hello Nathan,
On Wed, Mar 06, 2024 at 21:15:47 CET, n...@ksu.edu wrote:
> I was working on a project and noticed that the only kernel fault
> core allows a component to handle is a page fault. Is there a
> particular reason that core only allows page faults to be handled
> and not all kernel fault
Hello Genodians,
I was working on a project and noticed that the only kernel fault core allows a
component to handle is a page fault. Is there a particular reason that core
only allows page faults to be handled and not all kernel faults? If there is a
problem with receiving all faults I would
