From: "Heiko Stübner" <heiko@sntech.de>
To: palmer@dabbelt.com, paul.walmsley@sifive.com
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
wefu@redhat.com, guoren@kernel.org, cmuellner@linux.com,
philipp.tomsich@vrull.eu, hch@lst.de, samuel@sholland.org,
atishp@atishpatra.org, anup@brainfault.org, mick@ics.forth.gr,
robh+dt@kernel.org, krzk+dt@kernel.org,
devicetree@vger.kernel.org, drew@beagleboard.org,
rdunlap@infradead.org, Atish Patra <atish.patra@wdc.com>
Subject: Re: [PATCH v7 3/4] riscv: Add support for non-coherent devices using zicbom extension
Date: Thu, 07 Jul 2022 10:40:57 +0200 [thread overview]
Message-ID: <1729939.VLH7GnMWUR@diego> (raw)
In-Reply-To: <20220706231536.2041855-4-heiko@sntech.de>
Am Donnerstag, 7. Juli 2022, 01:15:35 CEST schrieb Heiko Stuebner:
> The Zicbom ISA-extension was ratified in november 2021
> and introduces instructions for dcache invalidate, clean
> and flush operations.
>
> Implement cache management operations for non-coherent devices
> based on them.
>
> Of course not all cores will support this, so implement an
> alternative-based mechanism that replaces empty instructions
> with ones done around Zicbom instructions.
>
> As discussed in previous versions, assume the platform
> being coherent by default so that non-coherent devices need
> to get marked accordingly by firmware.
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Atish Patra <atish.patra@wdc.com>
> Cc: Guo Ren <guoren@kernel.org>
> Cc: Anup Patel <anup@brainfault.org>
Over in v6 Guo provided [0] a
Reviewed-by: Guo Ren <guoren@kernel.org>
[0] https://lore.kernel.org/r/CAJF2gTRN1J3edjbt5L9ELLtMzXKWUABQb=QxDA90uY7mj=O0rw@mail.gmail.com
next prev parent reply other threads:[~2022-07-07 8:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 23:15 [PATCH v7 0/4] riscv: implement Zicbom-based CMO instructions + the t-head variant Heiko Stuebner
2022-07-06 23:15 ` [PATCH v7 1/4] of: also handle dma-noncoherent in of_dma_is_coherent() Heiko Stuebner
2022-07-06 23:15 ` [PATCH v7 2/4] dt-bindings: riscv: document cbom-block-size Heiko Stuebner
2022-07-06 23:15 ` [PATCH v7 3/4] riscv: Add support for non-coherent devices using zicbom extension Heiko Stuebner
2022-07-07 8:40 ` Heiko Stübner [this message]
2022-07-06 23:15 ` [PATCH v7 4/4] riscv: implement cache-management errata for T-Head SoCs Heiko Stuebner
2022-08-04 0:28 ` Palmer Dabbelt
2022-08-04 8:16 ` Arnd Bergmann
2022-08-11 4:52 ` [PATCH v7 0/4] riscv: implement Zicbom-based CMO instructions + the t-head variant 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=1729939.VLH7GnMWUR@diego \
--to=heiko@sntech.de \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--cc=atishp@atishpatra.org \
--cc=cmuellner@linux.com \
--cc=devicetree@vger.kernel.org \
--cc=drew@beagleboard.org \
--cc=guoren@kernel.org \
--cc=hch@lst.de \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mick@ics.forth.gr \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=philipp.tomsich@vrull.eu \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wefu@redhat.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).