From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: "Theodore Ts'o" <tytso@mit.edu>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Arnd Bergmann <arnd@arndb.de>, Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-arch@vger.kernel.org
Subject: [PATCH 0/4] Fixups for random vDSO
Date: Tue, 27 Aug 2024 09:31:46 +0200 [thread overview]
Message-ID: <cover.1724743492.git.christophe.leroy@csgroup.eu> (raw)
This small series is an extract of fixups for generic part of random vDSO in
preparation of implementing vDSO getrandom for powerpc.
See last version of full series at:
https://patchwork.ozlabs.org/project/linuxppc-dev/cover/cover.1724309198.git.christophe.leroy@csgroup.eu/
This series is based on top of:
https://git.kernel.org/pub/scm/linux/kernel/git/crng/random.git master
Christophe Leroy (4):
asm-generic/unaligned.h: Extract common header for vDSO
random: vDSO: Don't use PAGE_SIZE and PAGE_MASK
random: vDSO: Clean header inclusion in getrandom
random: vDSO: don't use 64 bits atomics on 32 bits architectures
arch/x86/include/asm/pvclock.h | 1 +
drivers/char/random.c | 9 ++++++++-
include/asm-generic/unaligned.h | 11 +----------
include/vdso/helpers.h | 1 +
include/vdso/unaligned.h | 15 +++++++++++++++
lib/vdso/getrandom.c | 16 ++++++++--------
6 files changed, 34 insertions(+), 19 deletions(-)
create mode 100644 include/vdso/unaligned.h
--
2.44.0
next reply other threads:[~2024-08-27 7:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 7:31 Christophe Leroy [this message]
2024-08-27 7:31 ` [PATCH 1/4] asm-generic/unaligned.h: Extract common header for vDSO Christophe Leroy
2024-08-27 7:31 ` [PATCH 2/4] random: vDSO: Don't use PAGE_SIZE and PAGE_MASK Christophe Leroy
2024-08-27 7:49 ` Jason A. Donenfeld
2024-08-27 8:16 ` Christophe Leroy
2024-08-27 8:23 ` Jason A. Donenfeld
2024-08-27 8:26 ` [PATCH] random: vDSO: Redefine " Christophe Leroy
2024-08-27 8:40 ` Jason A. Donenfeld
2024-08-27 8:55 ` Christophe Leroy
2024-08-27 9:59 ` Arnd Bergmann
2024-08-27 10:49 ` Christophe Leroy
2024-08-27 16:05 ` Vincenzo Frascino
2024-08-27 17:14 ` Christophe Leroy
2024-08-29 12:01 ` Vincenzo Frascino
2024-08-29 15:00 ` Christophe Leroy
2024-08-29 15:34 ` Vincenzo Frascino
2024-08-27 17:38 ` LEROY Christophe
2024-08-29 14:07 ` Vincenzo Frascino
2024-08-27 7:31 ` [PATCH 3/4] random: vDSO: Clean header inclusion in getrandom Christophe Leroy
2024-08-27 7:31 ` [PATCH 4/4] random: vDSO: don't use 64 bits atomics on 32 bits architectures Christophe Leroy
2024-08-27 8:03 ` Jason A. Donenfeld
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=cover.1724743492.git.christophe.leroy@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=Jason@zx2c4.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=vincenzo.frascino@arm.com \
--cc=x86@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 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).