From: Andrew Jones <ajones@ventanamicro.com>
To: Atish Kumar Patra <atishp@rivosinc.com>
Cc: Anup Patel <anup@brainfault.org>,
Atish Patra <atishp@atishpatra.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 4/4] KVM: riscv: selftests: Allow number of interrupts to be configurable
Date: Tue, 4 Mar 2025 09:58:15 +0100 [thread overview]
Message-ID: <20250304-5a85b3a246f14f60f61a45e0@orel> (raw)
In-Reply-To: <CAHBxVyGGw6Ur4Kdd8Vvwp6viKWPx64w7gNvNiUzmAGeXF2PGoA@mail.gmail.com>
On Mon, Mar 03, 2025 at 01:27:47PM -0800, Atish Kumar Patra wrote:
> On Thu, Feb 27, 2025 at 12:16 AM Andrew Jones <ajones@ventanamicro.com> wrote:
> >
> > On Wed, Feb 26, 2025 at 12:25:06PM -0800, Atish Patra wrote:
...
> I will change the default value to 0 to avoid ambiguity for now.
> Please let me know if you strongly think we should support -n 0.
> We can always support it. I just don't see the point of specifying the
> test with options to disable it anymore.
>
I don't mind not supporting '-n 0'.
Thanks,
drew
prev parent reply other threads:[~2025-03-04 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 20:25 [PATCH 0/4] RISC-V KVM PMU fix and selftest improvement Atish Patra
2025-02-26 20:25 ` [PATCH 1/4] RISC-V: KVM: Disable the kernel perf counter during configure Atish Patra
2025-02-27 8:49 ` Andrew Jones
2025-02-26 20:25 ` [PATCH 2/4] KVM: riscv: selftests: Do not start the counter in the overflow handler Atish Patra
2025-02-27 8:44 ` Andrew Jones
2025-02-26 20:25 ` [PATCH 3/4] KVM: riscv: selftests: Change command line option Atish Patra
2025-02-27 8:08 ` Andrew Jones
2025-03-03 20:53 ` Atish Kumar Patra
2025-02-26 20:25 ` [PATCH 4/4] KVM: riscv: selftests: Allow number of interrupts to be configurable Atish Patra
2025-02-27 8:16 ` Andrew Jones
2025-03-03 21:27 ` Atish Kumar Patra
2025-03-04 8:58 ` 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=20250304-5a85b3a246f14f60f61a45e0@orel \
--to=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-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
/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