dead loops, read HPET directly if panic in progress.
Signed-off-by: Tony W Wang-oc
---
arch/x86/kernel/hpet.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
index c96ae8fee95e..ecadd0698d6a 100644
--- a/arch/x86/kernel/hpet.c
+++ b/arch/x86/ke
On 2024/5/29 06:12, Thomas Gleixner wrote:
[这封邮件来自外部发件人 谨防风险]
On Tue, May 28 2024 at 07:18, Dave Hansen wrote:
On 5/27/24 23:38, Tony W Wang-oc wrote:
...> diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
index c96ae8fee95e..ecadd0698d6a 100644
--- a/arch/x86/kernel/hpe
On 2024/5/29 12:39, Tony W Wang-oc wrote:
On 2024/5/29 06:12, Thomas Gleixner wrote:
[这封邮件来自外部发件人 谨防风险]
On Tue, May 28 2024 at 07:18, Dave Hansen wrote:
On 5/27/24 23:38, Tony W Wang-oc wrote:
...> diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
index c96ae8fee
On 2024/5/29 15:45, Thomas Gleixner wrote:
[这封邮件来自外部发件人 谨防风险]
On Wed, May 29 2024 at 14:44, Tony W Wang-oc wrote:
Actually, this scenario is what this patch is trying to solve.
We encountered hpet_lock deadlock from the call path of the MCE handler,
and this hpet_lock deadlock scenario
On 2024/5/29 15:42, Thomas Gleixner wrote:
[这封邮件来自外部发件人 谨防风险]
Linus!
On Tue, May 28 2024 at 16:22, Linus Torvalds wrote:
On Tue, 28 May 2024 at 15:12, Thomas Gleixner wrote:
I see the smiley, but yeah, I don't think we really care about it.
Indeed. But the same problem exists on other
On 2024/6/5 17:36, Borislav Petkov wrote:
[这封邮件来自外部发件人 谨防风险]
On Wed, Jun 05, 2024 at 02:23:32PM +0800, Tony W Wang-oc wrote:
After MCE has occurred, it is possible for the MCE handler to execute the
add_taint() function without panic. For example, the fake_panic is
configured
On 2024/6/5 19:33, Borislav Petkov wrote:
[这封邮件来自外部发件人 谨防风险]
On Wed, Jun 05, 2024 at 06:10:07PM +0800, Tony W Wang-oc wrote:
It may also happen without setting fake_panic, such as an MCE error of the
UCNA/SRAO type occurred?
Which types exactly do you mean when you're looking a
On 2024/6/5 23:51, Luck, Tony wrote:
[这封邮件来自外部发件人 谨防风险]
Which types exactly do you mean when you're looking at the severities[]
array in severity.c?
And what scenario are you talking about?
To get an #MC exception and detect only UCNA/SRAO errors? Can that even
happen on any hardware?
On 2024/5/29 06:12, Thomas Gleixner wrote:
[这封邮件来自外部发件人 谨防风险]
On Tue, May 28 2024 at 07:18, Dave Hansen wrote:
On 5/27/24 23:38, Tony W Wang-oc wrote:
...> diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
index c96ae8fee95e..ecadd0698d6a 100644
--- a/arch/x86/kernel/hpe
