From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Alessio Igor Bogani <abogani@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Avi Kivity <avi@redhat.com>, Chris Metcalf <cmetcalf@tilera.com>,
Christoph Lameter <cl@linux.com>,
Geoff Levand <geoff@infradead.org>,
Gilad Ben Yossef <gilad@benyossef.com>,
Hakan Akkan <hakanakkan@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>, Kevin Hilman <khilman@ti.com>,
Max Krasnyansky <maxk@qualcomm.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Stephen Hemminger <shemminger@vyatta.com>,
Sven-Thorsten Dietrich <thebigcorporation@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 1/5] user_hooks: New user hooks subsystem
Date: Wed, 1 Aug 2012 14:45:19 +0200 [thread overview]
Message-ID: <20120801124513.GB28650@somewhere.redhat.com> (raw)
In-Reply-To: <1343824983.27983.74.camel@gandalf.stny.rr.com>
On Wed, Aug 01, 2012 at 08:43:03AM -0400, Steven Rostedt wrote:
> On Wed, 2012-08-01 at 14:28 +0200, Frederic Weisbecker wrote:
> > On Tue, Jul 31, 2012 at 06:14:22PM +0200, Peter Zijlstra wrote:
>
> > So we probably need to generalize a bit more. Some naming based on
> > "code domain"?
> >
> > struct code_domain {
> > int is_tracking;
> > enum {
> > in_kernel,
> > in_user,
> > in_guest
> > } state;
> > }
>
> Is there a fundamental difference between 'in_user' and 'in_guest'
> though?
Probably not from RCU POV. But the cputime is not accounted the same.
next prev parent reply other threads:[~2012-08-01 12:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 15:40 [RFC PATCH 0/5] cputime: Generic virtual based cputime accounting Frederic Weisbecker
2012-07-27 15:40 ` [PATCH 1/5] user_hooks: New user hooks subsystem Frederic Weisbecker
2012-07-27 16:40 ` Paul E. McKenney
2012-07-27 16:58 ` Frederic Weisbecker
2012-07-30 15:08 ` Peter Zijlstra
2012-07-30 15:27 ` Steven Rostedt
2012-07-30 16:30 ` Peter Zijlstra
2012-07-30 15:51 ` Frederic Weisbecker
2012-07-30 16:07 ` Steven Rostedt
2012-07-30 16:31 ` Peter Zijlstra
2012-07-30 16:32 ` Peter Zijlstra
2012-07-31 7:06 ` Ingo Molnar
2012-07-31 10:48 ` Frederic Weisbecker
2012-07-31 14:57 ` Ingo Molnar
2012-07-31 16:14 ` Peter Zijlstra
2012-08-01 12:28 ` Frederic Weisbecker
2012-08-01 12:43 ` Steven Rostedt
2012-08-01 12:45 ` Frederic Weisbecker [this message]
2012-07-27 15:40 ` [PATCH 2/5] cputime: Don't allow virtual and irq finegrained cputime accounting simultaneously Frederic Weisbecker
2012-07-27 15:40 ` [PATCH 3/5] cputime: Allow dynamic switch between tick/virtual based cputime accounting Frederic Weisbecker
2012-07-27 15:40 ` [PATCH 4/5] cputime: Rename account_system_vtime to account_vtime Frederic Weisbecker
2012-07-27 15:40 ` [PATCH 5/5] cputime: Generic on-demand virtual cputime accounting Frederic Weisbecker
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=20120801124513.GB28650@somewhere.redhat.com \
--to=fweisbec@gmail.com \
--cc=abogani@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=cl@linux.com \
--cc=cmetcalf@tilera.com \
--cc=geoff@infradead.org \
--cc=gilad@benyossef.com \
--cc=hakanakkan@gmail.com \
--cc=hpa@zytor.com \
--cc=khilman@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shemminger@vyatta.com \
--cc=tglx@linutronix.de \
--cc=thebigcorporation@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.