linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Pratyush Anand <panand@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ingo Molnar <mingo@redhat.com>
Cc: Linux USB <linux-usb@vger.kernel.org>,
	linux-kernel@vger.kernel.org,
	Chunyan Zhang <zhang.chunyan@linaro.org>
Subject: Re: [PATCH] usb: gadget: functions: add ftrace export over USB
Date: Fri, 14 Jul 2017 09:56:12 +0300	[thread overview]
Message-ID: <87d1935wxf.fsf@linux.intel.com> (raw)
In-Reply-To: <16a6940d-d071-cd2d-5911-dad427a13cb0@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]


Hi,

Pratyush Anand <panand@redhat.com> writes:
> Hi Felipe,
>
> On Friday 09 June 2017 11:43 AM, Felipe Balbi wrote:
>> +static void notrace ftrace_write(struct trace_export *ftrace, const void *buf,
>> +				 unsigned int len)
>> +{
>> +	struct usb_ftrace		*trace = ftrace_to_trace(ftrace);
>> +	struct usb_request		*req = next_request(&trace->list);
>> +
>> +	if (!req)
>> +		return;
>> +
>> +	if (!trace->in->enabled)
>> +		return;
>> +
>> +	req->buf = kmemdup(buf, len, GFP_ATOMIC);
>
> Probably we can avoid the copy of trace data.

not with current setup. I have no control over data's lifetime. If I
did, then this would be zero-copy.

> We can make write() call of "struct trace_export" as posted. Can have a 

that would require further patching in trace core which is not part of
$subject. Also, if we turn this into asynchronous calls, we could run
out of trace buffer before the first chunk of data is transferred over
to the other side.

> write_complete() callback function implemented in  struct trace_export,which 
> can be called from your ftrace_complete().

well, you're welcome to propose a patch :-)

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2017-07-14  6:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09  6:13 [PATCH] usb: gadget: functions: add ftrace export over USB Felipe Balbi
2017-06-09 10:28 ` Felipe Balbi
2017-06-09 11:15   ` Felipe Balbi
2017-07-14  5:52   ` Pratyush Anand
2017-07-14  6:53     ` Felipe Balbi
2017-07-14 21:44     ` Steven Rostedt
2017-06-09 14:02 ` Steven Rostedt
2017-06-09 14:05   ` Felipe Balbi
2017-06-09 15:07     ` Steven Rostedt
2017-06-10  3:38 ` kbuild test robot
2017-06-12 10:39   ` Felipe Balbi
2017-06-10  4:02 ` kbuild test robot
2017-07-13 11:40 ` Felipe Balbi
2017-07-14  5:31 ` Pratyush Anand
2017-07-14  6:56   ` Felipe Balbi [this message]
2019-03-21  9:38 ` Felipe Balbi
2019-03-21 16:37   ` Steven Rostedt
2019-03-22 11:49     ` Felipe Balbi
2019-03-22 12:22       ` Steven Rostedt
2019-03-22 12:27         ` Felipe Balbi

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=87d1935wxf.fsf@linux.intel.com \
    --to=felipe.balbi@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=panand@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=zhang.chunyan@linaro.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).