From: Steven Rostedt <rostedt@goodmis.org>
To: Rabin Vincent <rabin@rab.in>
Cc: Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] tracing: don't busy wait in buffer splice
Date: Fri, 7 Nov 2014 19:04:13 -0500 [thread overview]
Message-ID: <20141107190413.28a2ae84@gandalf.local.home> (raw)
In-Reply-To: <20141107132106.0c318068@gandalf.local.home>
On Fri, 7 Nov 2014 13:21:06 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> This also needs to be marked for stable. I'll start looking at how far
> this goes back. I'm thinking it may go back as far as the splice code
> was created.
Actually, it is broken back to 3.16. 3.15 and before was safe because
it was still using the mockup poll_wait_pipe() that would wake up every
1/10 of a second to see if something was in the buffer.
See commit: b1169cc69ba9 "tracing: Remove mock up poll wait function"
-- Steve
next prev parent reply other threads:[~2014-11-08 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 21:26 Rabin Vincent
2014-11-06 21:26 ` [PATCH 2/2] tracing: don't risk busy looping " Rabin Vincent
2014-11-07 18:21 ` [PATCH 1/2] tracing: don't busy wait " Steven Rostedt
2014-11-08 0:04 ` Steven Rostedt [this message]
2014-11-10 18:46 ` [PATCHv2] " Rabin Vincent
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=20141107190413.28a2ae84@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rabin@rab.in \
/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
all inboxes | Powered by JetHome®