From: David Long <dave.long@linaro.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Documentation: kprobes: Document jprobes stack copying limitations
Date: Mon, 15 Aug 2016 15:41:00 +0000 [thread overview]
Message-ID: <57B1E28C.10806@linaro.org> (raw)
In-Reply-To: <20160815093243.4576258a@lwn.net>
On 08/15/2016 11:32 AM, Jonathan Corbet wrote:
> On Mon, 15 Aug 2016 10:49:36 -0400
> David Long <dave.long@linaro.org> wrote:
>
>> On 08/15/2016 10:25 AM, Jonathan Corbet wrote:
>>> On Fri, 12 Aug 2016 16:24:44 -0400
>>> David Long <dave.long@linaro.org> wrote:
>>>
>>>> Some architectures (i.e.: sparc64 and arm64) make reasonable partial stack
>>>> duplication for jprobes problematic. Document this.
>>>
>>> Applied to the docs tree, thanks.
>>>
>>> jon
>>>
>>
>> Was kind of hoping to see an ack (or critique) from a sparc maintainer.
>
> So are you saying you don't want the patch applied at this point?
>
> jon
>
I think we can apply it. It's not looking like we're going to get
comments from a sparc/kprobes maintainer. The need for this change was
first addressed on the sparc email alias exactly one week ago, which is
maybe long enough to wait.
Sorry for the trouble,
-dl
WARNING: multiple messages have this Message-ID (diff)
From: dave.long@linaro.org (David Long)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Documentation: kprobes: Document jprobes stack copying limitations
Date: Mon, 15 Aug 2016 11:41:00 -0400 [thread overview]
Message-ID: <57B1E28C.10806@linaro.org> (raw)
In-Reply-To: <20160815093243.4576258a@lwn.net>
On 08/15/2016 11:32 AM, Jonathan Corbet wrote:
> On Mon, 15 Aug 2016 10:49:36 -0400
> David Long <dave.long@linaro.org> wrote:
>
>> On 08/15/2016 10:25 AM, Jonathan Corbet wrote:
>>> On Fri, 12 Aug 2016 16:24:44 -0400
>>> David Long <dave.long@linaro.org> wrote:
>>>
>>>> Some architectures (i.e.: sparc64 and arm64) make reasonable partial stack
>>>> duplication for jprobes problematic. Document this.
>>>
>>> Applied to the docs tree, thanks.
>>>
>>> jon
>>>
>>
>> Was kind of hoping to see an ack (or critique) from a sparc maintainer.
>
> So are you saying you don't want the patch applied at this point?
>
> jon
>
I think we can apply it. It's not looking like we're going to get
comments from a sparc/kprobes maintainer. The need for this change was
first addressed on the sparc email alias exactly one week ago, which is
maybe long enough to wait.
Sorry for the trouble,
-dl
WARNING: multiple messages have this Message-ID (diff)
From: David Long <dave.long@linaro.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: sparclinux@vger.kernel.org, daniel.thompson@linaro.org,
Ananth N Mavinakayanahalli <ananth@linux.vnet.ibm.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
marc.zyngier@arm.com, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] Documentation: kprobes: Document jprobes stack copying limitations
Date: Mon, 15 Aug 2016 11:41:00 -0400 [thread overview]
Message-ID: <57B1E28C.10806@linaro.org> (raw)
In-Reply-To: <20160815093243.4576258a@lwn.net>
On 08/15/2016 11:32 AM, Jonathan Corbet wrote:
> On Mon, 15 Aug 2016 10:49:36 -0400
> David Long <dave.long@linaro.org> wrote:
>
>> On 08/15/2016 10:25 AM, Jonathan Corbet wrote:
>>> On Fri, 12 Aug 2016 16:24:44 -0400
>>> David Long <dave.long@linaro.org> wrote:
>>>
>>>> Some architectures (i.e.: sparc64 and arm64) make reasonable partial stack
>>>> duplication for jprobes problematic. Document this.
>>>
>>> Applied to the docs tree, thanks.
>>>
>>> jon
>>>
>>
>> Was kind of hoping to see an ack (or critique) from a sparc maintainer.
>
> So are you saying you don't want the patch applied at this point?
>
> jon
>
I think we can apply it. It's not looking like we're going to get
comments from a sparc/kprobes maintainer. The need for this change was
first addressed on the sparc email alias exactly one week ago, which is
maybe long enough to wait.
Sorry for the trouble,
-dl
next prev parent reply other threads:[~2016-08-15 15:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 20:24 [PATCH] Documentation: kprobes: Document jprobes stack copying limitations David Long
2016-08-12 20:24 ` David Long
2016-08-12 20:24 ` David Long
2016-08-12 23:46 ` Masami Hiramatsu
2016-08-12 23:46 ` Masami Hiramatsu
2016-08-12 23:46 ` Masami Hiramatsu
2016-08-15 14:25 ` Jonathan Corbet
2016-08-15 14:25 ` Jonathan Corbet
2016-08-15 14:25 ` Jonathan Corbet
2016-08-15 14:49 ` David Long
2016-08-15 14:49 ` David Long
2016-08-15 14:49 ` David Long
2016-08-15 15:32 ` Jonathan Corbet
2016-08-15 15:32 ` Jonathan Corbet
2016-08-15 15:32 ` Jonathan Corbet
2016-08-15 15:41 ` David Long [this message]
2016-08-15 15:41 ` David Long
2016-08-15 15:41 ` David Long
2016-08-15 15:41 ` Catalin Marinas
2016-08-15 15:41 ` Catalin Marinas
2016-08-15 15:41 ` Catalin Marinas
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=57B1E28C.10806@linaro.org \
--to=dave.long@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.