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 V2 5/6] riscv: Test for specific SBI implementation ID
Date: Wed, 13 Mar 2024 12:23:38 +0100	[thread overview]
Message-ID: <20240313-852a2b0acf59e8205d0ec9d0@orel> (raw)
In-Reply-To: <20240313084644.277426-6-cem@kernel.org>

On Wed, Mar 13, 2024 at 09:46:23AM +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>
> Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
> ---
> V2:
> 	- Update commit description to fit 70 chars
> 	- Move sbi_ecall() after expected assignment to make consistent with
> 	  other tests
> 
>  riscv/sbi.c | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/riscv/sbi.c b/riscv/sbi.c
> index bc0f5c68..65492fd6 100644
> --- a/riscv/sbi.c
> +++ b/riscv/sbi.c
> @@ -51,6 +51,15 @@ static void check_base(void)
>  	}
>  	report_prefix_pop();
>  
> +	report_prefix_push("sbi_impl_id");
> +	if (env_or_skip("SBI_IMPLID")) {

Let's spell this SBI_IMPL_ID (just like its report prefix)

> +		expected = strtol(getenv("SBI_IMPLID"), NULL, 0);
> +		ret = sbi_ecall(SBI_EXT_BASE, SBI_EXT_BASE_GET_IMP_ID,
> +				SBI_EXT_BASE, 0, 0, 0, 0, 0);

This should be

  sbi_ecall(SBI_EXT_BASE, SBI_EXT_BASE_GET_IMP_ID, 0, ...)

> +		gen_report(&ret, 0, expected);
> +	}
> +	report_prefix_pop();
> +
>  	report_prefix_push("probe_ext");
>  	expected = getenv("PROBE_EXT") ? strtol(getenv("PROBE_EXT"), NULL, 0) : 1;
>  	ret = sbi_ecall(SBI_EXT_BASE, SBI_EXT_BASE_PROBE_EXT, SBI_EXT_BASE, 0, 0, 0, 0, 0);
> -- 
> 2.44.0
>

Thanks,
drew


  reply	other threads:[~2024-03-13 11:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-13  8:46 [PATCH V2 0/6] Add riscv tests to cover the base extension specs cem
2024-03-13  8:46 ` [PATCH V2 1/6] riscv: Add test to probe SBI Extension cem
2024-03-13 11:06   ` Andrew Jones
2024-03-13  8:46 ` [PATCH V2 2/6] riscv: Factor out environment variable check and report generation cem
2024-03-13 11:11   ` Andrew Jones
2024-03-13  8:46 ` [PATCH V2 3/6] riscv: Implement test for architecture ID register cem
2024-03-13 11:21   ` Andrew Jones
2024-03-13  8:46 ` [PATCH V2 4/6] riscv: Enable gen_report() to print the wrong value in case of failure cem
2024-03-13 11:19   ` Andrew Jones
2024-03-13  8:46 ` [PATCH V2 5/6] riscv: Test for specific SBI implementation ID cem
2024-03-13 11:23   ` Andrew Jones [this message]
2024-03-13 11:28     ` Andrew Jones
2024-03-13  8:46 ` [PATCH 6/6] riscv: Add a wrapper to call sbi_ecall for base extension cem
2024-03-13 11:33   ` Andrew Jones

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=20240313-852a2b0acf59e8205d0ec9d0@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