From: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Hari Bathini <hbathini@linux.vnet.ibm.com>,
daniel@iogearbox.net, peterz@infradead.org,
linux-kernel@vger.kernel.org, acme@kernel.org,
alexander.shishkin@linux.intel.com, mingo@redhat.com,
paulus@samba.org, ebiederm@xmission.com, kernel@kyup.com,
viro@zeniv.linux.org.uk, ananth@in.ibm.com
Subject: Re: [RFC PATCH v2 2/3] tracefs: add instances support for uprobe events
Date: Thu, 4 Aug 2016 01:46:04 +0530 [thread overview]
Message-ID: <57A25104.7040805@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160803161039.3180f0fd@gandalf.local.home>
On Thursday 04 August 2016 01:40 AM, Steven Rostedt wrote:
> On Thu, 4 Aug 2016 01:00:51 +0530
> Aravinda Prasad <aravinda@linux.vnet.ibm.com> wrote:
>
>>
>>> Can a container have its own function tracing?
>>
>> Sorry, I didn't understand that. Do you mean to have a separate
>> per-container trace files?
>
> Actually, it's more my ignorance of containers, as I haven't had the
> need to play with them. Although, I think it may be time to do so.
>
> When a container enters kernel mode, I'm assuming that it's part of the
> host at that moment, and the host needs to take care of separating
> everything? That is, there's not a "second kernel" like VMs have, right?
Yes. The host needs to take care of separating everything. There is no
"second kernel".
>
> -- Steve
>
--
Regards,
Aravinda
next prev parent reply other threads:[~2016-08-03 20:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-27 21:27 [RFC PATCH v2 0/3] perf/tracefs: Container-aware tracing support Hari Bathini
2016-07-27 21:27 ` [RFC PATCH v2 1/3] perf: filter container events based on cgroup namespace Hari Bathini
2016-07-27 21:27 ` [RFC PATCH v2 2/3] tracefs: add instances support for uprobe events Hari Bathini
2016-08-01 21:45 ` Steven Rostedt
2016-08-02 17:27 ` Hari Bathini
2016-08-02 17:32 ` Hari Bathini
2016-08-02 17:49 ` Steven Rostedt
2016-08-03 19:30 ` Aravinda Prasad
2016-08-03 20:10 ` Steven Rostedt
2016-08-03 20:16 ` Aravinda Prasad [this message]
2016-08-04 1:04 ` Steven Rostedt
2016-08-04 13:46 ` Aravinda Prasad
2016-08-04 14:08 ` Steven Rostedt
2016-08-04 14:34 ` Aravinda Prasad
2016-07-27 21:27 ` [RFC PATCH v2 3/3] tracefs: add 'newinstance' mount option Hari Bathini
2016-08-04 2:54 ` Eric W. Biederman
2016-08-04 12:26 ` Hari Bathini
2016-08-04 14:12 ` Eric W. Biederman
2016-08-04 2:59 ` [RFC PATCH v2 0/3] perf/tracefs: Container-aware tracing support Eric W. Biederman
2016-08-04 14:48 ` Aravinda Prasad
2016-08-04 18:27 ` Eric W. Biederman
2016-08-04 19:11 ` Aravinda Prasad
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=57A25104.7040805@linux.vnet.ibm.com \
--to=aravinda@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth@in.ibm.com \
--cc=daniel@iogearbox.net \
--cc=ebiederm@xmission.com \
--cc=hbathini@linux.vnet.ibm.com \
--cc=kernel@kyup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=viro@zeniv.linux.org.uk \
/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