From: Paul Mackerras <paulus@ozlabs.org>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: linuxppc-dev@lists.ozlabs.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH kernel] KVM: PPC: Expose userspace mm context id via debugfs
Date: Tue, 17 Jul 2018 12:01:19 +1000 [thread overview]
Message-ID: <20180717020119.GA11424@fergus> (raw)
In-Reply-To: <20180712073026.19463-1-aik@ozlabs.ru>
On Thu, Jul 12, 2018 at 05:30:26PM +1000, Alexey Kardashevskiy wrote:
> This adds a debugfs entry with mm context id of a process which is using
> KVM. This id is an index in the process table so the userspace can dump
> that tree provided it is granted access to /dev/mem.
Is the main intention here to be able to look at the PTEs for the
process that owns the VM? If so, that doesn't seem particularly
KVM-specific, so perhaps something under powerpc/ in debugfs would be
more appropriate.
Is the information in /proc/<pid>/pagemap sufficient for what you
need?
Also, this doesn't seem very useful if /dev/mem is unavailable or
restricted, as it is in most distros these days.
How about a file under debugfs where you can just read out the PTEs
for a given process?
Paul.
prev parent reply other threads:[~2018-07-17 2:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 7:30 [PATCH kernel] KVM: PPC: Expose userspace mm context id via debugfs Alexey Kardashevskiy
2018-07-17 2:01 ` Paul Mackerras [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=20180717020119.GA11424@fergus \
--to=paulus@ozlabs.org \
--cc=aik@ozlabs.ru \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).