From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Will Deacon <will.deacon@arm.com>
Subject: [GIT PULL] arm64 fixes for 3.18
Date: Fri, 24 Oct 2014 18:33:45 +0100 [thread overview]
Message-ID: <20141024173328.GA14639@e104818-lin.cambridge.arm.com> (raw)
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1:
Linux 3.18-rc1 (2014-10-19 18:08:38 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
for you to fetch changes up to 3dec0fe48a8936528aae2fc3f904c2c9a34ba368:
arm64: Fix memblock current_limit with 64K pages and 48-bit VA (2014-10-24 18:16:47 +0100)
----------------------------------------------------------------
arm64 fixes:
- Enable 48-bit VA space now that KVM has been fixed, together with
a couple of fixes for pgd allocation alignment and initial memblock
current_limit. There is still a dependency on !ARM_SMMU which needs to
be updated as it uses the page table manipulation macros of the host
kernel
- eBPF fixes following changes/conflicts during the merging window
- Compat types affecting compat_elf_prpsinfo
- Compilation error on UP builds
- ASLR fix when /proc/sys/kernel/randomize_va_space == 0
- DT definitions for CLCD support on ARMv8 model platform
----------------------------------------------------------------
Alex Bennée (1):
Documentation/arm64/memory.txt: fix typo
Arun Chandran (1):
arm64: ASLR: Don't randomise text when randomise_va_space == 0
Catalin Marinas (4):
arm64: Align less than PAGE_SIZE pgds naturally
arm64: Fix compilation error on UP builds
arm64: vexpress: Add CLCD support to the ARMv8 model platform
arm64: Fix memblock current_limit with 64K pages and 48-bit VA
Christoffer Dall (1):
arm64: Allow 48-bits VA space without ARM_SMMU
Daniel Borkmann (2):
net: bpf: arm64: address randomize and write protect JIT code
net: bpf: arm64: minor fix of type in jited
Steve Capper (1):
arm64: mm: Correct fixmap pagetable types
Victor Kamensky (1):
arm64: compat: fix compat types affecting struct compat_elf_prpsinfo
Zi Shen Lim (2):
arm64: bpf: add 'shift by register' instructions
arm64: bpf: add 'load 64-bit immediate' instruction
Documentation/arm64/memory.txt | 2 +-
arch/arm64/Kconfig | 3 +-
arch/arm64/boot/dts/rtsm_ve-motherboard.dtsi | 35 +++++++++++-
arch/arm64/configs/defconfig | 2 +
arch/arm64/include/asm/compat.h | 4 +-
arch/arm64/include/asm/elf.h | 4 +-
arch/arm64/include/asm/irq_work.h | 11 ++++
arch/arm64/kernel/process.c | 5 --
arch/arm64/mm/ioremap.c | 4 +-
arch/arm64/mm/mmu.c | 12 ++--
arch/arm64/mm/pgd.c | 18 +++++-
arch/arm64/net/bpf_jit.h | 8 ++-
arch/arm64/net/bpf_jit_comp.c | 84 ++++++++++++++++++++++++----
13 files changed, 160 insertions(+), 32 deletions(-)
--
Catalin
next reply other threads:[~2014-10-24 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 17:33 Catalin Marinas [this message]
2014-11-09 9:44 Catalin Marinas
2014-11-14 18:38 Catalin Marinas
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=20141024173328.GA14639@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®