From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: linux-next: manual merge of the cputime tree
Date: Tue, 25 Nov 2008 12:00:24 +0100 [thread overview]
Message-ID: <1227610824.30264.5.camel@localhost> (raw)
In-Reply-To: <1227608880.4259.1451.camel@twins>
On Tue, 2008-11-25 at 11:28 +0100, Peter Zijlstra wrote:
> On Tue, 2008-11-25 at 11:15 +0100, Martin Schwidefsky wrote:
> > On Tue, 2008-11-25 at 11:06 +0100, Peter Zijlstra wrote:
> > > Why does s390 do its own cpu accounting?
> >
> > Is that a trick question? I invented the cputime accounting specifically
> > for s390 because it is a virtual architecture and the standard cpu
> > accounting numbers are just useless.
>
> Nah, just general ignorance brought on by the mondays on a tuesday ;-)
Ah, I usually have this on mondays ..
> Right, makes sense, is it shared with all other virt* folks out there?
Yes, the other virtual architectures have started to use the interface
as well.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2008-11-25 11:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 9:21 linux-next: manual merge of the cputime tree Stephen Rothwell
2008-11-25 10:06 ` Peter Zijlstra
2008-11-25 10:15 ` Martin Schwidefsky
2008-11-25 10:28 ` Peter Zijlstra
2008-11-25 10:32 ` Paul Mackerras
2008-11-25 11:00 ` Martin Schwidefsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-11 6:56 Stephen Rothwell
2008-11-10 6:09 Stephen Rothwell
2008-11-10 8:45 ` Martin Schwidefsky
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=1227610824.30264.5.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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.