From: Jing Zhang <jingzhangos@google.com> To: Marc Zyngier <maz@kernel.org> Cc: KVM <kvm@vger.kernel.org>, KVMARM <kvmarm@lists.cs.columbia.edu>, Will Deacon <will@kernel.org>, Paolo Bonzini <pbonzini@redhat.com>, David Matlack <dmatlack@google.com>, Oliver Upton <oupton@google.com>, Reiji Watanabe <reijiw@google.com>, Raghavendra Rao Ananta <rananta@google.com> Subject: Re: [RFC PATCH 3/3] KVM: selftests: Add vgic initialization for dirty log perf test for ARM Date: Tue, 11 Jan 2022 14:16:01 -0800 [thread overview] Message-ID: <CAAdAUthmAMy3UE3_C_CitW9MWWMGcOPHu0x9aV72YEUL2kpO=g@mail.gmail.com> (raw) In-Reply-To: <87a6g2tvia.wl-maz@kernel.org> On Tue, Jan 11, 2022 at 2:30 AM Marc Zyngier <maz@kernel.org> wrote: > > On Mon, 10 Jan 2022 21:04:41 +0000, > Jing Zhang <jingzhangos@google.com> wrote: > > > > For ARM64, if no vgic is setup before the dirty log perf test, the > > userspace irqchip would be used, which would affect the dirty log perf > > test result. > > Doesn't it affect *all* performance tests? How much does this change > contributes to the performance numbers you give in the cover letter? > This bottleneck showed up after adding the fast path patch. I didn't try other performance tests with this, but I think it is a good idea to add a vgic setup for all performance tests. I can post another patch later to make it available for all performance tests after finishing this one and verifying all other performance tests. Below is the test result without adding the vgic setup. It shows 20~30% improvement for the different number of vCPUs. +-------+------------------------+ | #vCPU | dirty memory time (ms) | +-------+------------------------+ | 1 | 965 | +-------+------------------------+ | 2 | 1006 | +-------+------------------------+ | 4 | 1128 | +-------+------------------------+ | 8 | 2005 | +-------+------------------------+ | 16 | 3903 | +-------+------------------------+ | 32 | 7595 | +-------+------------------------+ | 64 | 15783 | +-------+------------------------+ > > > > Signed-off-by: Jing Zhang <jingzhangos@google.com> > > --- > > tools/testing/selftests/kvm/dirty_log_perf_test.c | 10 ++++++++++ > > 1 file changed, 10 insertions(+) > > > > diff --git a/tools/testing/selftests/kvm/dirty_log_perf_test.c b/tools/testing/selftests/kvm/dirty_log_perf_test.c > > index 1954b964d1cf..b501338d9430 100644 > > --- a/tools/testing/selftests/kvm/dirty_log_perf_test.c > > +++ b/tools/testing/selftests/kvm/dirty_log_perf_test.c > > @@ -18,6 +18,12 @@ > > #include "test_util.h" > > #include "perf_test_util.h" > > #include "guest_modes.h" > > +#ifdef __aarch64__ > > +#include "aarch64/vgic.h" > > + > > +#define GICD_BASE_GPA 0x8000000ULL > > +#define GICR_BASE_GPA 0x80A0000ULL > > How did you pick these values? I used the same values from other tests. Talked with Raghavendra about the values. It could be arbitrary and he chose these values from QEMU's configuration. > > Thanks, > > M. > > -- > Without deviation from the norm, progress is not possible. Thanks, Jing
WARNING: multiple messages have this Message-ID (diff)
From: Jing Zhang <jingzhangos@google.com> To: Marc Zyngier <maz@kernel.org> Cc: KVM <kvm@vger.kernel.org>, David Matlack <dmatlack@google.com>, Paolo Bonzini <pbonzini@redhat.com>, Will Deacon <will@kernel.org>, KVMARM <kvmarm@lists.cs.columbia.edu> Subject: Re: [RFC PATCH 3/3] KVM: selftests: Add vgic initialization for dirty log perf test for ARM Date: Tue, 11 Jan 2022 14:16:01 -0800 [thread overview] Message-ID: <CAAdAUthmAMy3UE3_C_CitW9MWWMGcOPHu0x9aV72YEUL2kpO=g@mail.gmail.com> (raw) In-Reply-To: <87a6g2tvia.wl-maz@kernel.org> On Tue, Jan 11, 2022 at 2:30 AM Marc Zyngier <maz@kernel.org> wrote: > > On Mon, 10 Jan 2022 21:04:41 +0000, > Jing Zhang <jingzhangos@google.com> wrote: > > > > For ARM64, if no vgic is setup before the dirty log perf test, the > > userspace irqchip would be used, which would affect the dirty log perf > > test result. > > Doesn't it affect *all* performance tests? How much does this change > contributes to the performance numbers you give in the cover letter? > This bottleneck showed up after adding the fast path patch. I didn't try other performance tests with this, but I think it is a good idea to add a vgic setup for all performance tests. I can post another patch later to make it available for all performance tests after finishing this one and verifying all other performance tests. Below is the test result without adding the vgic setup. It shows 20~30% improvement for the different number of vCPUs. +-------+------------------------+ | #vCPU | dirty memory time (ms) | +-------+------------------------+ | 1 | 965 | +-------+------------------------+ | 2 | 1006 | +-------+------------------------+ | 4 | 1128 | +-------+------------------------+ | 8 | 2005 | +-------+------------------------+ | 16 | 3903 | +-------+------------------------+ | 32 | 7595 | +-------+------------------------+ | 64 | 15783 | +-------+------------------------+ > > > > Signed-off-by: Jing Zhang <jingzhangos@google.com> > > --- > > tools/testing/selftests/kvm/dirty_log_perf_test.c | 10 ++++++++++ > > 1 file changed, 10 insertions(+) > > > > diff --git a/tools/testing/selftests/kvm/dirty_log_perf_test.c b/tools/testing/selftests/kvm/dirty_log_perf_test.c > > index 1954b964d1cf..b501338d9430 100644 > > --- a/tools/testing/selftests/kvm/dirty_log_perf_test.c > > +++ b/tools/testing/selftests/kvm/dirty_log_perf_test.c > > @@ -18,6 +18,12 @@ > > #include "test_util.h" > > #include "perf_test_util.h" > > #include "guest_modes.h" > > +#ifdef __aarch64__ > > +#include "aarch64/vgic.h" > > + > > +#define GICD_BASE_GPA 0x8000000ULL > > +#define GICR_BASE_GPA 0x80A0000ULL > > How did you pick these values? I used the same values from other tests. Talked with Raghavendra about the values. It could be arbitrary and he chose these values from QEMU's configuration. > > Thanks, > > M. > > -- > Without deviation from the norm, progress is not possible. Thanks, Jing _______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next prev parent reply other threads:[~2022-01-11 22:16 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-10 21:04 [RFC PATCH 0/3] ARM64: Guest performance improvement during dirty Jing Zhang 2022-01-10 21:04 ` Jing Zhang 2022-01-10 21:04 ` [RFC PATCH 1/3] KVM: arm64: Use read/write spin lock for MMU protection Jing Zhang 2022-01-10 21:04 ` Jing Zhang 2022-01-11 10:23 ` Marc Zyngier 2022-01-11 10:23 ` Marc Zyngier 2022-01-11 22:12 ` Jing Zhang 2022-01-11 22:12 ` Jing Zhang 2022-01-10 21:04 ` [RFC PATCH 2/3] KVM: arm64: Add fast path to handle permission relaxation during dirty logging Jing Zhang 2022-01-10 21:04 ` Jing Zhang 2022-01-11 10:22 ` Marc Zyngier 2022-01-11 10:22 ` Marc Zyngier 2022-01-11 10:50 ` Marc Zyngier 2022-01-11 10:50 ` Marc Zyngier 2022-01-11 22:12 ` Jing Zhang 2022-01-11 22:12 ` Jing Zhang 2022-01-10 21:04 ` [RFC PATCH 3/3] KVM: selftests: Add vgic initialization for dirty log perf test for ARM Jing Zhang 2022-01-10 21:04 ` Jing Zhang 2022-01-11 9:55 ` Andrew Jones 2022-01-11 9:55 ` Andrew Jones 2022-01-11 22:12 ` Jing Zhang 2022-01-11 22:12 ` Jing Zhang 2022-01-11 10:30 ` Marc Zyngier 2022-01-11 10:30 ` Marc Zyngier 2022-01-11 22:16 ` Jing Zhang [this message] 2022-01-11 22:16 ` Jing Zhang 2022-01-12 11:37 ` Marc Zyngier 2022-01-12 11:37 ` Marc Zyngier 2022-01-12 17:40 ` Jing Zhang 2022-01-12 17:40 ` Jing Zhang 2022-01-11 11:54 ` [RFC PATCH 0/3] ARM64: Guest performance improvement during dirty Marc Zyngier 2022-01-11 11:54 ` Marc Zyngier 2022-01-11 22:12 ` Jing Zhang 2022-01-11 22:12 ` Jing Zhang 2022-01-13 2:49 ` Ricardo Koller 2022-01-13 2:49 ` Ricardo Koller 2022-01-13 3:50 ` Jing Zhang 2022-01-13 3:50 ` Jing Zhang 2022-01-13 6:12 ` Ricardo Koller 2022-01-13 6:12 ` Ricardo Koller
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='CAAdAUthmAMy3UE3_C_CitW9MWWMGcOPHu0x9aV72YEUL2kpO=g@mail.gmail.com' \ --to=jingzhangos@google.com \ --cc=dmatlack@google.com \ --cc=kvm@vger.kernel.org \ --cc=kvmarm@lists.cs.columbia.edu \ --cc=maz@kernel.org \ --cc=oupton@google.com \ --cc=pbonzini@redhat.com \ --cc=rananta@google.com \ --cc=reijiw@google.com \ --cc=will@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.