KVM-RISCV Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: kvm-riscv@lists.infradead.org
Subject: [PATCH 5/6] riscv: Test for specific SBI implementation ID
Date: Fri, 1 Mar 2024 09:45:44 +0100	[thread overview]
Message-ID: <20240301-0f3547e2dadd07512851f808@orel> (raw)
In-Reply-To: <20240229124246.309304-6-cem@kernel.org>

On Thu, Feb 29, 2024 at 01:42:11PM +0100, cem at kernel.org wrote:
> From: Carlos Maiolino <cem@kernel.org>
> 
> Retrieve the ID from the SBI, and test it against the SBI_IMPLID enviroment
> variable.
> 
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> ---
>  riscv/sbi.c | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/riscv/sbi.c b/riscv/sbi.c
> index 8ad8f375..9daab9dc 100644
> --- a/riscv/sbi.c
> +++ b/riscv/sbi.c
> @@ -54,6 +54,16 @@ static void check_base(void)
>  	}
>  	report_prefix_pop();
>  
> +	report_prefix_push("sbi_impl_id");
> +	if (env_is_defined("SBI_IMPLID")) {
> +		ret = sbi_ecall(SBI_EXT_BASE, SBI_EXT_BASE_GET_IMP_ID,
> +				SBI_EXT_BASE, 0, 0, 0, 0, 0);
> +		expected = strtol(getenv("SBI_IMPLID"), NULL, 0);
> +
> +		gen_report(&ret, expected);

nit: keep this sequence of lines consistent to make it easier for
readers, i.e. always use

   expected = ...
   ret = sbi_ecal(...
   gen_report(...

> +	}
> +	report_prefix_pop();
> +
>  	report_prefix_push("probe_ext");
>  	if (env_is_defined("PROBE_EXT")) {
>  		expected = strtol(getenv("PROBE_EXT"), NULL, 0);
> -- 
> 2.43.2
>

Otherwise,

Reviewed-by: Andrew Jones <ajones@ventanamicro.com>


  reply	other threads:[~2024-03-01  8:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29 12:42 [PATCH 0/6] Add riscv tests to cover the base extension specs cem
2024-02-29 12:42 ` [PATCH 1/6] riscv: Add test to probe SBI Extension cem
2024-03-01  8:25   ` Andrew Jones
2024-02-29 12:42 ` [PATCH 2/6] riscv: Factor out environment variable check cem
2024-03-01  8:28   ` Andrew Jones
2024-03-04 10:52     ` Carlos Maiolino
2024-02-29 12:42 ` [PATCH 3/6] riscv: Implement test for architecture ID register cem
2024-03-01  8:31   ` Andrew Jones
2024-02-29 12:42 ` [PATCH 4/6] riscv: Enable gen_report() to print the wrong value in case of test failure cem
2024-03-01  8:43   ` Andrew Jones
2024-03-05  8:05     ` Carlos Maiolino
2024-03-05 12:16       ` Andrew Jones
2024-03-01  8:46   ` Andrew Jones
2024-02-29 12:42 ` [PATCH 5/6] riscv: Test for specific SBI implementation ID cem
2024-03-01  8:45   ` Andrew Jones [this message]
2024-02-29 12:42 ` [PATCH 6/6] riscv: Test for a SBI implementation ID range cem
2024-03-01  8:52   ` Andrew Jones
2024-02-29 14:05 ` [PATCH 0/6] Add riscv tests to cover the base extension specs Andrew Jones
2024-02-29 14:12   ` Carlos Maiolino
2024-02-29 15:03     ` Andrew Jones
2024-02-29 15:31       ` Carlos Maiolino

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=20240301-0f3547e2dadd07512851f808@orel \
    --to=ajones@ventanamicro.com \
    --cc=kvm-riscv@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox