linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: ananth@in.ibm.com
Cc: Scott Wood <scottwood@freescale.com>,
	linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
	ego@linux.vnet.ibm.com, mingo@kernel.org
Subject: Re: powerpc: Add user-return-notifier support
Date: Tue, 08 Sep 2015 19:24:39 +1000	[thread overview]
Message-ID: <1441704279.7601.6.camel@ellerman.id.au> (raw)
In-Reply-To: <20150902050958.GC1196@in.ibm.com>

On Wed, 2015-09-02 at 10:39 +0530, Ananth N Mavinakayanahalli wrote:
> On Tue, Sep 01, 2015 at 10:29:12PM -0500, Scott Wood wrote:
> 
> > Why is this selected by KVM on PPC if KVM on PPC doesn't use it?  What is the 
> > user you're trying to enable?
> 
> I copied Paul and Gautham to get their thoughts on whether it is
> something they could use on Power. At this time, apart from enabling the
> feature, I do not have a specific usecase for it. We can park this patch
> pending a real user on powerpc.

OK, thanks for hashing that out guys. I think parking it is the best solution
for now, we could merge it and disable it somehow, but that would be ugly and
prone to breaking.

Do we want to do something like this?

cheers

diff --git a/Documentation/features/arch-support.txt b/Documentation/features/arch-support.txt
index d22a1095e661..3e2cf6161cf4 100644
--- a/Documentation/features/arch-support.txt
+++ b/Documentation/features/arch-support.txt
@@ -8,4 +8,5 @@ The meaning of entries in the tables is:
     | ok |  # feature supported by the architecture
     |TODO|  # feature not yet supported by the architecture
     | .. |  # feature cannot be supported by the hardware
+    |n/a |  # feature is not needed/wanted/meaningful for the architecture
 
diff --git a/Documentation/features/debug/user-ret-profiler/arch-support.txt b/Documentation/features/debug/user-ret-profiler/arch-support.txt
index 44cc1ff3f603..669813180dc5 100644
--- a/Documentation/features/debug/user-ret-profiler/arch-support.txt
+++ b/Documentation/features/debug/user-ret-profiler/arch-support.txt
@@ -27,7 +27,7 @@
     |       nios2: | TODO |
     |    openrisc: | TODO |
     |      parisc: | TODO |
-    |     powerpc: | TODO |
+    |     powerpc: | n/a  |    # http://lkml.kernel.org/r/20150825054110.GD3815@in.ibm.com
     |        s390: | TODO |
     |       score: | TODO |
     |          sh: | TODO |

  reply	other threads:[~2015-09-08  9:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25  5:41 [PATCH] powerpc: Add user-return-notifier support Ananth N Mavinakayanahalli
2015-08-31 10:35 ` Michael Ellerman
2015-09-01  6:41   ` Ananth N Mavinakayanahalli
2015-09-02  0:03     ` Scott Wood
2015-09-02  2:37       ` Ananth N Mavinakayanahalli
2015-09-02  3:29         ` Scott Wood
2015-09-02  5:09           ` Ananth N Mavinakayanahalli
2015-09-08  9:24             ` Michael Ellerman [this message]
2015-09-08 10:51               ` Ananth N Mavinakayanahalli

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=1441704279.7601.6.camel@ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=ananth@in.ibm.com \
    --cc=ego@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mingo@kernel.org \
    --cc=paulus@samba.org \
    --cc=scottwood@freescale.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).