From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Aravinda Prasad <aravinda@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: nfont@linux.vnet.ibm.com, naveen.n.rao@linux.vnet.ibm.com,
aravinda@linux.vnet.ibm.com
Subject: Re: [v3] powerpc/pseries: Export raw per-CPU VPA data via debugfs
Date: Mon, 22 Oct 2018 20:38:39 +1100 (AEDT) [thread overview]
Message-ID: <42ds0J1SZKz9sDC@ozlabs.org> (raw)
In-Reply-To: <153969060579.20425.17023211720854729638.stgit@aravinda>
On Tue, 2018-10-16 at 11:50:05 UTC, Aravinda Prasad wrote:
> This patch exports the raw per-CPU VPA data via debugfs.
> A per-CPU file is created which exports the VPA data of
> that CPU to help debug some of the VPA related issues or
> to analyze the per-CPU VPA related statistics.
>
> v3: Removed offline CPU check.
>
> v2: Included offline CPU check and other review comments.
>
> Signed-off-by: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/c6c26fb55e8e4b3fc376be56116859
cheers
prev parent reply other threads:[~2018-10-22 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 11:50 [PATCH v3] powerpc/pseries: Export raw per-CPU VPA data via debugfs Aravinda Prasad
2018-10-22 9:38 ` Michael Ellerman [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=42ds0J1SZKz9sDC@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=aravinda@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.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).