From: Sean Christopherson <seanjc@google.com>
To: Anup Patel <anup@brainfault.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
Andrew Jones <ajones@ventanamicro.com>,
Atish Patra <atishp@atishpatra.org>,
Atish Patra <atishp@rivosinc.com>,
KVM General <kvm@vger.kernel.org>,
"open list:KERNEL VIRTUAL MACHINE FOR RISC-V (KVM/riscv)"
<kvm-riscv@lists.infradead.org>,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [GIT PULL] KVM/riscv changes for 6.9
Date: Thu, 7 Mar 2024 10:42:41 -0800 [thread overview]
Message-ID: <ZeoKoUJlCZMiwPXB@google.com> (raw)
In-Reply-To: <Zen8qGzVpaOB_vKa@google.com>
On Thu, Mar 07, 2024, Sean Christopherson wrote:
> On Thu, Mar 07, 2024, Anup Patel wrote:
> > ----------------------------------------------------------------
> > KVM/riscv changes for 6.9
> >
> > - Exception and interrupt handling for selftests
> > - Sstc (aka arch_timer) selftest
> > - Forward seed CSR access to KVM userspace
> > - Ztso extension support for Guest/VM
> > - Zacas extension support for Guest/VM
> >
> > ----------------------------------------------------------------
> > Anup Patel (5):
> > RISC-V: KVM: Forward SEED CSR access to user space
> > RISC-V: KVM: Allow Ztso extension for Guest/VM
> > KVM: riscv: selftests: Add Ztso extension to get-reg-list test
> > RISC-V: KVM: Allow Zacas extension for Guest/VM
> > KVM: riscv: selftests: Add Zacas extension to get-reg-list test
> >
> > Haibo Xu (11):
> > KVM: arm64: selftests: Data type cleanup for arch_timer test
> > KVM: arm64: selftests: Enable tuning of error margin in arch_timer test
> > KVM: arm64: selftests: Split arch_timer test code
> > KVM: selftests: Add CONFIG_64BIT definition for the build
> > tools: riscv: Add header file csr.h
> > tools: riscv: Add header file vdso/processor.h
> > KVM: riscv: selftests: Switch to use macro from csr.h
> > KVM: riscv: selftests: Add exception handling support
> > KVM: riscv: selftests: Add guest helper to get vcpu id
>
> Uh, what's going on with this series? Many of these were committed *yesterday*,
> but you sent a mail on February 12th[1] saying these were queued. That's quite
> the lag.
...
> And again, this showing up _so_ late means it's unnecessarily difficult to clean
> things up. Which is kinda the whole point of getting thing into linux-next, so
> that folks that weren't involved in the original patch/series can react if there
> is a hiccup/problem/oddity.
Case in point (I pinky-swear I didn't see the patch before sending the first mail):
https://lore.kernel.org/all/20240307081951.1954830-1-colin.i.king@gmail.com
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-03-07 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 6:45 [GIT PULL] KVM/riscv changes for 6.9 Anup Patel
2024-03-07 17:43 ` Sean Christopherson
2024-03-07 18:42 ` Sean Christopherson [this message]
2024-03-08 5:27 ` Anup Patel
2024-03-08 15:40 ` Sean Christopherson
2024-03-11 14:10 ` Paolo Bonzini
2024-03-12 6:51 ` Anup Patel
2024-03-08 7:53 ` Andrew Jones
2024-03-11 14:19 ` Paolo Bonzini
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=ZeoKoUJlCZMiwPXB@google.com \
--to=seanjc@google.com \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--cc=atishp@rivosinc.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=pbonzini@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).