From: Frederic Weisbecker <fweisbec@gmail•com>
To: Peter Zijlstra <peterz@infradead•org>
Cc: Wanpeng Li <kernellwp@gmail•com>,
Jesper Dangaard Brouer <brouer@redhat•com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
linux-mm <linux-mm@kvack•org>,
Mel Gorman <mgorman@techsingularity•net>,
Tariq Toukan <tariqt@mellanox•com>,
Tariq Toukan <ttoukan.linux@gmail•com>,
Rik van Riel <riel@redhat•com>,
Thomas Gleixner <tglx@linutronix•de>,
Ingo Molnar <mingo@kernel•org>
Subject: Re: Bisected softirq accounting issue in v4.11-rc1~170^2~28
Date: Tue, 28 Mar 2017 15:06:04 +0200 [thread overview]
Message-ID: <20170328130602.GA4216@lerouge> (raw)
In-Reply-To: <20170328122642.dhw2zkjbghfw4fzn@hirez.programming.kicks-ass.net>
On Tue, Mar 28, 2017 at 02:26:42PM +0200, Peter Zijlstra wrote:
> On Tue, Mar 28, 2017 at 06:34:52PM +0800, Wanpeng Li wrote:
> >
> > sched_clock_cpu(cpu) should be converted from cputime to ns.
>
> Uhm, no. sched_clock_cpu() returns u64 in ns.
Yes, and most of the cputime_t have been converted to u64 so there
should be no such conversion issue between u64 and cputime_t anymore.
Perhaps my commit has another side effect on softirq time accounting,
I'll see if I can reproduce.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack•org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack•org"> email@kvack•org </a>
next prev parent reply other threads:[~2017-03-28 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 8:14 Bisected softirq accounting issue in v4.11-rc1~170^2~28 Jesper Dangaard Brouer
2017-03-28 10:34 ` Wanpeng Li
2017-03-28 11:49 ` Jesper Dangaard Brouer
2017-03-28 12:26 ` Peter Zijlstra
2017-03-28 13:06 ` Frederic Weisbecker [this message]
2017-03-28 13:18 ` Jesper Dangaard Brouer
2017-03-28 14:34 ` Frederic Weisbecker
2017-03-28 15:23 ` Jesper Dangaard Brouer
2017-03-28 21:11 ` Frederic Weisbecker
2017-03-29 9:30 ` Jesper Dangaard Brouer
2017-03-29 13:13 ` 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=20170328130602.GA4216@lerouge \
--to=fweisbec@gmail$(echo .)com \
--cc=brouer@redhat$(echo .)com \
--cc=kernellwp@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=mgorman@techsingularity$(echo .)net \
--cc=mingo@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=peterz@infradead$(echo .)org \
--cc=riel@redhat$(echo .)com \
--cc=tariqt@mellanox$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=ttoukan.linux@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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