From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH v3 0/5] arm64: vdso: getcpu() support
Date: Tue, 1 Sep 2020 11:46:52 +0100 [thread overview]
Message-ID: <20200901104652.GA6262@sirena.org.uk> (raw)
In-Reply-To: <20200901092551.GG5561@gaia>
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
On Tue, Sep 01, 2020 at 10:25:52AM +0100, Catalin Marinas wrote:
> Thanks Shuah for the ack. We are still pondering whether the merge these
> patches as they have some limitations (the per-CPU data structures may
> not fit in the sole data vDSO page).
They definitely don't fit, I did have some half-written proof of concept
patches that I posted that extend this but I was waiting to see if there
was any interest in a vDSO getcpu() at all before taking it further.
Vincenzo's work on doing the multipage user data that he announced at
Plumbers would cover it as well, I hadn't been aware of that.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>,
linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Shuah Khan <shuah@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/5] arm64: vdso: getcpu() support
Date: Tue, 1 Sep 2020 11:46:52 +0100 [thread overview]
Message-ID: <20200901104652.GA6262@sirena.org.uk> (raw)
In-Reply-To: <20200901092551.GG5561@gaia>
[-- Attachment #1.1: Type: text/plain, Size: 601 bytes --]
On Tue, Sep 01, 2020 at 10:25:52AM +0100, Catalin Marinas wrote:
> Thanks Shuah for the ack. We are still pondering whether the merge these
> patches as they have some limitations (the per-CPU data structures may
> not fit in the sole data vDSO page).
They definitely don't fit, I did have some half-written proof of concept
patches that I posted that extend this but I was waiting to see if there
was any interest in a vDSO getcpu() at all before taking it further.
Vincenzo's work on doing the multipage user data that he announced at
Plumbers would cover it as well, I hadn't been aware of that.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-09-01 10:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 12:13 [PATCH v3 0/5] arm64: vdso: getcpu() support Mark Brown
2020-08-19 12:13 ` Mark Brown
2020-08-19 12:13 ` [PATCH v3 1/5] arm64: vdso: Provide a define when building the vDSO Mark Brown
2020-08-19 12:13 ` Mark Brown
2020-08-19 12:13 ` [PATCH v3 2/5] arm64: vdso: Add per-CPU data Mark Brown
2020-08-19 12:13 ` Mark Brown
2020-08-19 12:13 ` [PATCH v3 3/5] arm64: vdso: Initialise the per-CPU vDSO data Mark Brown
2020-08-19 12:13 ` Mark Brown
2020-08-19 12:13 ` [PATCH v3 4/5] arm64: vdso: Add getcpu() implementation Mark Brown
2020-08-19 12:13 ` Mark Brown
2020-08-19 12:13 ` [PATCH v3 5/5] selftests: vdso: Support arm64 in getcpu() test Mark Brown
2020-08-19 12:13 ` Mark Brown
2020-08-31 21:47 ` [PATCH v3 0/5] arm64: vdso: getcpu() support Shuah Khan
2020-08-31 21:47 ` Shuah Khan
2020-09-01 9:25 ` Catalin Marinas
2020-09-01 9:25 ` Catalin Marinas
2020-09-01 10:46 ` Mark Brown [this message]
2020-09-01 10:46 ` 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=20200901104652.GA6262@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=vincenzo.frascino@arm.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: link
Be 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.