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: <F7F9B0BE3E9BD449B110D0B1CEF6CAEF04FEB0F5@ABGEX01E.abg.fsc.net>
Date:	Thu, 22 Mar 2007 17:46:15 +0100
From:	"Cestonaro, Thilo \(external\)" 
	<Thilo.Cestonaro.external@...itsu-siemens.com>
To:	"Lee Revell" <rlrevell@...-job.com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: RE: how can I touch softlockup watchdog on all cpus?

> Sounds like you have a fundamentally incompatible set of requirements.

Sounds so yep :)

> Why do you need the softlockup watchdog if you intend to induce soft
> lockups on purpose?

It's a condition of a customer of us, so I can't change it.

But it happens not often that my part is used. So I thought there is a mechanism to disable or reset the watchdog
because it is a legal pause for it. And there is one "touch_softlockup_watchdog()", that does what I want,
BUT just for the current cpu. And so the watchdog blats from the other cpu.

Thilo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ