linux-kernel - Re: Re: [PATCH v3 0/2] Add driver for Intel Over-Clocking Watchdog

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: <20250603094329.125537-1-diogo.ivo@siemens.com>
Date: Tue,  3 Jun 2025 10:43:29 +0100
From: Diogo Ivo <diogo.ivo@...mens.com>
To: andy.shevchenko@...il.com
Cc: benedikt.niedermayr@...mens.com,
	diogo.ivo@...mens.com,
	jan.kiszka@...mens.com,
	lenb@...nel.org,
	linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	linux-watchdog@...r.kernel.org,
	linux@...ck-us.net,
	mika.westerberg@...ux.intel.com,
	rafael@...nel.org,
	wim@...ux-watchdog.org
Subject: Re: Re: [PATCH v3 0/2] Add driver for Intel Over-Clocking Watchdog

Hi Andy,

> This doesn't describe why we need the driver. We have established ACPI WDAT
> table. Can't you utilise it by providing in the firmware?

You are right, I did not make that clear.

When you say we have established WDAT table do you mean that this should be the
mechanism that we use going forward to control watchdogs in ACPI platforms
generally or that you know that the WDAT for this specific watchdog is present
in the firmware?

I wrote the driver because on the two platforms I have access to (a fairly
recent LG Gram with an i7 1260p and a Siemens BX51A) by delving into the
BIOS options I was not able to find a toggle for them to provide a WDAT table
for this watchdog. In fact, on the LG Gram by searching we can get it to pass
us a WDAT table but for the iTCO watchdog (at least that is what I gathered
from my testing).

This means that to the best of my knowledge there are platforms that do not
provide a WDAT table for the Over-Clocking Watchdog which then makes this
driver necessary.

However I am not an expert on this topic so if there are things that I am
missing I would be happy to work on a better approach.

Thanks,
Diogo