Hi Jerry, On Wed, Dec 06, 2023 at 03:02:40PM +0800, Jerry Shih wrote: > On Dec 6, 2023, at 08:46, Eric Biggers <ebiggers@xxxxxxxxxx> wrote: > > On Tue, Dec 05, 2023 at 05:27:49PM +0800, Jerry Shih wrote: > >> This series depend on: > >> 2. support kernel-mode vector > >> Link: https://lore.kernel.org/all/20230721112855.1006-1-andy.chiu@xxxxxxxxxx/ > >> 3. vector crypto extensions detection > >> Link: https://lore.kernel.org/lkml/20231017131456.2053396-1-cleger@xxxxxxxxxxxx/ > > > > What's the status of getting these prerequisites merged? > > > > - Eric > > The latest extension detection patch version is v5. > Link: https://lore.kernel.org/lkml/20231114141256.126749-1-cleger@xxxxxxxxxxxx/ > It's still under reviewing. > But I think the checking codes used in this crypto patch series will not change. > We could just wait and rebase when it's merged. > > The latest kernel-mode vector patch version is v3. > Link: https://lore.kernel.org/all/20231019154552.23351-1-andy.chiu@xxxxxxxxxx/ > This patch doesn't work with qemu(hit kernel panic when using vector). It's not > clear for the status. Could we still do the reviewing process for the gluing code and > the crypto asm parts? I'm almost ready to give my Reviewed-by for this whole series. The problem is that it can't be merged until its prerequisites are merged. Andy Chiu's last patchset "riscv: support kernel-mode Vector" was 2 months ago, but he also gave a talk at Plumbers about it more recently (https://www.youtube.com/watch?v=eht3PccEn5o). So I assume he's still working on it. It sounds like he's also going to include support for preemption, and optimizations to memcpy, memset, memmove, and copy_{to,from}_user. I think it would be a good idea to split out the basic support for kernel_vector_{begin,end} so that the users of them, as well as the preemption support, can be considered and merged separately. Maybe patch 1 of the series (https://lore.kernel.org/r/20231019154552.23351-2-andy.chiu@xxxxxxxxxx) is all that's needed initially? Andy, what do you think? - Eric