On Wed, Nov 27, 2024 at 10:17 PM Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > > On Wed, Nov 27, 2024 at 5:44 PM Anup Patel <anup@xxxxxxxxxxxxxx> wrote: > > > > On Wed, Nov 27, 2024 at 10:08 PM Paolo Bonzini <pbonzini@xxxxxxxxxx> wrote: > > > > > > On Thu, Nov 21, 2024 at 1:55 PM Anup Patel <anup@xxxxxxxxxxxxxx> wrote: > > > > > > > > Hi Paolo, > > > > > > > > As mentioned in the last PR, here are the remaining KVM RISC-V > > > > changes for 6.13 which mainly consists of Svade/Svadu extension > > > > support for Host and Guest/VM. > > > > > > > > Please note that Palmer has not yet sent the RISC-V PR for 6.13 > > > > so these patches will conflict with the RISC-V tree. > > > > > > The RISC-V PR has not been merged yet (has it been sent?) and I am not > > > sure what's happening here. If these are merged first, presumably > > > Linus will bump the arch/riscv/include/asm/hwcap.h constants -- > > > leaving SVADE/SVADU at 87 and 88 and adjusting the others. Should I do > > > that or is it delayed to 6.14 at this point? > > > > Yes, Palmer send-out RISC-V PR one hour ago. > > (subject "[GIT PULL] RISC-V Paches for the 6.13 Merge Window, Part 1") > > (git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git > > tags/riscv-for-linus-6.13-mw1) > > > > We have already skipped Svade & Svadu support in the 6.12 merge > > window. If possible please take it in this merge window. > > Ok, will do. But I'd like to understand if KVM patches needed the bare > metal support. If not, and the only reason to skip it in 6.12 was the > hwcap.h constants, then there was no reason to delay it. Just send the > hwcap.h update as a pull request to both me and Palmer, and we'll > merge it from the same commit into our trees. It was skipped in 6.12 due to confusion between myself and Palmer about which tree these patches will go through and we did not resolve this in time. Regards, Anup
