Hi,
I am referring to https://neoverse-reference-design.docs.arm.com/en/latest/features/ras/ras.ht... for RAS error injection on neoverse reference design platform.
I am referring to below steps : mount -t debugfs none /sys/kernel/debug # Step needed for Buildroot only echo 0x80020000 > /sys/kernel/debug/apei/einj/error_type echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-firmware-first echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-component echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-error-type echo 1 > /sys/kernel/debug/apei/einj/error_inject
I want to refer to kernel source driver which exposes attributes : sel-firmware-first , sel-component , sel-error-type. Also that driver must be doing the actual injections and registering sdei events with EL3 .
can I be advised where to look in for kernel sources ?
Regards Amit
+Rohit & Nishant.
________________________________ From: Nagal, Amit via TF-A tf-a@lists.trustedfirmware.org Sent: 13 September 2024 15:43 To: tf-a@lists.trustedfirmware.org tf-a@lists.trustedfirmware.org; support support@arm.com Subject: [TF-A] Kernel source for RAS error injection on neoverse reference design platform
Hi,
I am referring to https://neoverse-reference-design.docs.arm.com/en/latest/features/ras/ras.ht... for RAS error injection on neoverse reference design platform.
I am referring to below steps : mount -t debugfs none /sys/kernel/debug # Step needed for Buildroot only echo 0x80020000 > /sys/kernel/debug/apei/einj/error_type echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-firmware-first echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-component echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-error-type echo 1 > /sys/kernel/debug/apei/einj/error_inject
I want to refer to kernel source driver which exposes attributes : sel-firmware-first , sel-component , sel-error-type. Also that driver must be doing the actual injections and registering sdei events with EL3 .
can I be advised where to look in for kernel sources ?
Regards Amit -- TF-A mailing list -- tf-a@lists.trustedfirmware.org To unsubscribe send an email to tf-a-leave@lists.trustedfirmware.org
Hi Omkar, could you please assist Amit with his query?
Hi Amit, you will find the kernel source code in the same project you synced.
Thanks, Nishant
From: Olivier Deprez Olivier.Deprez@arm.com Date: Monday, 16 September 2024 at 8:59 AM To: Nagal, Amit amit.nagal@amd.com, Rohit Mathew Rohit.Mathew@arm.com, Nishant Sharma Nishant.Sharma@arm.com Cc: support support@arm.com, tf-a@lists.trustedfirmware.org tf-a@lists.trustedfirmware.org Subject: Re: Kernel source for RAS error injection on neoverse reference design platform +Rohit & Nishant.
________________________________ From: Nagal, Amit via TF-A tf-a@lists.trustedfirmware.org Sent: 13 September 2024 15:43 To: tf-a@lists.trustedfirmware.org tf-a@lists.trustedfirmware.org; support support@arm.com Subject: [TF-A] Kernel source for RAS error injection on neoverse reference design platform
Hi,
I am referring to https://neoverse-reference-design.docs.arm.com/en/latest/features/ras/ras.ht... for RAS error injection on neoverse reference design platform.
I am referring to below steps : mount -t debugfs none /sys/kernel/debug # Step needed for Buildroot only echo 0x80020000 > /sys/kernel/debug/apei/einj/error_type echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-firmware-first echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-component echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-error-type echo 1 > /sys/kernel/debug/apei/einj/error_inject
I want to refer to kernel source driver which exposes attributes : sel-firmware-first , sel-component , sel-error-type. Also that driver must be doing the actual injections and registering sdei events with EL3 .
can I be advised where to look in for kernel sources ?
Regards Amit -- TF-A mailing list -- tf-a@lists.trustedfirmware.org To unsubscribe send an email to tf-a-leave@lists.trustedfirmware.org
Hi Nishant / Omkar ,
I referred to the kernel sources from the manifest file . Can you please give a functional flow and the source files to refer to for FFH firmware first handling mode : 1. kernel registering sdei events with EL3 . 2. error injection in kernel. 3. kernel wait function for sdei events ( events sent from EL3 when interrupt is triggered against injected errors and handled by EL3 firmware). Regards Amit
From: Nishant Sharma Nishant.Sharma@arm.com Sent: Monday, September 16, 2024 1:50 PM To: Nagal, Amit amit.nagal@amd.com; Omkar Kulkarni Omkar.Kulkarni@arm.com Cc: support support@arm.com; tf-a@lists.trustedfirmware.org; Rohit Mathew Rohit.Mathew@arm.com; Olivier Deprez Olivier.Deprez@arm.com Subject: Re: Kernel source for RAS error injection on neoverse reference design platform
Hi Omkar, could you please assist Amit with his query?
Hi Amit, you will find the kernel source code in the same project you synced.
Thanks, Nishant
From: Olivier Deprez mailto:Olivier.Deprez@arm.com Date: Monday, 16 September 2024 at 8:59 AM To: Nagal, Amit mailto:amit.nagal@amd.com, Rohit Mathew mailto:Rohit.Mathew@arm.com, Nishant Sharma mailto:Nishant.Sharma@arm.com Cc: support mailto:support@arm.com, mailto:tf-a@lists.trustedfirmware.org mailto:tf-a@lists.trustedfirmware.org Subject: Re: Kernel source for RAS error injection on neoverse reference design platform +Rohit & Nishant.
________________________________________ From: Nagal, Amit via TF-A mailto:tf-a@lists.trustedfirmware.org Sent: 13 September 2024 15:43 To: mailto:tf-a@lists.trustedfirmware.org mailto:tf-a@lists.trustedfirmware.org; support mailto:support@arm.com Subject: [TF-A] Kernel source for RAS error injection on neoverse reference design platform Hi,
I am referring to https://neoverse-reference-design.docs.arm.com/en/latest/features/ras/ras.ht... for RAS error injection on neoverse reference design platform.
I am referring to below steps : mount -t debugfs none /sys/kernel/debug # Step needed for Buildroot only echo 0x80020000 > /sys/kernel/debug/apei/einj/error_type echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-firmware-first echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-component echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-error-type echo 1 > /sys/kernel/debug/apei/einj/error_inject
I want to refer to kernel source driver which exposes attributes : sel-firmware-first , sel-component , sel-error-type. Also that driver must be doing the actual injections and registering sdei events with EL3 .
can I be advised where to look in for kernel sources ?
Regards Amit -- TF-A mailing list -- mailto:tf-a@lists.trustedfirmware.org To unsubscribe send an email to mailto:tf-a-leave@lists.trustedfirmware.org
Hi Amit,
You can find the elaborative SDEI documentation here https://trustedfirmware-a.readthedocs.io/en/latest/components/sdei.html
The error injection code where the debugfs entries are defined can be found here https://gitlab.arm.com/infra-solutions/reference-design/platsw/linux/-/blob/...
Regards, Omkar
-----Original Message----- From: Nagal, Amit amit.nagal@amd.com Sent: Monday, September 16, 2024 10:21 PM To: Nishant Sharma Nishant.Sharma@arm.com; Omkar Kulkarni Omkar.Kulkarni@arm.com Cc: support support@arm.com; tf-a@lists.trustedfirmware.org; Rohit Mathew Rohit.Mathew@arm.com; Olivier Deprez Olivier.Deprez@arm.com Subject: RE: Kernel source for RAS error injection on neoverse reference design platform
Hi Nishant / Omkar ,
I referred to the kernel sources from the manifest file . Can you please give a functional flow and the source files to refer to for FFH firmware first handling mode :
- kernel registering sdei events with EL3 .
- error injection in kernel.
- kernel wait function for sdei events ( events sent from EL3 when interrupt
is triggered against injected errors and handled by EL3 firmware). Regards Amit
From: Nishant Sharma Nishant.Sharma@arm.com Sent: Monday, September 16, 2024 1:50 PM To: Nagal, Amit amit.nagal@amd.com; Omkar Kulkarni Omkar.Kulkarni@arm.com Cc: support support@arm.com; tf-a@lists.trustedfirmware.org; Rohit Mathew Rohit.Mathew@arm.com; Olivier Deprez Olivier.Deprez@arm.com Subject: Re: Kernel source for RAS error injection on neoverse reference design platform
Hi Omkar, could you please assist Amit with his query?
Hi Amit, you will find the kernel source code in the same project you synced.
Thanks, Nishant
From: Olivier Deprez mailto:Olivier.Deprez@arm.com Date: Monday, 16 September 2024 at 8:59 AM To: Nagal, Amit mailto:amit.nagal@amd.com, Rohit Mathew mailto:Rohit.Mathew@arm.com, Nishant Sharma mailto:Nishant.Sharma@arm.com Cc: support mailto:support@arm.com, mailto:tf- a@lists.trustedfirmware.org mailto:tf-a@lists.trustedfirmware.org Subject: Re: Kernel source for RAS error injection on neoverse reference design platform +Rohit & Nishant.
From: Nagal, Amit via TF-A mailto:tf-a@lists.trustedfirmware.org Sent: 13 September 2024 15:43 To: mailto:tf-a@lists.trustedfirmware.org mailto:tf- a@lists.trustedfirmware.org; support mailto:support@arm.com Subject: [TF-A] Kernel source for RAS error injection on neoverse reference design platform
Hi,
I am referring to https://neoverse-reference- design.docs.arm.com/en/latest/features/ras/ras.html#error-injection-via- kernel for RAS error injection on neoverse reference design platform.
I am referring to below steps : mount -t debugfs none /sys/kernel/debug # Step needed for Buildroot only echo 0x80020000 > /sys/kernel/debug/apei/einj/error_type echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-firmware-first echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-component echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-error-type echo 1 > /sys/kernel/debug/apei/einj/error_inject
I want to refer to kernel source driver which exposes attributes : sel-firmware- first , sel-component , sel-error-type. Also that driver must be doing the actual injections and registering sdei events with EL3 .
can I be advised where to look in for kernel sources ?
Regards Amit -- TF-A mailing list -- mailto:tf-a@lists.trustedfirmware.org To unsubscribe send an email to mailto:tf-a-leave@lists.trustedfirmware.org
Hi Omkar ,
Thanks for reply .
Referring https://gitlab.arm.com/infra-solutions/reference-design/platsw/linux/-/blob/... I see arm_cpu_einj() is not called in case of FIRMWARE_FIRST selection . If so, where is error injection done in case of FIRMWARE_FIRST selection ?
Could you please share some details about functional flow in linux driver from point of view of sdei event registration, error injection and sdei event reception once EL3 receives interrupt and notifies lower layer SW.
Regards Amit
-----Original Message----- From: Omkar Kulkarni Omkar.Kulkarni@arm.com Sent: Wednesday, September 18, 2024 3:54 PM To: Nagal, Amit amit.nagal@amd.com; Nishant Sharma Nishant.Sharma@arm.com Cc: support support@arm.com; tf-a@lists.trustedfirmware.org; Rohit Mathew Rohit.Mathew@arm.com; Olivier Deprez Olivier.Deprez@arm.com Subject: RE: Kernel source for RAS error injection on neoverse reference design platform
Hi Amit,
You can find the elaborative SDEI documentation here https://trustedfirmware-a.readthedocs.io/en/latest/components/sdei.html
The error injection code where the debugfs entries are defined can be found here https://gitlab.arm.com/infra-solutions/reference-design/platsw/linux/-/blob/...
Regards, Omkar
-----Original Message----- From: Nagal, Amit amit.nagal@amd.com Sent: Monday, September 16, 2024 10:21 PM To: Nishant Sharma Nishant.Sharma@arm.com; Omkar Kulkarni Omkar.Kulkarni@arm.com Cc: support support@arm.com; tf-a@lists.trustedfirmware.org; Rohit Mathew Rohit.Mathew@arm.com; Olivier Deprez Olivier.Deprez@arm.com Subject: RE: Kernel source for RAS error injection on neoverse reference design platform
Hi Nishant / Omkar ,
I referred to the kernel sources from the manifest file . Can you please give a functional flow and the source files to refer to for FFH firmware first handling mode :
- kernel registering sdei events with EL3 .
- error injection in kernel.
- kernel wait function for sdei events ( events sent from EL3 when
interrupt is triggered against injected errors and handled by EL3 firmware). Regards Amit
From: Nishant Sharma Nishant.Sharma@arm.com Sent: Monday, September 16, 2024 1:50 PM To: Nagal, Amit amit.nagal@amd.com; Omkar Kulkarni Omkar.Kulkarni@arm.com Cc: support support@arm.com; tf-a@lists.trustedfirmware.org; Rohit Mathew Rohit.Mathew@arm.com; Olivier Deprez Olivier.Deprez@arm.com Subject: Re: Kernel source for RAS error injection on neoverse reference design platform
Hi Omkar, could you please assist Amit with his query?
Hi Amit, you will find the kernel source code in the same project you synced.
Thanks, Nishant
From: Olivier Deprez mailto:Olivier.Deprez@arm.com Date: Monday, 16 September 2024 at 8:59 AM To: Nagal, Amit mailto:amit.nagal@amd.com, Rohit Mathew mailto:Rohit.Mathew@arm.com, Nishant Sharma mailto:Nishant.Sharma@arm.com Cc: support mailto:support@arm.com, mailto:tf- a@lists.trustedfirmware.org mailto:tf-a@lists.trustedfirmware.org Subject: Re: Kernel source for RAS error injection on neoverse reference design platform +Rohit & Nishant.
From: Nagal, Amit via TF-A mailto:tf-a@lists.trustedfirmware.org Sent: 13 September 2024 15:43 To: mailto:tf-a@lists.trustedfirmware.org <mailto:tf- a@lists.trustedfirmware.org>; support mailto:support@arm.com Subject: [TF-A] Kernel source for RAS error injection on neoverse reference design platform
Hi,
I am referring to https://neoverse-reference- design.docs.arm.com/en/latest/features/ras/ras.html#error-injection-vi a- kernel for RAS error injection on neoverse reference design platform.
I am referring to below steps : mount -t debugfs none /sys/kernel/debug # Step needed for Buildroot only echo 0x80020000 > /sys/kernel/debug/apei/einj/error_type echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-firmware-first echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-component echo 1 > /sys/kernel/debug/apei/einj/oem-einj/sel-error-type echo 1 > /sys/kernel/debug/apei/einj/error_inject
I want to refer to kernel source driver which exposes attributes : sel-firmware- first , sel-component , sel-error-type. Also that driver must be doing the actual injections and registering sdei events with EL3 .
can I be advised where to look in for kernel sources ?
Regards Amit -- TF-A mailing list -- mailto:tf-a@lists.trustedfirmware.org To unsubscribe send an email to mailto:tf-a-leave@lists.trustedfirmware.org
tf-a@lists.trustedfirmware.org