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: <Y0V3Snlqvz2+1UUQ@hirez.programming.kicks-ass.net>
Date:   Tue, 11 Oct 2022 16:01:46 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Zhang Rui <rui.zhang@...el.com>
Cc:     Dave Hansen <dave.hansen@...el.com>,
        Feng Tang <feng.tang@...el.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        "H . Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org, tim.c.chen@...el.com,
        Xiongfeng Wang <wangxiongfeng2@...wei.com>,
        Yu Liao <liaoyu15@...wei.com>
Subject: Re: [PATCH] x86/tsc: Extend the watchdog check exemption to 4S/8S
 machine

On Tue, Oct 11, 2022 at 09:33:26PM +0800, Zhang Rui wrote:

> topology_max_packages() or variable logical_packages can tell the
> maximum packages.
> But this check_system_tsc_reliable() is done in early boot phase where
> we have boot cpu only. And the cpu topology is not built up at this
> stage.

Is there a problem with disabling the TSC watchdog later in boot --
after SMP bringup for example?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ