linux-kernel - Re: [PATCH V2] cpustat: print watchdog time and statistics of soft and hard interrupts in soft lockup scenes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <c169f207-2f88-c457-2f08-f5da546db113@huawei.com>
Date:   Fri, 23 Aug 2019 15:26:45 +0800
From:   c00423981 <caomeng5@...wei.com>
To:     Peter Zijlstra <peterz@...radead.org>
CC:     <tglx@...utronix.de>, <mingo@...hat.com>, <hpa@...or.com>,
        <x86@...nel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2] cpustat: print watchdog time and statistics of soft
 and hard interrupts in soft lockup scenes



On 2019/8/23 0:14, Peter Zijlstra wrote:
> On Thu, Aug 22, 2019 at 07:58:37PM +0800, c00423981 wrote:
> 
>> V1->V2
>> - fix the broken interfaces: get_idle_time and get_iowait_time
> 
>> +	else if (index == CPUTIME_IOWAIT)
>> +		time = get_iowait_time(kcs, cpu);
> 
> I'm confused; isn't that still reporting per-cpu iowait, which is still
> complete garbage?
> 
> 

Yes, I understand that these two interfaces(nr_iowait_cpu and nr_iowait) will
use nonsensical data. Thanks for your answer very much.

By the way, are there an alternative about these two interfaces?
Looking forward to your reply.