linux-kernel - [patch 4/4] xtensa: s6000 isef exception

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 25 Mar 2009 11:49:18 +0100
From:	Oskar Schirmer <os@...ix.com>
To:	Chris Zankel <chris@...kel.net>
Cc:	linux-kernel@...r.kernel.org, linux-xtensa@...ux-xtensa.org,
	Oskar Schirmer <os@...ix.com>
Subject: [patch 4/4] xtensa: s6000 isef exception

Allow the ISEF being used implicitly, loading functionality into its ALU
on demand through an exception handler.

Signed-off-by: Oskar Schirmer <os@...ix.com>
---
 arch/xtensa/kernel/traps.c |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/arch/xtensa/kernel/traps.c b/arch/xtensa/kernel/traps.c
index 9f0b711..a26b367 100644
--- a/arch/xtensa/kernel/traps.c
+++ b/arch/xtensa/kernel/traps.c
@@ -66,6 +66,10 @@ extern void do_page_fault (struct pt_regs*, unsigned long);
 extern void do_debug (struct pt_regs*);
 extern void system_call (struct pt_regs*);
 
+#ifdef CONFIG_XTENSA_VARIANT_S6000
+extern void s6_isef_autoload(struct pt_regs*, unsigned long);
+#endif
+
 /*
  * The vector table must be preceded by a save area (which
  * implies it must be in RAM, unless one places RAM immediately
@@ -142,9 +146,13 @@ COPROCESSOR(5),
 #if XTENSA_HAVE_COPROCESSOR(6)
 COPROCESSOR(6),
 #endif
+#ifdef CONFIG_XTENSA_VARIANT_S6000
+{ EXCCAUSE_COPROCESSOR7_DISABLED, 0, s6_isef_autoload },
+#else
 #if XTENSA_HAVE_COPROCESSOR(7)
 COPROCESSOR(7),
 #endif
+#endif
 { EXCCAUSE_MAPPED_DEBUG,		0,		do_debug },
 { -1, -1, 0 }
 
-- 
1.6.2.107.ge47ee

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/