From: Matthew Wilcox <willy@infradead.org>
To: Zhu Hengbo <zhuhengbo@iscas.ac.cn>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Suren Baghdasaryan <surenb@google.com>,
Alexandre Ghiti <alexghiti@rivosinc.com>,
Andrew Morton <akpm@linux-foundation.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: add tracepoints for page fault
Date: Mon, 15 Jul 2024 14:36:05 +0100 [thread overview]
Message-ID: <ZpUlxa2yqtkVvUBb@casper.infradead.org> (raw)
In-Reply-To: <20240715101400.39103-1-zhuhengbo@iscas.ac.cn>
On Mon, Jul 15, 2024 at 10:13:55AM +0000, Zhu Hengbo wrote:
> Introduce page_fault_user and page_fault_kernel for riscv page fault.
> Help to get more detail information when page fault happen.
Why be different from x86?
TP_printk("address=%ps ip=%ps error_code=0x%lx",
(void *)__entry->address, (void *)__entry->ip,
__entry->error_code) );
adding the instruction pointer (ip) seems like it would be useful.
> + TP_printk("user page fault, address=%ps cause=0x%lx",
> + (void *)__entry->address, __entry->cause)
next prev parent reply other threads:[~2024-07-15 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 10:13 [PATCH] riscv: add tracepoints for page fault Zhu Hengbo
2024-07-15 13:36 ` Matthew Wilcox [this message]
2024-07-17 8:27 ` [PATCH v2] " Zhu Hengbo
2024-07-17 14:55 ` Matthew Wilcox
2024-07-18 1:29 ` Zhu Hengbo
2024-07-18 1:34 ` Zhu Hengbo
2024-07-20 10:18 ` Jisheng Zhang
2024-07-22 3:21 ` Zhu Hengbo
2024-07-22 3:26 ` Zhu Hengbo
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=ZpUlxa2yqtkVvUBb@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alexghiti@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=surenb@google.com \
--cc=wangkefeng.wang@huawei.com \
--cc=zhuhengbo@iscas.ac.cn \
/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