Re: [PATCH gnumach] Update task_basic_info and thread_basic_info to include time_value64_t data.

2023-04-26 Thread Samuel Thibault
Applied, thanks! Flavio Cruz, le lun. 17 avril 2023 00:46:36 -0400, a ecrit: > RPCs remain compatible with existing clients but if they know about the > new size then we will populate the new fields. > --- > include/mach/task_info.h | 8 > include/mach/thread_info.h | 6 ++ > ker

Re: [PATCH 5/5] add setting gs/fsbase

2023-04-26 Thread Sergey Bugaev
Hi again, I managed to break gnumach in a new and exciting way (tm): ../kern/ipc_tt.c:395: retrieve_task_self_fast: Assertion `task->itk_self != IP_NULL' failed.panic ../kern/debug.c:103: Debugger: Debugger invoked, but there isn't one! This is after typing 'quit' in bc, which calls exit () -- I

Re: [PATCH gnumach] Use c_string for dev_name_t in the device subsystem.

2023-04-26 Thread Sergey Bugaev
Hi Flavio, could you please explain what the difference / the advantage of new_dev_name_t is over dev_name_t? (Preferably, put it into the commit message too.) Isn't c_string same as MACH_MSG_TYPE_STRING_C? What are we gaining? What is your overall plan concerning string handling in RPCs? The tw

Re: [PATCH gnumach] Update task_basic_info and thread_basic_info to include time_value64_t data.

2023-04-26 Thread Samuel Thibault
Flávio Cruz, le mar. 25 avril 2023 22:26:53 -0400, a ecrit: > Ok, but none of the clock(), getrusage() and times() functions expose > nano-second precision. If we can avoid complexity when we don't actually > need it, I'd rather avoid it :) > > > Sounds fair, but doesn't clock_gettime