From: Bin Meng <bmeng.cn@gmail.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
alistair.francis@wdc.com, bmeng@tinylab.org,
liweiwei@iscas.ac.cn, zhiwei_liu@linux.alibaba.com,
Ben Dooks <ben.dooks@codethink.co.uk>,
Anup Patel <apatel@ventanamicro.com>,
Andrew Jones <ajones@ventanamicro.com>
Subject: Re: [PATCH v2 1/1] hw/riscv/virt.c: add cbo[mz]-block-size fdt properties
Date: Thu, 2 Mar 2023 17:57:44 +0800 [thread overview]
Message-ID: <CAEUhbmXuECx1Ka9Mmvm_Y6DCvX55Grmmt1s3idbY7UDpQokn=Q@mail.gmail.com> (raw)
In-Reply-To: <20230302091406.407824-2-dbarboza@ventanamicro.com>
On Thu, Mar 2, 2023 at 5:16 PM Daniel Henrique Barboza
<dbarboza@ventanamicro.com> wrote:
>
> From: Anup Patel <apatel@ventanamicro.com>
>
> The cbom-block-size fdt property property is used to inform the OS about
> the blocksize in bytes for the Zicbom cache operations. Linux documents
> it in Documentation/devicetree/bindings/riscv/cpus.yaml
> as:
>
> riscv,cbom-block-size:
> $ref: /schemas/types.yaml#/definitions/uint32
> description:
> The blocksize in bytes for the Zicbom cache operations.
>
> cboz-block-size has the same role but for the Zicboz extension, i.e.
> informs the size in bytes for Zicboz cache operations. Linux support
> for it is under review/approval in [1]. Patch 3 of that series describes
> cboz-block-size as:
>
> riscv,cboz-block-size:
> $ref: /schemas/types.yaml#/definitions/uint32
> description:
> The blocksize in bytes for the Zicboz cache operations.
>
> [1] https://lore.kernel.org/all/20230224162631.405473-1-ajones@ventanamicro.com/
>
> Cc: Andrew Jones <ajones@ventanamicro.com>
> Signed-off-by: Anup Patel <apatel@ventanamicro.com>
> Signed-off-by: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
> ---
> hw/riscv/virt.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
Reviewed-by: Bin Meng <bmeng@tinylab.org>
next prev parent reply other threads:[~2023-03-02 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 9:14 [PATCH v2 0/1] hw/riscv/virt.c: add cbo[mz]-block-size fdt properties Daniel Henrique Barboza
2023-03-02 9:14 ` [PATCH v2 1/1] " Daniel Henrique Barboza
2023-03-02 9:57 ` Bin Meng [this message]
2023-03-05 20:39 ` [PATCH v2 0/1] " Palmer Dabbelt
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='CAEUhbmXuECx1Ka9Mmvm_Y6DCvX55Grmmt1s3idbY7UDpQokn=Q@mail.gmail.com' \
--to=bmeng.cn@gmail.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=apatel@ventanamicro.com \
--cc=ben.dooks@codethink.co.uk \
--cc=bmeng@tinylab.org \
--cc=dbarboza@ventanamicro.com \
--cc=liweiwei@iscas.ac.cn \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).