From: Oliver Upton <oliver.upton@linux.dev>
To: Eric Auger <eauger@redhat.com>
Cc: Shaoqin Huang <shahuang@redhat.com>,
Marc Zyngier <maz@kernel.org>,
kvmarm@lists.linux.dev, Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v7 2/3] KVM: selftests: aarch64: Introduce pmu_event_filter_test
Date: Tue, 7 May 2024 14:49:06 +0000 [thread overview]
Message-ID: <Zjo_Yj9_dkZiQIBT@linux.dev> (raw)
In-Reply-To: <acbc717e-5f7b-405b-9674-e03d315726cb@redhat.com>
Hi,
On Tue, May 07, 2024 at 10:45:24AM +0200, Eric Auger wrote:
> On 4/9/24 05:03, Shaoqin Huang wrote:
> > +#define GICD_BASE_GPA 0x8000000ULL
> > +#define GICR_BASE_GPA 0x80A0000ULL
> in v4 Oliver suggested "Shouldn't a standardized layout of the GIC
> frames go with the rest of the GIC stuff?"
>
Just a heads up, commit 1505bc70f80d ("KVM: selftests: Standardise layout
of GIC frames") will do exactly this, which is currently on /next.
--
Thanks,
Oliver
next prev parent reply other threads:[~2024-05-07 14:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 3:03 [PATCH v7 0/3] KVM: selftests: aarch64: Introduce pmu_event_filter_test Shaoqin Huang
2024-04-09 3:03 ` [PATCH v7 1/3] KVM: selftests: aarch64: Add helper function for the vpmu vcpu creation Shaoqin Huang
2024-04-09 3:03 ` [PATCH v7 2/3] KVM: selftests: aarch64: Introduce pmu_event_filter_test Shaoqin Huang
2024-05-07 8:45 ` Eric Auger
2024-05-07 14:49 ` Oliver Upton [this message]
2024-05-09 8:31 ` Shaoqin Huang
2024-05-09 7:34 ` Shaoqin Huang
2024-04-09 3:03 ` [PATCH v7 3/3] KVM: selftests: aarch64: Add invalid filter test in pmu_event_filter_test Shaoqin Huang
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=Zjo_Yj9_dkZiQIBT@linux.dev \
--to=oliver.upton@linux.dev \
--cc=eauger@redhat.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=shahuang@redhat.com \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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).