[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2] docs: fusa: Add Assumption of Use (AoU)


  • To: Julien Grall <julien@xxxxxxx>, Ayan Kumar Halder <ayan.kumar.halder@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx
  • From: Ayan Kumar Halder <ayankuma@xxxxxxx>
  • Date: Wed, 11 Sep 2024 12:24:54 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=amd.com; dmarc=pass action=none header.from=amd.com; dkim=pass header.d=amd.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=UO8QjgI9SO5lOJ1K6gSEFto5jY/cbxDS0TLAwqJyUvo=; b=tpebARlV6JeIH9PRqJeHuEbKxmeTZsBZxjVHZkAJSZPrLAkJhqUVyCtHK2Y1v6LWUIDFTMiMwdInkdJ5ENNVIagtA4dCn5VrWko9axc5aWErTenBYB0iLvy4M4ldxg5HOfq9YzAwgD66/z0AQmUNg4aJVg7YjZTZrqWIowA/zCNsXHfpBfmtHhz01E6r7JuRw6BREOy3cK6W4IaP2OsfBFV6ydLgScTKhG6c4vdqqKLxtJFOXRiJLL+Mp0DxmSGZJ5aMYnJsrUuLMm/dpyQE7CahQtXTN9xgByXgi/bZjuJPgmzTr0H10+lSQW7tcbTxK+KBCiTTASJ3MqMSUaDDdw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=Yzdc2iEfyeH+b2dXEjiFsV+hjxVmZHzTAt8L+pm4armP76bWWup6T8XXTB6eXC1gOhvfEGMMol7YR5V/GvTB+QceDmWr0J9gGM/Nk24feRwhqFxwTrPDzXz+h3bwl91qsqagwQTx46EUOFQQYHT/MvprnME3dleWg/ru7oPEobhpK9yJavTPGZCRJIv02KR/tFKBfTmnZoC3TLQgSbCpPG39+10R1PoqMJuSEE+K1jKe6hlFXK+lPm2n2TxhhkehGjG/paVhFJIfrBXWBVQnJNLY0IiiOyqIDVsk1EhKOUtOIwvIBJURJUjqbSzIOuTknXhuyr1kh1iCkzEmCkk7CQ==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=amd.com;
  • Cc: Michal Orzel <michal.orzel@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Bertrand Marquis <bertrand.marquis@xxxxxxx>, Artem Mygaiev <artem_mygaiev@xxxxxxxx>, Hisao Munakata <hisao.munakata.vt@xxxxxxxxxxx>
  • Delivery-date: Wed, 11 Sep 2024 11:25:25 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>


On 11/09/2024 10:55, Julien Grall wrote:
Hi,
Hi,

On 11/09/2024 10:44, Ayan Kumar Halder wrote:
From: Michal Orzel <michal.orzel@xxxxxxx>

AoU are the assumptions Xen relies on other components (eg platform, domains) to fulfill its requirements. In our case, platform means a combination of
hardware, firmware and bootloader.

We have defined AoU in the intro.rst and added AoU for the generic timer.

Signed-off-by: Michal Orzel <michal.orzel@xxxxxxx>
Signed-off-by: Ayan Kumar Halder <ayan.kumar.halder@xxxxxxx>
---
Changes from :-

v1 - 1. Removed the part of requirement which states that Xen exposes the
frequency of the system timer by reading the "clock-frequency" property.

2. Added a rationale for AoU.

3. Reworded the AoU.

  .../reqs/design-reqs/arm64/generic-timer.rst  | 24 ++++++++++++++++++-
  docs/fusa/reqs/intro.rst                      | 10 ++++++++
  2 files changed, 33 insertions(+), 1 deletion(-)

diff --git a/docs/fusa/reqs/design-reqs/arm64/generic-timer.rst b/docs/fusa/reqs/design-reqs/arm64/generic-timer.rst
index f2a0cd7fb8..86d84a3c40 100644
--- a/docs/fusa/reqs/design-reqs/arm64/generic-timer.rst
+++ b/docs/fusa/reqs/design-reqs/arm64/generic-timer.rst
@@ -30,7 +30,7 @@ Read system counter frequency
    Description:
  Xen shall expose the frequency of the system counter to the domains in
-CNTFRQ_EL0 register and/or domain device tree's "clock-frequency" property.
+CNTFRQ_EL0 register.

This either wants to be split or explained in the commit message.

Yes, I will explain this in the commit message. Does the following sound fine ?

```

docs: fusa: Add Assumption of Use (AoU)

AoU are the assumptions that Xen relies on other components (eg platform, domains)
to fulfill its requirements. In our case, platform means a combination of
hardware, firmware and bootloader.

We have defined AoU in the intro.rst and added AoU for the generic timer.

Also, fixed a requirement to denote that Xen shall **not** expose the system counter frequency via the "clock-frequency" device tree property. The reason being the device tree documentation strongly discourages the use of this peoperty. Further if the "clock-frequency" is exposed, then it overrides the value programmed in the CNTFRQ_EL0 register.

So, the frequency shall be exposed via the CNTFRQ_EL0 register only and consequently there is an assumption on the platform to program the register correctly.

```

- Ayan



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.