public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <ajones@ventanamicro.com>, <kvm-riscv@lists.infradead.org>,
	<linux-riscv@lists.infradead.org>
Cc: <palmer@dabbelt.com>, <heiko@sntech.de>, <anup@brainfault.org>,
	<atishp@atishpatra.org>
Subject: Re: [PATCH 1/3] RISC-V: Output cbom-block-size
Date: Tue, 6 Sep 2022 08:40:23 +0000	[thread overview]
Message-ID: <3da2f5bd-104d-4562-3748-847b2d1c8166@microchip.com> (raw)
In-Reply-To: <20220906083555.931806-2-ajones@ventanamicro.com>

On 06/09/2022 09:35, Andrew Jones wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> Provide an info message with the block size when the Zicbom extension is
> present and the block size has been determined.

Why might someone care about this?

> 
> Signed-off-by: Andrew Jones <ajones@ventanamicro.com>
> ---
>   arch/riscv/mm/cacheflush.c | 4 +++-
>   1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/riscv/mm/cacheflush.c b/arch/riscv/mm/cacheflush.c
> index e5b087be1577..8595baf8e403 100644
> --- a/arch/riscv/mm/cacheflush.c
> +++ b/arch/riscv/mm/cacheflush.c
> @@ -122,7 +122,9 @@ void riscv_init_cbom_blocksize(void)
>                  }
>          }
> 
> -       if (probed_block_size)
> +       if (probed_block_size) {
>                  riscv_cbom_block_size = probed_block_size;
> +               pr_info("riscv: Zicbom: Cache blocksize is %u bytes", probed_block_size);
> +       }
>   }
>   #endif
> --
> 2.37.2
> 

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2022-09-06  8:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06  8:35 [PATCH 0/3] riscv: KVM: Expose Zicbom to the guest Andrew Jones
2022-09-06  8:35 ` [PATCH 1/3] RISC-V: Output cbom-block-size Andrew Jones
2022-09-06  8:40   ` Conor.Dooley [this message]
2022-09-06  8:55     ` Andrew Jones
2022-09-06  9:00       ` Conor.Dooley
2022-09-06  9:29         ` Andrew Jones
2022-09-06  9:42           ` Conor.Dooley
2022-09-06 14:34             ` Heiko Stübner
2022-09-06 14:51               ` Andrew Jones
2022-09-06  9:01       ` Andrew Jones
2022-09-06  8:35 ` [PATCH 2/3] RISC-V: KVM: Provide UAPI for Zicbom block size Andrew Jones
2022-09-06  8:35 ` [PATCH 3/3] RISC-V: KVM: Expose Zicbom to the guest 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=3da2f5bd-104d-4562-3748-847b2d1c8166@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=ajones@ventanamicro.com \
    --cc=anup@brainfault.org \
    --cc=atishp@atishpatra.org \
    --cc=heiko@sntech.de \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    /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