All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao-ying Fu <icebergfu@gmail.com>
To: opensbi@lists.infradead.org
Subject: [PATCH] Add a dummy register to sbi_trap_regs
Date: Thu,  9 Jan 2025 15:52:19 -0800	[thread overview]
Message-ID: <20250109235219.2568-1-cfu@mips.com> (raw)

SBI_TRAP_CONTEXT_SIZE becomes a multiple of 8 bytes for RV32
or 16 bytes for RV64, so we have sp aligned to 8 or 16 bytes
to have better performance on some platforms,
---
 include/sbi/sbi_trap.h | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/include/sbi/sbi_trap.h b/include/sbi/sbi_trap.h
index d5182bf..df99d8e 100644
--- a/include/sbi/sbi_trap.h
+++ b/include/sbi/sbi_trap.h
@@ -84,8 +84,10 @@
 #define SBI_TRAP_REGS_mstatus			33
 /** Index of mstatusH member in sbi_trap_regs */
 #define SBI_TRAP_REGS_mstatusH			34
+/** Index of a dummy register */
+#define SBI_TRAP_REGS_dummy			35
 /** Last member index in sbi_trap_regs */
-#define SBI_TRAP_REGS_last			35
+#define SBI_TRAP_REGS_last			36
 
 /** Index of cause member in sbi_trap_info */
 #define SBI_TRAP_INFO_cause			0
@@ -194,6 +196,8 @@ struct sbi_trap_regs {
 	unsigned long mstatus;
 	/** mstatusH register state (only for 32-bit) */
 	unsigned long mstatusH;
+	/** a dummy register */
+	unsigned long dummy;
 };
 
 /** Representation of trap details */
-- 
2.47.1



             reply	other threads:[~2025-01-09 23:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 23:52 Chao-ying Fu [this message]
2025-01-10  0:30 ` [PATCH] Add a dummy register to sbi_trap_regs Jessica Clarke
2025-01-10  1:44   ` Chao-ying Fu
2025-02-06 19:22 ` [PATCH v2] Align SBI trap registers to a nice boundary for performance reasons Raj Vishwanathan
2025-02-08  5:34   ` Samuel Holland
2025-02-10 22:54     ` [EXTERNAL]Re: " Raj Vishwanathan
2025-02-10 22:47 ` Raj Vishwanathan
2025-02-11  2:49   ` Xiang W
2025-02-11  4:48   ` Anup Patel
2025-02-11 21:46 ` [PATCH v2] include: sbi: Align SBI trap registers to a nice boundary Raj Vishwanathan
2025-02-12  4:00   ` Anup Patel

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=20250109235219.2568-1-cfu@mips.com \
    --to=icebergfu@gmail.com \
    --cc=opensbi@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.