From: Josh Stone <jistone@redhat.com>
To: Malte Nuhn <nuhn@physik.rwth-aachen.de>
Cc: systemtap@sources.redhat.com
Subject: Re: context.stp - read session ID - function sid()
Date: Mon, 11 May 2009 18:22:00 -0000 [thread overview]
Message-ID: <4A086CE1.8050107@redhat.com> (raw)
In-Reply-To: <4A081834.8080004@physik.rwth-aachen.de>
On 05/11/2009 05:21 AM, Malte Nuhn wrote:
> I read about process namespaces @ http://lwn.net/Articles/259217/
> and I'm not quite sure, what one should do (even in general) with these.
> Being exact, a call like "pid()" or "sid()"
> is not "valid" anymore, since you need to specify the pid namespace. The
> easiest thing to do is to always pull out the
> virtual pid implicitly. But but then, the user should at least know that
> systemtap chose the virtual one.
>
> What do you think about that?
I think the best approach for SystemTap is to provide ids from the init
namespace (with the *_nr variants), so they will still be globally
unique. We can provide the virtual ids in separate calls, perhaps
vpid(), vsid(), etc.
Josh
prev parent reply other threads:[~2009-05-11 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 15:04 Malte Nuhn
2009-05-08 20:06 ` Josh Stone
2009-05-11 12:21 ` Malte Nuhn
2009-05-11 18:22 ` Josh Stone [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A086CE1.8050107@redhat.com \
--to=jistone@redhat.com \
--cc=nuhn@physik.rwth-aachen.de \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).