From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: kvmarm@lists.linux.dev, kvm@vger.kernel.org,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Mark Brown <broonie@kernel.org>,
Jing Zhang <jingzhangos@google.com>
Subject: Re: [PATCH 0/2] tools: arm64: Sync sysreg.h with the kernel
Date: Thu, 05 Oct 2023 19:25:34 +0100 [thread overview]
Message-ID: <867co1ncyp.wl-maz@kernel.org> (raw)
In-Reply-To: <20231005180325.525236-1-oliver.upton@linux.dev>
On Thu, 05 Oct 2023 19:03:22 +0100,
Oliver Upton <oliver.upton@linux.dev> wrote:
>
> KVM selftests needs to use the full set of sysreg definitions for an
> upcoming change [1]. We took a stab at copying the entire sysreg
> generation infrastructure into the tools directory, but that exploded
> and broke the build for perf, oops [2].
>
> Short of better build infrastructure in tools for handling common
> prerequisite tasks, this series takes the lazy route and copies the
> generated output of the sysreg infra from the kernel.
Hopefully this will spark some interest. In the meantime, this gets us
going, so:
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2023-10-05 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 18:03 [PATCH 0/2] tools: arm64: Sync sysreg.h with the kernel Oliver Upton
2023-10-05 18:03 ` [PATCH 2/2] tools: arm64: Sync sysreg.h with the kernel source Oliver Upton
2023-10-05 18:25 ` Marc Zyngier [this message]
[not found] ` <20231005180325.525236-2-oliver.upton@linux.dev>
2023-10-06 0:23 ` [PATCH 1/2] tools: arm64: Add a copy of sysreg-defs.h generated from the kernel Mark Brown
2023-10-06 9:23 ` Oliver Upton
2023-10-06 11:33 ` Mark Brown
2023-10-06 19:41 ` Oliver Upton
2023-10-06 20:52 ` Mark Brown
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=867co1ncyp.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=broonie@kernel.org \
--cc=james.morse@arm.com \
--cc=jingzhangos@google.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=oliver.upton@linux.dev \
--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).