Re: Hacking gnumach to track parental relationship of tasks

2013-09-06 Thread Justus Winter
Quoting Ludovic =?utf-8?Q?Court=C3=A8s?= (2013-09-05 18:11:43) > Justus Winter <4win...@informatik.uni-hamburg.de> skribis: > > > I made two rather small and (as I thought) straight forward changes to > > gnumach to keep track of a tasks father task and to make this > > information available. > >

Re: Hacking gnumach to track parental relationship of tasks

2013-09-06 Thread Ludovic Courtès
Justus Winter <4win...@informatik.uni-hamburg.de> skribis: > Quoting Ludovic =?utf-8?Q?Court=C3=A8s?= (2013-09-05 18:11:43) >> Justus Winter <4win...@informatik.uni-hamburg.de> skribis: >> >> > I made two rather small and (as I thought) straight forward changes to >> > gnumach to keep track of a

Re: Hacking gnumach to track parental relationship of tasks

2013-09-06 Thread Neal H. Walfield
At Thu, 5 Sep 2013 16:57:41 +0200, Justus Winter wrote: > I made two rather small and (as I thought) straight forward changes to > gnumach to keep track of a tasks father task and to make this > information available. What happens when the parent task is destroyed? Are the children destroyed wit

Re: Hacking gnumach to track parental relationship of tasks

2013-09-06 Thread Justus Winter
Quoting Ludovic =?utf-8?Q?Court=C3=A8s?= (2013-09-06 11:58:43) > Justus Winter <4win...@informatik.uni-hamburg.de> skribis: > > > Quoting Ludovic =?utf-8?Q?Court=C3=A8s?= (2013-09-05 18:11:43) > >> Justus Winter <4win...@informatik.uni-hamburg.de> skribis: > >> > >> > I made two rather small and

[PATCH] chips: drop the register keyword and use boolean_t

2013-09-06 Thread Marin Ramesa
I noticed a variable that only receives values 0 and 1, so I'm turning it into a boolean. I think the code is more readable that way. Also drop the register keyword since I've seen Justus mention it is ignored by modern compilers. And I must admit I've never seen it used in a more modern microk

Re: [PATCH 1/2] Port gdbserver to GNU/Hurd

2013-09-06 Thread Pedro Alves
Hi! On 09/05/2013 08:29 PM, Pedro Alves wrote: >> > +static int >> > +gnu_read_memory (CORE_ADDR addr, unsigned char *myaddr, int length) >> > +{ >> > + int ret = 0; >> > + task_t task = (gnu_current_inf >> > + ? (gnu_current_inf->task >> > +? gnu_current_inf->task->port : 0) : 0); >> > + i

[PATCH] ipc: perform conditional locking while changing the port sequence number

2013-09-06 Thread Marin Ramesa
* ipc/ipc_port.c (ipc_port_set_seqno) [MACH_SLOCKS]: Conditional locking. =46rom d56b769755a5d671f084ebdd482de8b34be9cd5b Mon Sep 17 00:00:00 2001 From: Marin Ramesa Date: Sat, 7 Sep 2013 07:37:42 +0200 Subject: [PATCH] perform conditional locking while changing the port sequence number --- ipc

Re: [PATCH] ipc: perform conditional locking while changing the port sequence number

2013-09-06 Thread Samuel Thibault
Marin Ramesa, le Sat 07 Sep 2013 08:00:47 +0200, a écrit : > * ipc/ipc_port.c (ipc_port_set_seqno) [MACH_SLOCKS]: Conditional locking. What is the rationale? Does it really bring an noticeable improvement? The locking is already conditional inside ipc_port_lock_mqueue, from the simple_*lock* macr