From: Catalin Marinas <catalin.marinas@arm.com>
To: Fred Griffoul <fgriffo@amazon.co.uk>
Cc: griffoul@gmail.com, kernel test robot <lkp@intel.com>,
Will Deacon <will@kernel.org>,
Alex Williamson <alex.williamson@redhat.com>,
Waiman Long <longman@redhat.com>,
Zefan Li <lizefan.x@bytedance.com>, Tejun Heo <tj@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Mark Brown <broonie@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
Joey Gouly <joey.gouly@arm.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Jeremy Linton <jeremy.linton@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Yi Liu <yi.l.liu@intel.com>,
Kevin Tian <kevin.tian@intel.com>,
Eric Auger <eric.auger@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Christian Brauner <brauner@kernel.org>,
Ankit Agrawal <ankita@nvidia.com>,
Reinette Chatre <reinette.chatre@intel.com>,
Ye Bin <yebin10@huawei.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
cgroups@vger.kernel.org
Subject: Re: [PATCH v6 1/2] cgroup/cpuset: export cpuset_cpus_allowed()
Date: Wed, 12 Jun 2024 10:21:54 +0100 [thread overview]
Message-ID: <Zmlosj-Fmsoq1AiU@arm.com> (raw)
In-Reply-To: <20240611174430.90787-2-fgriffo@amazon.co.uk>
On Tue, Jun 11, 2024 at 05:44:24PM +0000, Fred Griffoul wrote:
> diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
> index 56583677c1f2..2f1de6343bee 100644
> --- a/arch/arm64/kernel/cpufeature.c
> +++ b/arch/arm64/kernel/cpufeature.c
> @@ -127,6 +127,7 @@ static bool __read_mostly allow_mismatched_32bit_el0;
> * seen at least one CPU capable of 32-bit EL0.
> */
> DEFINE_STATIC_KEY_FALSE(arm64_mismatched_32bit_el0);
> +EXPORT_SYMBOL_GPL(arm64_mismatched_32bit_el0);
>
> /*
> * Mask of CPUs supporting 32-bit EL0.
> @@ -1614,6 +1615,7 @@ const struct cpumask *system_32bit_el0_cpumask(void)
>
> return cpu_possible_mask;
> }
> +EXPORT_SYMBOL_GPL(system_32bit_el0_cpumask);
For the arm64 bits:
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2024-06-12 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 17:44 [PATCH v6 0/2] vfio/pci: add interrupt affinity support Fred Griffoul
2024-06-11 17:44 ` [PATCH v6 1/2] cgroup/cpuset: export cpuset_cpus_allowed() Fred Griffoul
2024-06-11 18:32 ` Waiman Long
2024-06-12 9:21 ` Catalin Marinas [this message]
2024-06-11 17:44 ` [PATCH v6 2/2] vfio/pci: add interrupt affinity support Fred Griffoul
2024-06-18 20:29 ` Alex Williamson
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=Zmlosj-Fmsoq1AiU@arm.com \
--to=catalin.marinas@arm.com \
--cc=alex.williamson@redhat.com \
--cc=ankita@nvidia.com \
--cc=ardb@kernel.org \
--cc=brauner@kernel.org \
--cc=broonie@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=eric.auger@redhat.com \
--cc=fgriffo@amazon.co.uk \
--cc=griffoul@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=jeremy.linton@arm.com \
--cc=jgg@ziepe.ca \
--cc=joey.gouly@arm.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=lkp@intel.com \
--cc=longman@redhat.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=reinette.chatre@intel.com \
--cc=ryan.roberts@arm.com \
--cc=stefanha@redhat.com \
--cc=tj@kernel.org \
--cc=will@kernel.org \
--cc=yebin10@huawei.com \
--cc=yi.l.liu@intel.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).