linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Cc: Yordan Karadzhov <y.karadz@gmail.com>
Subject: Re: [PATCH v2] trace-cruncher: Add API to set tracing CPU affinity
Date: Mon, 17 Jan 2022 20:16:04 -0500	[thread overview]
Message-ID: <20220117201604.7b635a25@gandalf.local.home> (raw)
In-Reply-To: <20220117201231.414a4799@gandalf.local.home>

On Mon, 17 Jan 2022 20:12:31 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:

> +++ b/src/ftracepy.c
> @@ -372,11 +372,21 @@ static PyMethodDef ftracepy_methods[] = {
>  	 METH_VARARGS | METH_KEYWORDS,
>  	 "Define a kretprobe."
>  	},
> +	{"reset_affinity",
> +	 (PyCFunction) PyFtrace_reset_affinity,
> +	 METH_VARARGS | METH_KEYWORDS,
> +	 "Set an instance tracing affinity to all CPUs"
> +	},
>  	{"hist",
>  	 (PyCFunction) PyFtrace_hist,
>  	 METH_VARARGS | METH_KEYWORDS,
>  	 "Define a histogram."
>  	},
> +	{"set_affinity",
> +	 (PyCFunction) PyFtrace_set_affinity,
> +	 METH_VARARGS | METH_KEYWORDS,
> +	 "Return tracing affinity of an instance."

Bah, that should have been:

	"Set tracing affinity of an instance."

I wrote that while working on the "get_affinity" in libtracefs. :-p

v3 soon.

-- Steve


> +	},
>  	{"set_ftrace_loglevel",
>  	 (PyCFunction) PyFtrace_set_ftrace_loglevel,
>  	 METH_VARARGS | METH_KEYWORDS,

      reply	other threads:[~2022-01-18  1:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18  1:12 [PATCH v2] trace-cruncher: Add API to set tracing CPU affinity Steven Rostedt
2022-01-18  1:16 ` Steven Rostedt [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=20220117201604.7b635a25@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=y.karadz@gmail.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).