From: Chris von Recklinghausen <crecklin@redhat•com>
To: linux-arm-kernel@lists•infradead.org, steve.capper@arm•com
Subject: [PATCH] arm64: remove arm64 definitions of kc_vaddr_to_offset and kc_offset_to_vaddr.
Date: Tue, 8 Oct 2019 13:54:34 -0400 [thread overview]
Message-ID: <20191008175434.27434-1-crecklin@redhat.com> (raw)
With the reshuffling of kernel VA space to support 52 bits, the
kc_vaddr_to_offset and kc_offset_to_vaddr macros are broken, since they are
based on VA_START, but VA_START no longer points to the base of the kernel
virtual address space, (PAGE_OFFSET does now). fs/proc/kcore.c already has
default definitions of kc_vaddr_to_offset and kc_offset_to_vaddr based on
PAGE_OFFSET, so simply remove the arm64 definitions of them.
Fixes: 14c127c957c1c607 ("arm64: mm: Flip kernel VA space")
---
arch/arm64/include/asm/pgtable.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/arm64/include/asm/pgtable.h b/arch/arm64/include/asm/pgtable.h
index 7576df00eb50..8330810f699e 100644
--- a/arch/arm64/include/asm/pgtable.h
+++ b/arch/arm64/include/asm/pgtable.h
@@ -876,9 +876,6 @@ static inline void update_mmu_cache(struct vm_area_struct *vma,
#define update_mmu_cache_pmd(vma, address, pmd) do { } while (0)
-#define kc_vaddr_to_offset(v) ((v) & ~PAGE_END)
-#define kc_offset_to_vaddr(o) ((o) | PAGE_END)
-
#ifdef CONFIG_ARM64_PA_BITS_52
#define phys_to_ttbr(addr) (((addr) | ((addr) >> 46)) & TTBR_BADDR_MASK_52)
#else
--
2.18.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-10-08 17:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 17:54 Chris von Recklinghausen [this message]
2019-10-09 18:09 ` [PATCH] arm64: remove arm64 definitions of kc_vaddr_to_offset and kc_offset_to_vaddr Chris von Recklinghausen
2019-10-10 12:51 ` Chris von Recklinghausen
2019-10-10 13:05 ` Dave Anderson
2019-10-10 16:12 ` James Morse
2019-10-10 16:55 ` Mark Rutland
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=20191008175434.27434-1-crecklin@redhat.com \
--to=crecklin@redhat$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=steve.capper@arm$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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