ring-buffer: Remove HAVE_64BIT_ALIGNED_ACCESS

Commit c19fa94a8fed ("Add HAVE_64BIT_ALIGNED_ACCESS") added the config for
architectures that required 64bit aligned access for all 64bit words. As
the ftrace ring buffer stores data on 4 byte alignment, this config option
was used to force it to store data on 8 byte alignment to make sure the data
being stored and written directly into the ring buffer was 8 byte aligned as
it would cause issues trying to write an 8 byte word on a 4 not 8 byte
aligned memory location.

But with the removal of the metag architecture, which was the only
architecture to use this, there is no architecture supported by Linux that
requires 8 byte aligne access for all 8 byte words (4 byte alignment is good
enough). Removing this config can simplify the code a bit.

Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

1 files changed, 0 insertions, 16 deletions

diff --git a/arch/Kconfig b/arch/Kconfig
index c47b328eada0..665a7557b15c 100644
--- a/arch/Kconfig
+++ b/arch/Kconfig
@@ -128,22 +128,6 @@ config UPROBES
             managed by the kernel and kept transparent to the probed
             application. )
 
-config HAVE_64BIT_ALIGNED_ACCESS
-        def_bool 64BIT && !HAVE_EFFICIENT_UNALIGNED_ACCESS
-        help
-          Some architectures require 64 bit accesses to be 64 bit
-          aligned, which also requires structs containing 64 bit values
-          to be 64 bit aligned too. This includes some 32 bit
-          architectures which can do 64 bit accesses, as well as 64 bit
-          architectures without unaligned access.
-
-          This symbol should be selected by an architecture if 64 bit
-          accesses are required to be 64 bit aligned in this way even
-          though it is not a 64 bit architecture.
-
-          See Documentation/unaligned-memory-access.txt for more
-          information on the topic of unaligned memory accesses.
-
 config HAVE_EFFICIENT_UNALIGNED_ACCESS
         bool
         help