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 for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <TYCPR01MB6160551BCB54E2AC118FF988E98E9@TYCPR01MB6160.jpnprd01.prod.outlook.com>
Date:   Fri, 5 Nov 2021 07:27:41 +0000
From:   "ishii.shuuichir@...itsu.com" <ishii.shuuichir@...itsu.com>
To:     "'rafael@...nel.org'" <rafael@...nel.org>,
        "'lenb@...nel.org'" <lenb@...nel.org>,
        "'inux-acpi@...r.kernel.org'" <inux-acpi@...r.kernel.org>,
        "'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
        "'orenzo.pieralisi@....com'" <orenzo.pieralisi@....com>,
        "'guohanjun@...wei.com'" <guohanjun@...wei.com>,
        "'sudeep.holla@....com'" <sudeep.holla@....com>,
        "'inux-arm-kernel@...ts.infradead.org'" 
        <inux-arm-kernel@...ts.infradead.org>
CC:     "ishii.shuuichir@...itsu.com" <ishii.shuuichir@...itsu.com>
Subject: [RFC]Development of the AEST(Arm Error Source Table) driver

Hello,
to all concerned with ACPI (arm64) processing implementation,

We are considering to develop an AEST driver.

Currently, the following has been posted as an RFC patch [1] for the AEST driver.
[1] https://lore.kernel.org/linux-acpi/1562086280-5351-1-git-send-email-baicar@os.amperecomputing.com/

We sent an email to the developer of this patch to check the current status of the AEST driver.
Unfortunately, there was no response, so we would like to make the necessary feature updates.

We have two questions.

Question 1: About the update features.
Since [1] is implemented based on the ACPI for the Arm8 RAS Extensions 1.0 specification, 
we are thinking of updating it based on the latest specification. 
Any comments would be appreciated.

 (a) ACPI for the Arm8 RAS Extensions v.1.1[2] support
 (b) Register addition and its dumping process to comply with ARMv8.4 RAS Extensions
 (c) Addition of processing for each missing error type.
   
  [2] https://developer.arm.com/documentation/den0085/latest
    
Question 2: About the directory to be placed
AEST will be ARM specification.Is there any problem that the directory
to store the main source (aest.c) is under drivers/acpi/arm64/?

If you have any comments, please let me know.

Best regards,
Shuuichirou.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ