From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx2.zhaoxin.com (mx2.zhaoxin.com [203.110.167.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BF43E13AA5E for ; Thu, 6 Jun 2024 08:44:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=203.110.167.99 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1717663500; cv=none; b=NGfDVD9qLwZmo0HaFJXy3qzgTlkuH+W0i4sygX80s/bb4lT/3dqiJFf6Wcz/vR/2nLwd6gOVjcewERvKUm7HEL3/m6Is9vy3qiwDcaKX8UA6cibgn6ahdCixdKqkXZyr49W79hZSJbkVPxjuGRD8e7dpvFe2lxop9PLn/MKPjnc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1717663500; c=relaxed/simple; bh=cXuF/BWQZ89YFbsWT4c4SuCikNyWWk9/fkG6XTn4U90=; h=Message-ID:Date:MIME-Version:Subject:To:CC:References:From: In-Reply-To:Content-Type; b=LVx9vDMq23fNyvvUYb96vt0cRBA9nf/jJjQtSRvF6WMjvAMTDT0+W6eiyyLDqoY/6JiTThKO+4liLqJ2h564gNtoD6/+WWKeMSpvYqvWnjaTxPaVuqv2BZBnX/90qH6xTgSgLaT7sEIBKebGVv0iuFv3jrIBVpbgLpix/Hg3blc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=zhaoxin.com; spf=pass smtp.mailfrom=zhaoxin.com; arc=none smtp.client-ip=203.110.167.99 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=zhaoxin.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=zhaoxin.com X-ASG-Debug-ID: 1717663487-1eb14e15751a540001-PleebU Received: from ZXSHMBX1.zhaoxin.com (ZXSHMBX1.zhaoxin.com [10.28.252.163]) by mx2.zhaoxin.com with ESMTP id ZMf1DOmNJyk7ZEa1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 06 Jun 2024 16:44:47 +0800 (CST) X-Barracuda-Envelope-From: TonyWWang-oc@zhaoxin.com X-Barracuda-RBL-Trusted-Forwarder: 10.28.252.163 Received: from ZXBJMBX03.zhaoxin.com (10.29.252.7) by ZXSHMBX1.zhaoxin.com (10.28.252.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.27; Thu, 6 Jun 2024 16:44:46 +0800 Received: from [10.32.65.162] (10.32.65.162) by ZXBJMBX03.zhaoxin.com (10.29.252.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.1.2507.27; Thu, 6 Jun 2024 16:44:44 +0800 X-Barracuda-RBL-Trusted-Forwarder: 10.28.252.163 Message-ID: X-Barracuda-RBL-Trusted-Forwarder: 10.32.65.162 Date: Thu, 6 Jun 2024 16:44:38 +0800 Precedence: bulk X-Mailing-List: linux-hardening@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] x86/hpet: Read HPET directly if panic in progress To: "Luck, Tony" , Borislav Petkov X-ASG-Orig-Subj: Re: [PATCH] x86/hpet: Read HPET directly if panic in progress CC: Thomas Gleixner , Linus Torvalds , "Hansen, Dave" , "mingo@redhat.com" , "dave.hansen@linux.intel.com" , "x86@kernel.org" , "hpa@zytor.com" , "keescook@chromium.org" , "gpiccoli@igalia.com" , "mat.jonczyk@o2.pl" , "rdunlap@infradead.org" , "alexandre.belloni@bootlin.com" , "mario.limonciello@amd.com" , "yaolu@kylinos.cn" , "bhelgaas@google.com" , "justinstitt@google.com" , "linux-kernel@vger.kernel.org" , "linux-hardening@vger.kernel.org" , "CobeChen@zhaoxin.com" , "TimGuo@zhaoxin.com" , "LeoLiu-oc@zhaoxin.com" References: <20240528063836.5248-1-TonyWWang-oc@zhaoxin.com> <50fc1bd3-909e-41c4-a991-9d81e32ef92c@intel.com> <87wmnda8mc.ffs@tglx> <87le3t9i8c.ffs@tglx> <0aff3f62-a8a5-4358-ae3f-2ded339aface@zhaoxin.com> <20240605093609.GCZmAxidNIBP5bkDcX@fat_crate.local> <20240605113323.GFZmBNA7ec2s191_2w@fat_crate.local> <46741fad-425c-4ed2-97be-3f2679da63eb@zhaoxin.com> Content-Language: en-US From: Tony W Wang-oc In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-ClientProxiedBy: ZXSHCAS2.zhaoxin.com (10.28.252.162) To ZXBJMBX03.zhaoxin.com (10.29.252.7) X-Barracuda-Connect: ZXSHMBX1.zhaoxin.com[10.28.252.163] X-Barracuda-Start-Time: 1717663487 X-Barracuda-Encrypted: ECDHE-RSA-AES128-GCM-SHA256 X-Barracuda-URL: https://10.28.252.36:4443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at zhaoxin.com X-Barracuda-Scan-Msg-Size: 1311 X-Barracuda-BRTS-Status: 1 X-Barracuda-Bayes: INNOCENT GLOBAL 0.0000 1.0000 -2.0210 X-Barracuda-Spam-Score: -2.02 X-Barracuda-Spam-Status: No, SCORE=-2.02 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.125870 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 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? >>> >> >> Yes, I mean an #MC exception happened and detect only like SRAO errors >> like below: >> >> MCESEV( >> AO, "Action optional: memory scrubbing error", >> SER, MASK(MCI_UC_AR|MCACOD_SCRUBMSK, >> MCI_STATUS_UC|MCACOD_SCRUB) >> ), >> MCESEV( >> AO, "Action optional: last level cache writeback error", >> SER, MASK(MCI_UC_AR|MCACOD, MCI_STATUS_UC|MCACOD_L3WB) >> ), >> >> I think these errors are actually encountered on some platforms that >> support these type of errors report to the #MC. > > Intel servers from Nehalem through Cascade Lake reported memory controller > patrol scrub uncorrected error with #MC and SRAO signature. > > Icelake and newer use CMCI with a UCNA signature. > I have a question, does Intel use #MC to report UCNA errors? Sincerely TonyWWang-oc