From: Steven Rostedt <rostedt@goodmis.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
linux-mm@kvack.org, akpm@linux-foundation.org,
naoya.horiguchi@linux.dev, Ingo Molnar <mingo@redhat.com>,
Zi Yan <ziy@nvidia.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
John Hubbard <jhubbard@nvidia.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 2/2] mm/migration: Add trace events for base page and HugeTLB migrations
Date: Tue, 25 Jan 2022 10:16:06 -0500 [thread overview]
Message-ID: <20220125101606.3cfb5561@gandalf.local.home> (raw)
In-Reply-To: <Ye/7EWJ576hdkWDg@casper.infradead.org>
On Tue, 25 Jan 2022 13:28:49 +0000
Matthew Wilcox <willy@infradead.org> wrote:
> On Tue, Jan 25, 2022 at 08:38:25AM +0530, Anshuman Khandual wrote:
> > + TP_printk("addr=%lx, pte=%lx order=%d", __entry->addr, __entry->pte, __entry->order)
>
> In these days of increasingly advanced Rowhammer attacks, is it wise
> to let userspace know exactly which physical addresses are being
> used for virtual addresses?
Is it an issue if this is only available for privileged users?
With tracing, you can just create a kprobe to get the same information for
you as well, so this isn't giving a user anything they do not already have.
-- Steve
prev parent reply other threads:[~2022-01-25 15:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 3:08 [PATCH V2 0/2] mm/migration: Add trace events Anshuman Khandual
2022-01-25 3:08 ` [PATCH V2 1/2] mm/migration: Add trace events for THP migrations Anshuman Khandual
2022-01-25 3:08 ` [PATCH V2 2/2] mm/migration: Add trace events for base page and HugeTLB migrations Anshuman Khandual
2022-01-25 9:41 ` kernel test robot
2022-01-25 9:41 ` kernel test robot
2022-01-25 10:28 ` Anshuman Khandual
2022-01-27 4:07 ` Andrew Morton
2022-01-27 4:52 ` Anshuman Khandual
2022-01-27 6:55 ` Anshuman Khandual
2022-01-25 11:13 ` kernel test robot
2022-01-25 13:28 ` Matthew Wilcox
2022-01-25 15:16 ` Steven Rostedt [this message]
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=20220125101606.3cfb5561@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=naoya.horiguchi@linux.dev \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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).