[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZpUlxa2yqtkVvUBb@casper.infradead.org>
Date: Mon, 15 Jul 2024 14:36:05 +0100
From: Matthew Wilcox <willy@...radead.org>
To: Zhu Hengbo <zhuhengbo@...as.ac.cn>
Cc: Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Suren Baghdasaryan <surenb@...gle.com>,
Alexandre Ghiti <alexghiti@...osinc.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Kefeng Wang <wangkefeng.wang@...wei.com>,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] riscv: add tracepoints for page fault
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)
Powered by blists - more mailing lists