From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Ingo Molnar <mingo@kernel.org>, Mike Galbraith <efault@gmx.de>,
linux-kernel@vger.kernel.org,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [PATCH 0/2] RFC: readd fair sleepers for server systems
Date: Wed, 23 May 2012 17:43:54 +0200 [thread overview]
Message-ID: <1337787834.9783.4.camel@laptop> (raw)
In-Reply-To: <4FBD0236.7040508@linux.vnet.ibm.com>
On Wed, 2012-05-23 at 17:28 +0200, Christian Ehrhardt wrote:
> We don't have any code for CONFIG_PARAVIRT and its childs yet, so I need
> to look further into it.
Yeah, screw CONFIG_PARAVIRT :-) Its just that the code that deals with
high res steal time is only used by them. So ideally you'd extract the
relevant bits from under CONFIG_PARAVIRT and use them.
So its that one block in update_rq_clock_task() (or both if you also
have high res irq accounting) and then you need to provide
paravirt_steal_clock(int cpu) which returns the steal time of that cpu
in nano-seconds granularity. Which I'm assuming s390 has available
someplace.
+- some renames to remove the paravirt_ part of names.
prev parent reply other threads:[~2012-05-23 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 15:45 [PATCH 0/2] RFC: readd fair sleepers for server systems Martin Schwidefsky
2012-05-21 15:45 ` [PATCH 1/2] sched: readd FAIR_SLEEPERS feature Martin Schwidefsky
2012-05-22 7:11 ` Christian Ehrhardt
2012-05-22 9:06 ` Mike Galbraith
2012-05-21 15:45 ` [PATCH 2/2] sched: enable FAIR_SLEEPERS for s390 Martin Schwidefsky
2012-05-21 18:17 ` [PATCH 0/2] RFC: readd fair sleepers for server systems Mike Galbraith
2012-05-22 7:11 ` Christian Ehrhardt
2012-05-22 8:53 ` Mike Galbraith
2012-05-22 9:01 ` Peter Zijlstra
2012-05-23 11:32 ` Christian Ehrhardt
2012-05-23 11:49 ` Peter Zijlstra
2012-05-23 15:28 ` Christian Ehrhardt
2012-05-23 15:43 ` Peter Zijlstra [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=1337787834.9783.4.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=ehrhardt@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=schwidefsky@de.ibm.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