All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ayan Kumar Halder <ayankuma@amd.com>
To: "Orzel, Michal" <michal.orzel@amd.com>,
	Ayan Kumar Halder <ayan.kumar.halder@amd.com>,
	<xen-devel@lists.xenproject.org>
Cc: <sstabellini@kernel.org>, <bertrand.marquis@arm.com>,
	<volodymyr_babchuk@epam.com>, <mark.brown@parrylabs.com>,
	<matthew.l.weber3@boeing.com>, <sookyung.ahn@boeing.com>
Subject: Re: [RFC PATCH v1] imagebuilder: Add a script to check the sanity of device tree
Date: Thu, 4 Sep 2025 15:16:43 +0100	[thread overview]
Message-ID: <587d2566-b451-4385-ba49-062eca1d2acd@amd.com> (raw)
In-Reply-To: <ce4c05ed-6fb0-4735-b0d5-ab264c5f946e@amd.com>

Hi,

On 01/09/2025 14:51, Ayan Kumar Halder wrote:
> Hi Michal,
>
> On 01/09/2025 14:17, Orzel, Michal wrote:
>>
>> On 01/09/2025 14:31, Ayan Kumar Halder wrote:
>>> Xen gives a panic if certain nodes are not present in the device 
>>> tree. In order
>>> to prevent this panic, scripts/dt_sanity.py is written so that it 
>>> checks if the
>>> node/s are present. If the node/s are not present, the script gives 
>>> an error.
>>>
>>> User is expected to run the script against the device tree before 
>>> booting Xen
>>> with dtb.
>>
One thing I forgot to mention is that as part of safety certification, 
we do need to do "Failure mode and error analysis". This means 
describing the scenarios in which Xen can fail to perform its regular 
functionality and coming up with prevention, detection and mitigation 
measures.

One can argue that the panics caused by system misconfiguration, are the 
most straightforward of all the errors. However, we do need to define 
prevention mechanisms to avoid these panics. For this particular 
failure, the prevention mechanism can be described as manually looking 
into the device tree to ensure that the nodes expected by Xen, are 
present. The script aims to provide a better alternative.

This script is not meant to catch all possible panics. However we do 
want to have such scripts and utilities wherever possible, and document 
them as part of our FMEA.

May be a safety expert can comment if the approach makes sense.

- Ayan




  reply	other threads:[~2025-09-04 14:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 12:31 [RFC PATCH v1] imagebuilder: Add a script to check the sanity of device tree Ayan Kumar Halder
2025-09-01 13:03 ` Andrew Cooper
2025-09-01 13:17 ` Orzel, Michal
2025-09-01 13:51   ` Ayan Kumar Halder
2025-09-04 14:16     ` Ayan Kumar Halder [this message]
2025-09-22 17:10 ` Ayan Kumar Halder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=587d2566-b451-4385-ba49-062eca1d2acd@amd.com \
    --to=ayankuma@amd.com \
    --cc=ayan.kumar.halder@amd.com \
    --cc=bertrand.marquis@arm.com \
    --cc=mark.brown@parrylabs.com \
    --cc=matthew.l.weber3@boeing.com \
    --cc=michal.orzel@amd.com \
    --cc=sookyung.ahn@boeing.com \
    --cc=sstabellini@kernel.org \
    --cc=volodymyr_babchuk@epam.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.