Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <ajones@ventanamicro.com>
To: patchwork-bot+linux-riscv@kernel.org
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	 palmer@dabbelt.com, aou@eecs.berkeley.edu, evan@rivosinc.com,
	 conor.dooley@microchip.com, apatel@ventanamicro.com
Subject: Re: [PATCH 0/6] RISC-V: Enable cbo.zero in usermode
Date: Wed, 30 Aug 2023 18:22:57 +0200	[thread overview]
Message-ID: <20230830-416e25b9fc6054b36bf81aab@orel> (raw)
In-Reply-To: <169340163447.19859.7372275191513999075.git-patchwork-notify@kernel.org>

On Wed, Aug 30, 2023 at 01:20:34PM +0000, patchwork-bot+linux-riscv@kernel.org wrote:
> Hello:
> 
> This series was applied to riscv/linux.git (for-next)
> by Palmer Dabbelt <palmer@rivosinc.com>:
> 
> On Wed,  9 Aug 2023 13:55:17 +0200 you wrote:
> > In order for usermode to issue cbo.zero, it needs privilege granted to
> > issue the extension instruction (patch 2) and to know that the extension
> > is available and its block size (patch 3). Patch 1 could be separate from
> > this series (it just fixes up some error messages), patches 4-5 convert
> > the hwprobe selftest to a statically-linked, TAP test and patch 6 adds a
> > new hwprobe test for the new information as well as testing CBO
> > instructions can or cannot be issued as appropriate.
> > 
> > [...]
> 
> Here is the summary with links:
>   - [1/6] RISC-V: Make zicbom/zicboz errors consistent
>     https://git.kernel.org/riscv/c/66e02b1d6430
>   - [2/6] RISC-V: Enable cbo.zero in usermode
>     https://git.kernel.org/riscv/c/090925374690
>   - [3/6] RISC-V: hwprobe: Expose Zicboz extension and its block size
>     https://git.kernel.org/riscv/c/d45243f8c239
>   - [4/6] RISC-V: selftests: Statically link hwprobe test
>     https://git.kernel.org/riscv/c/0ca410a80172
>   - [5/6] RISC-V: selftests: Convert hwprobe test to kselftest API
>     https://git.kernel.org/riscv/c/d79a646354a9
>   - [6/6] RISC-V: selftests: Add CBO tests
>     https://git.kernel.org/riscv/c/026645838c86
> 
> You are awesome, thank you!
> -- 
> Deet-doot-dot, I am a bot.
> https://korg.docs.kernel.org/patchwork/pwbot.html
> 
>

Hi Palmer,

This series needs a v2. There were couple minor comments on v1, and
I just found out that I broke the compiling of the nolibc vector
selftest.

I'll post v2 in the next few minutes. Sorry for the hassle!

Thanks,
drew

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

      reply	other threads:[~2023-08-30 16:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-09 11:55 [PATCH 0/6] RISC-V: Enable cbo.zero in usermode Andrew Jones
2023-08-09 11:55 ` [PATCH 1/6] RISC-V: Make zicbom/zicboz errors consistent Andrew Jones
2023-08-10  9:35   ` Conor Dooley
2023-08-09 11:55 ` [PATCH 2/6] RISC-V: Enable cbo.zero in usermode Andrew Jones
2023-08-09 16:00   ` Evan Green
2023-08-09 16:58     ` Andrew Jones
2023-08-09 18:12       ` Conor Dooley
2023-08-10  7:31         ` Andrew Jones
2023-08-10  9:34           ` Conor Dooley
2023-08-10 10:54             ` Andrew Jones
2023-08-10 13:23               ` Conor Dooley
2023-08-09 19:40       ` Evan Green
2023-08-09 11:55 ` [PATCH 3/6] RISC-V: hwprobe: Expose Zicboz extension and its block size Andrew Jones
2023-08-09 16:00   ` Evan Green
2023-08-10  9:49   ` Conor Dooley
2023-08-10 10:57     ` Andrew Jones
2023-08-10 11:33       ` Conor Dooley
2023-08-09 11:55 ` [PATCH 4/6] RISC-V: selftests: Statically link hwprobe test Andrew Jones
2023-08-10  9:36   ` Conor Dooley
2023-08-09 11:55 ` [PATCH 5/6] RISC-V: selftests: Convert hwprobe test to kselftest API Andrew Jones
2023-08-09 11:55 ` [PATCH 6/6] RISC-V: selftests: Add CBO tests Andrew Jones
2023-08-30 13:20 ` [PATCH 0/6] RISC-V: Enable cbo.zero in usermode patchwork-bot+linux-riscv
2023-08-30 16:22   ` Andrew Jones [this message]

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=20230830-416e25b9fc6054b36bf81aab@orel \
    --to=ajones@ventanamicro.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=apatel@ventanamicro.com \
    --cc=conor.dooley@microchip.com \
    --cc=evan@rivosinc.com \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=patchwork-bot+linux-riscv@kernel.org \
    --cc=paul.walmsley@sifive.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