From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <dunlapg@umich.edu>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2 6/8] xenalyze: handle more events in sched_process
Date: Tue, 12 May 2015 16:53:44 +0200 [thread overview]
Message-ID: <1431442424.2978.53.camel@citrix.com> (raw)
In-Reply-To: <CAFLBxZbXaLDfjErb+9uyFNYgwepMNv9HrysR5bEhDNLK0MdjUA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 892 bytes --]
On Thu, 2015-05-07 at 18:42 +0100, George Dunlap wrote:
> On Thu, May 7, 2015 at 6:28 PM, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
> > Is it a candidate for dropping from the hypervisor then? No use keeping
> > useless tracepoints.
>
> Well it would have to be replaced with something more informative.
>
Indeed. In fact, if one wants to figure out what happens when changing
some scheduling parameters, it is actually helpful to see the record
about the change in the trace. Provided such record is informative
enough, of course.
> "Someone changed something" is pretty useless, but it's still more
> information than nothing at all.
>
Agreed.
> (Presumably the replacement would be
> a per-scheduler tracepoint.)
>
Probably, so we can actually print the details of the adjustment being
done.
I'm adding this to my todo list. :-)
Regards,
Dario
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-05-12 14:53 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 10:35 [PATCH v2 0/8] add xenalyze to staging Olaf Hering
2015-05-07 10:35 ` [PATCH v2 1/8] xenalyze: add to tools/xentrace/xenalyze Olaf Hering
2015-05-07 16:45 ` George Dunlap
2015-05-08 5:20 ` Wei Liu
2015-05-11 14:15 ` Olaf Hering
2015-05-11 14:23 ` Ian Campbell
2015-05-11 14:28 ` Olaf Hering
2015-05-11 14:33 ` George Dunlap
2015-05-11 14:47 ` Olaf Hering
2015-05-12 8:45 ` Ian Campbell
2015-05-12 9:09 ` George Dunlap
2015-05-07 10:35 ` [PATCH v2 2/8] xenalyze: increase NR_CPUS to 256 Olaf Hering
2015-05-07 16:52 ` George Dunlap
2015-05-08 6:14 ` Olaf Hering
2015-05-08 5:22 ` Wei Liu
2015-05-07 10:35 ` [PATCH v2 3/8] xenalyze: print newline after unknown hvm events Olaf Hering
2015-05-07 16:53 ` George Dunlap
2015-05-08 5:22 ` Wei Liu
2015-05-07 10:35 ` [PATCH v2 4/8] xenalyze: include odd mmio states in default output Olaf Hering
2015-05-07 16:53 ` George Dunlap
2015-05-08 5:23 ` Wei Liu
2015-05-07 10:35 ` [PATCH v2 5/8] xenalyze: handle TRC_TRACE_WRAP_BUFFER Olaf Hering
2015-05-07 17:04 ` George Dunlap
2015-05-08 5:24 ` Wei Liu
2015-05-07 10:35 ` [PATCH v2 6/8] xenalyze: handle more events in sched_process Olaf Hering
2015-05-07 17:13 ` George Dunlap
2015-05-07 17:28 ` Andrew Cooper
2015-05-07 17:42 ` George Dunlap
2015-05-12 14:53 ` Dario Faggioli [this message]
2015-05-08 5:30 ` Wei Liu
2015-05-08 6:18 ` Olaf Hering
2015-05-07 10:35 ` [PATCH v2 7/8] xenalyze: remove traling whitespaces Olaf Hering
2015-05-07 17:15 ` George Dunlap
2015-05-07 17:26 ` Andrew Cooper
2015-05-07 17:34 ` George Dunlap
2015-05-08 6:22 ` Olaf Hering
2015-05-08 5:32 ` Wei Liu
2015-05-07 10:35 ` [PATCH v2 8/8] xenalyze: remove argp_program_version Olaf Hering
2015-05-07 17:18 ` George Dunlap
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=1431442424.2978.53.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dunlapg@umich.edu \
--cc=xen-devel@lists.xen.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.