From: m.smarduch@samsung.com (Mario Smarduch)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64 sched_clock cpu accounting
Date: Wed, 02 Dec 2015 15:42:10 -0800 [thread overview]
Message-ID: <565F81D2.3060401@samsung.com> (raw)
In-Reply-To: <20151202180741.GR18376@cbox>
On 12/2/2015 10:07 AM, Christoffer Dall wrote:
> Hi Mario,
>
> On Wed, Nov 18, 2015 at 06:20:03PM -0800, Mario Smarduch wrote:
>> Also with tick accounting enabled, and periodic timer HZ set to 1000 no irq time
>> is reported. That's with running a ping flood - 1200 int/s, not sure why
>> wouldn't any irq time be reported? The other two modes report irq time as expected.
>>
>> On 11/18/2015 11:46 AM, Mario Smarduch wrote:
>>> Hello,
>>> I noticed sched clock accounting can be enabled when arch-timer is
>>> initialized. But arm64 doesn't appear to have 'HAVE_IRQ_TIME_ACCOUNTING'
>>> selected (as of mainline 4.4-rc1) and IRQ_TIME_ACCOUNTING can't be selected.
>>> After adding it to arch/arm64/Kconfig, option appears to work fine. Depending on
>>> need all accounting options are fine, but irq time accounting appears to be most
>>> preferable.
>>>
>>> Any thoughts? Is it fine to enable it?
>>>
> Is any of this related to KVM?
Indirectly, given the guest should yield same results. To be on the safe side I
ran the guest in all combinations (7) to confirm that's the case.
Also verified that guest time on host appears fine in all these configurations.
It takes extra effort to get the guest time as opposed to other modes.
- Mario
>
> -Christoffer
>
next prev parent reply other threads:[~2015-12-02 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 19:46 arm64 sched_clock cpu accounting Mario Smarduch
2015-11-19 2:20 ` Mario Smarduch
2015-12-02 18:07 ` Christoffer Dall
2015-12-02 23:42 ` Mario Smarduch [this message]
2015-12-03 9:29 ` Will Deacon
2015-12-03 18:26 ` Mario Smarduch
2015-12-03 18:45 ` Mario Smarduch
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=565F81D2.3060401@samsung.com \
--to=m.smarduch@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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 NNTP newsgroup(s).