From: <Conor.Dooley@microchip.com>
To: <debug@rivosinc.com>
Cc: <ajones@ventanamicro.com>, <aou@eecs.berkeley.edu>,
<jan.kiszka@siemens.com>, <kbingham@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>,
<palmer@dabbelt.com>, <paul.walmsley@sifive.com>
Subject: Re: [PATCH v4] scripts/gdb: add lx_current support for riscv
Date: Tue, 15 Nov 2022 21:23:29 +0000 [thread overview]
Message-ID: <d65bddf3-c58a-1420-bff9-8333c10edb56@microchip.com> (raw)
In-Reply-To: <20221115204003.1866421-1-debug@rivosinc.com>
Hey Deepak,
On 15/11/2022 20:40, Deepak Gupta wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> 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)
>
> Patch also adds new cached type "ulong" in scripts/gdb/linux/utils.py
>
> Since patch has changed a little bit from v1 and I didn't include
> changelog earlier, here it is.
This bit here needs to go below the --- line as it should not end up
in the commit logs (as everything below the --- is ignored.
>
> ---
> 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
> ---
>
> Signed-off-by: Deepak Gupta <debug@rivosinc.com>
> Reviewed-by: Andrew Jones <ajones@ventanamicro.com>
And this bit needs to go above the first --- line as it does need
to go into the commit logs.
The order is:
$subject
body
tags
---
changelog & comments
diffs
For example, this is what I see when I apply the patch:
$ b4 shazam 20221115204003.1866421-1-debug@rivosinc.com
Grabbing thread from lore.kernel.org/all/20221115204003.1866421-1-debug%40rivosinc.com/t.mbox.gz
Checking for newer revisions on https://lore.kernel.org/all/
Analyzing 13 messages in the thread
Will use the latest revision: v4
You can pick other revisions using the -vN flag
Checking attestation on all messages, may take a moment...
---
✓ [PATCH v4] scripts/gdb: add lx_current support for riscv
---
✓ Signed: DKIM/rivosinc-com.20210112.gappssmtp.com (From: debug@rivosinc.com)
---
Total patches: 1
---
Applying: scripts/gdb: add lx_current support for riscv
$ git show
commit 5c93617c68980f767e312fc51849d78093f56e72 (HEAD)
Author: Deepak Gupta <debug@rivosinc.com>
Date: Tue Nov 15 12:40:03 2022 -0800
scripts/gdb: add lx_current support for riscv
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)
Patch also adds new cached type "ulong" in scripts/gdb/linux/utils.py
Since patch has changed a little bit from v1 and I didn't include
changelog earlier, here it is.
Taken a wee bit of the back and forth, Looks like you're nearly
there though!
Conor.
next prev parent reply other threads:[~2022-11-15 21:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 19:59 Updating python gdb command lx_current " debug
2022-11-11 19:59 ` [PATCH] gdb-script: updated " debug
2022-11-13 0:13 ` Conor Dooley
2022-11-13 14:14 ` Conor Dooley
2022-11-13 11:06 ` Andrew Jones
2022-11-15 1:29 ` [PATCH v2] scripts/gdb: add lx_current support " Deepak Gupta
2022-11-15 6:46 ` Andrew Jones
2022-11-15 8:49 ` [PATCH v3] " Deepak Gupta
2022-11-15 14:38 ` Conor Dooley
[not found] ` <CAKC1njRi9C0m3JKpu0ebAFCC25161EST=tFFWiAj1yZBbnak6A@mail.gmail.com>
2022-11-15 18:06 ` Conor.Dooley
2022-11-15 18:43 ` Deepak Gupta
2022-11-15 18:06 ` Andrew Jones
2022-11-15 20:40 ` [PATCH v4] " Deepak Gupta
2022-11-15 21:23 ` Conor.Dooley [this message]
2022-11-15 22:10 ` [PATCH v5] " Deepak Gupta
2022-11-16 8:16 ` Andrew Jones
2022-11-16 22:24 ` Deepak Gupta
2022-12-09 1:24 ` Palmer Dabbelt
2023-01-02 9:09 ` Jan Kiszka
2023-10-05 5:29 ` Hsieh-Tseng Shen
2023-10-26 23:41 ` 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=d65bddf3-c58a-1420-bff9-8333c10edb56@microchip.com \
--to=conor.dooley@microchip.com \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=debug@rivosinc.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=paul.walmsley@sifive.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
all inboxes | Powered by JetHome®