From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] generic CPU feature based udev module autoprobing
Date: Wed, 29 Jan 2014 17:50:41 +0100 [thread overview]
Message-ID: <1391014246-9715-1-git-send-email-ard.biesheuvel@linaro.org> (raw)
This series is a slightly expanded version of the series that I have proposed
before. It implements a generic way to wire up udev module autoprobing to
optional CPU features.
Patch #1 moves some code around to prevent duplication later.
Patch #2 implements the actual generic part. It relies on the include file
<asm/cpufeature.h> to be supplied by the architecture to map CPU features to
the number based scheme used by modalias.
Patch #3 aligns x86 with the generic code. As x86 allows matching on CPU vendor,
family and model IDs, it still retains most of the original code for creating
and matching the module metadata.
Patch #4 enables the generic implementation of patch #2 for arm64 by supplying
an 'asm/cpufeatures.h' that maps CPU feature numbers to bit offsets in
elf_hwcap, and by setting CONFIG_GENERIC_CPU_AUTOPROBE for the architecture.
Patch #5 is an example that maps an AES crypto module to the optional AES
feature found on arm64.
Ard Biesheuvel (5):
cpu: move arch_cpu_uevent() to generic code
cpu: add generic support for CPU feature based module autoloading
x86: align x86 arch with generic CPU modalias handling
arm64: enable generic CPU feature modalias matching for this
architecture
arm64: add Crypto Extensions based synchronous core AES cipher
arch/arm64/Kconfig | 1 +
arch/arm64/Makefile | 1 +
arch/arm64/crypto/Makefile | 13 +++++
arch/arm64/crypto/aes-ce-cipher.c | 103 ++++++++++++++++++++++++++++++++++++
arch/arm64/include/asm/cpufeature.h | 30 +++++++++++
arch/x86/Kconfig | 4 +-
arch/x86/include/asm/cpufeature.h | 7 +++
arch/x86/kernel/cpu/match.c | 42 ---------------
crypto/Kconfig | 6 +++
drivers/base/Kconfig | 3 ++
drivers/base/cpu.c | 46 ++++++++++++++--
include/linux/cpu.h | 7 ---
include/linux/cpufeature.h | 60 +++++++++++++++++++++
include/linux/mod_devicetable.h | 9 ++++
scripts/mod/devicetable-offsets.c | 3 ++
scripts/mod/file2alias.c | 20 +++++--
16 files changed, 293 insertions(+), 62 deletions(-)
create mode 100644 arch/arm64/crypto/Makefile
create mode 100644 arch/arm64/crypto/aes-ce-cipher.c
create mode 100644 arch/arm64/include/asm/cpufeature.h
create mode 100644 include/linux/cpufeature.h
--
1.8.3.2
next reply other threads:[~2014-01-29 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 16:50 Ard Biesheuvel [this message]
2014-01-29 16:50 ` [PATCH 1/5] cpu: move arch_cpu_uevent() to generic code Ard Biesheuvel
2014-01-29 16:50 ` [PATCH 2/5] cpu: add generic support for CPU feature based module autoloading Ard Biesheuvel
2014-02-03 17:13 ` Ard Biesheuvel
2014-01-29 16:50 ` [PATCH 3/5] x86: align x86 arch with generic CPU modalias handling Ard Biesheuvel
2014-01-29 17:16 ` H. Peter Anvin
2014-01-29 16:50 ` [PATCH 4/5] arm64: enable generic CPU feature modalias matching for this arch Ard Biesheuvel
2014-01-29 16:50 ` [PATCH 5/5] arm64: add Crypto Extensions based synchronous core AES cipher Ard Biesheuvel
2014-01-30 18:56 ` Will Deacon
2014-01-30 19:20 ` Ard Biesheuvel
2014-02-03 16:17 ` Will Deacon
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=1391014246-9715-1-git-send-email-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).