linux-kernel - Re: [PATCH v2] timers: Recalculate next timer interrupt only when necessary

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <c7a5015a-2b93-17d2-29bc-cd03e40cc09c@windriver.com>
Date:   Fri, 9 Jul 2021 13:37:11 +0800
From:   He Zhe <zhe.he@...driver.com>
To:     Frederic Weisbecker <frederic@...nel.org>
Cc:     anna-maria@...utronix.de, linux-kernel@...r.kernel.org,
        tglx@...utronix.de
Subject: Re: [PATCH v2] timers: Recalculate next timer interrupt only when
 necessary



On 7/8/21 11:36 PM, Frederic Weisbecker wrote:
> On Thu, Jul 08, 2021 at 02:43:01PM +0800, He Zhe wrote:
>> Hi,
>>
>> Ever since this commit merged in, when nohz_full enabled, the counts of arch_timer interrupt on arm64 arches keep increasing on cores that have been isolated. This can be reproduced on several arm64 boards. After reverting the commit, the counts would stop increasing after boot. my .config is attached.
>>
>> root@...uarm64:~# uname -a
>> Linux qemuarm64 5.13.0 #1 SMP PREEMPT Mon Jul 5 07:11:27 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux
>> root@...uarm64:~# cat /proc/cmdline
>> root=/dev/vda rw  mem=2048M ip=dhcp console=ttyAMA0 console=hvc0  earlyprintk isolcpus=1-5 nohz_full=1-5 rcu_nocbs=1-5
>> root@...uarm64:~# cat /proc/interrupts
> And I'm not observing that on default aarch64 on qemu either.
> Are you emulating a specific machine?

Here is my qemu configuration.

qemu-system-aarch64 --version
QEMU emulator version 6.0.0
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers

qemu-system-aarch64 -device virtio-net-device,netdev=net0,mac=52:54:00:12:35:02 -netdev user,id=net0,hostfwd=tcp::2222-:22,hostfwd=tcp::2323-:23,tftp=/qemuarm64 -object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0 -drive id=disk0,file=/qemuarm64/qemuarm64.rootfs.ext4,if=none,format=raw -device virtio-blk-device,drive=disk0 -device qemu-xhci -device usb-tablet -device usb-kbd  -machine virt -cpu cortex-a57 -smp 4 -m 2048  -smp 6 -m 2048 -serial mon:stdio -serial null -nographic -device VGA,edid=on -kernel /qemuarm64/Image.bin -append 'root=/dev/vda rw  mem=2048M ip=dhcp console=ttyAMA0 console=hvc0 earlyprintk isolcpus=1-5 nohz_full=1-5 rcu_nocbs=1-5'

>
> Can you enable the following trace events and send me the output from
> one of the isolated CPU trace, say CPU 3 for example:

output_to_send is attached.
I can confirm that during the sleep the count of arch_timer increases one on each isolated core.

Thanks,
Zhe

>
>
> DIR=/sys/kernel/debug/tracing
>
> echo 1 > $DIR/events/irq/enable
> echo 1 > $DIR/events/sched/sched_switch/enable
> echo 1 > $DIR/events/irq_vectors/enable
> echo 1 > $DIR/events/workqueue/workqueue_execute_start/enable
> echo 1 > $DIR/events/timer/hrtimer_expire_entry/enable
> echo 1 > $DIR/events/timer/timer_expire_entry/enable
> echo 1 > $DIR/events/timer/tick_stop/enable
> sleep 10
> cat $DIR/per_cpu/cpu0/trace > ~/output_to_send




View attachment "output_to_send" of type "text/plain" (2194756 bytes)