From: Deepak Gupta <debug@rivosinc.com>
To: woodrow.shen@sifive.com, Andrew Jones <ajones@ventanamicro.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Glenn Washburn <development@efficientek.com>,
Jeff Xie <xiehuan09@gmail.com>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org
Cc: akpm@linux-foundation.org
Subject: Re: [PATCH v6] scripts/gdb: add lx_current support for riscv
Date: Thu, 2 Nov 2023 08:45:17 -0700 [thread overview]
Message-ID: <ZUPEDWofcqgzsgMS@debug.ba.rivosinc.com> (raw)
In-Reply-To: <20231026233837.612405-1-debug@rivosinc.com>
Ping
+ CC: akpm@linux-foundation.org
Who should I ping to make sure that it lands up in mainline?
It's quite a trivial change to support lx_current riscv arch.
-Deepak
On Thu, Oct 26, 2023 at 04:38:23PM -0700, Deepak Gupta wrote:
>csr_sscratch CSR holds current task_struct address when hart is in
>user space. Trap handler on entry spills csr_sscratch into "tp" (x2)
>register and zeroes out csr_sscratch CSR. Trap handler on exit reloads
>"tp" with expected user mode value and place current task_struct address
>again in csr_sscratch CSR.
>
>This patch assumes "tp" is pointing to task_struct. If value in
>csr_sscratch is numerically greater than "tp" then it assumes csr_sscratch
>is correct address of current task_struct. This logic holds when
> - hart is in user space, "tp" will be less than csr_sscratch.
> - hart is in kernel space but not in trap handler, "tp" will be more
> than csr_sscratch (csr_sscratch being equal to 0).
> - hart is executing trap handler
> - "tp" is still pointing to user mode but csr_sscratch contains
> ptr to task_struct. Thus numerically higher.
> - "tp" is pointing to task_struct but csr_sscratch now contains
> either 0 or numerically smaller value (transiently holds
> user mode tp)
>
>Signed-off-by: Deepak Gupta <debug@rivosinc.com>
>Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
>Reviewed-by: Palmer Dabbelt <palmer@rivosinc.com>
>Acked-by: Palmer Dabbelt <palmer@rivosinc.com>
>Tested-by: Hsieh-Tseng Shen <woodrow.shen@sifive.com>
>
>---
>Since patch has changed a little bit from v1 and I didn't include
>changelog earlier, here it is.
>
>v1 --> v2:
> - added logic to locate task_struct irrespective of priv
> - made locating task_struct agnostic to bitness(32 vs 64).
> - added caching of ulong type in scripts/gdb/linux/utils.py
> - added more descriptive commit message
>
>v2 --> v3:
> - amended commit message and source line to fit column width
>
>v3 --> v4:
> - amended commit message and remove whitespace in source
> - added Reviewed-by for reviewers
>
>v4 --> v5:
> - changing the order of changelog and sign off/review tags in commit
>
>v5 --> v6:
> - rebased on 6.6-rc5. dropped changes in utils.py as they're upstream
>---
> scripts/gdb/linux/cpus.py | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
>diff --git a/scripts/gdb/linux/cpus.py b/scripts/gdb/linux/cpus.py
>index 255dc18cb9da..cba589e5b57d 100644
>--- a/scripts/gdb/linux/cpus.py
>+++ b/scripts/gdb/linux/cpus.py
>@@ -179,6 +179,21 @@ def get_current_task(cpu):
> else:
> raise gdb.GdbError("Sorry, obtaining the current task is not allowed "
> "while running in userspace(EL0)")
>+ elif utils.is_target_arch("riscv"):
>+ current_tp = gdb.parse_and_eval("$tp")
>+ scratch_reg = gdb.parse_and_eval("$sscratch")
>+
>+ # by default tp points to current task
>+ current_task = current_tp.cast(task_ptr_type)
>+
>+ # scratch register is set 0 in trap handler after entering kernel.
>+ # When hart is in user mode, scratch register is pointing to task_struct.
>+ # and tp is used by user mode. So when scratch register holds larger value
>+ # (negative address as ulong is larger value) than tp, then use scratch register.
>+ if (scratch_reg.cast(utils.get_ulong_type()) > current_tp.cast(utils.get_ulong_type())):
>+ current_task = scratch_reg.cast(task_ptr_type)
>+
>+ return current_task.dereference()
> else:
> raise gdb.GdbError("Sorry, obtaining the current task is not yet "
> "supported with this arch")
>--
>2.42.0
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-11-02 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 23:38 [PATCH v6] scripts/gdb: add lx_current support for riscv Deepak Gupta
2023-11-02 15:45 ` Deepak Gupta [this message]
2023-11-02 15:56 ` Andrew Morton
2023-11-02 15:58 ` Deepak Gupta
-- strict thread matches above, loose matches on Subject: below --
2023-10-28 4:58 Deepak Gupta
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=ZUPEDWofcqgzsgMS@debug.ba.rivosinc.com \
--to=debug@rivosinc.com \
--cc=ajones@ventanamicro.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=development@efficientek.com \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul.walmsley@sifive.com \
--cc=woodrow.shen@sifive.com \
--cc=xiehuan09@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).