Re: RFC [patch 13/34] PID Virtualization Define new task

From:		Alan Cox <alan-AT-lxorguk.ukuu.org.uk>
To:		"Serge E. Hallyn" <serue-AT-us.ibm.com>
Subject:		Re: RFC [patch 13/34] PID Virtualization Define new task_pid api
Date:		Tue, 17 Jan 2006 16:03:38 +0000
Cc:		Arjan van de Ven <arjan-AT-infradead.org>, linux-kernel-AT-vger.kernel.org, Hubertus Franke <frankeh-AT-watson.ibm.com>, Cedric Le Goater <clg-AT-fr.ibm.com>, Dave Hansen <haveblue-AT-us.ibm.com>
Archive-link:		Article, Thread

On Maw, 2006-01-17 at 09:56 -0600, Serge E. Hallyn wrote:
> The virtual pid is different depending on who is asking.  So simply
> storing current->realpid and current->pid isn't helpful, as we would
> still need to call a function when a pid crosses user->kernel boundary.

This is an obscure, weird piece of functionality for some special case
usages most of which are going to be eliminated by Xen. I don't see the
kernel side justification for it at all.

Maybe you should remap it the other side of the user->kernel boundary ?

(Log in to post comments)

Re: RFC [patch 13/34] PID Virtualization Define new task_pid api