From: Max Filippov <jcmvbkbc@gmail.com>
To: linux-xtensa@linux-xtensa.org
Cc: Chris Zankel <chris@zankel.net>,
linux-kernel@vger.kernel.org, Max Filippov <jcmvbkbc@gmail.com>
Subject: [PATCH 5/6] xtensa: add xtensa_xsr macro
Date: Fri, 15 Apr 2022 21:25:58 -0700 [thread overview]
Message-ID: <20220416042559.2035015-6-jcmvbkbc@gmail.com> (raw)
In-Reply-To: <20220416042559.2035015-1-jcmvbkbc@gmail.com>
xtensa_xsr does the XSR instruction for the specified special register.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
---
arch/xtensa/include/asm/processor.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/xtensa/include/asm/processor.h b/arch/xtensa/include/asm/processor.h
index 4489a27d527a..76bc63127c66 100644
--- a/arch/xtensa/include/asm/processor.h
+++ b/arch/xtensa/include/asm/processor.h
@@ -246,6 +246,13 @@ extern unsigned long __get_wchan(struct task_struct *p);
v; \
})
+#define xtensa_xsr(x, sr) \
+ ({ \
+ unsigned int __v__ = (unsigned int)(x); \
+ __asm__ __volatile__ ("xsr %0, " __stringify(sr) : "+a"(__v__)); \
+ __v__; \
+ })
+
#if XCHAL_HAVE_EXTERN_REGS
static inline void set_er(unsigned long value, unsigned long addr)
--
2.30.2
next prev parent reply other threads:[~2022-04-16 4:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 4:25 [PATCH 0/6] xtensa: support coprocessors on SMP Max Filippov
2022-04-16 4:25 ` [PATCH 1/6] xtensa: clean up function declarations in traps.c Max Filippov
2022-04-16 4:25 ` [PATCH 2/6] xtensa: clean up declarations in coprocessor.h Max Filippov
2022-04-16 4:25 ` [PATCH 3/6] xtensa: clean up excsave1 initialization Max Filippov
2022-04-16 4:25 ` [PATCH 4/6] xtensa: use callx0 opcode in fast_coprocessor Max Filippov
2022-04-16 4:25 ` Max Filippov [this message]
2022-04-16 4:25 ` [PATCH 6/6] xtensa: support coprocessors on SMP Max Filippov
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=20220416042559.2035015-6-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=chris@zankel.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.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
Powered by JetHome