qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Emilio G. Cota" <cota@braap.org>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org,
	Peter Crosthwaite <crosthwaite.peter@gmail.com>,
	Stefan Weil <sw@weilnetz.de>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Peter Xu <peterx@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 1/3] qsp: QEMU's Synchronization Profiler
Date: Thu, 16 Aug 2018 00:29:33 -0400	[thread overview]
Message-ID: <20180816042933.GA17638@flamenco> (raw)
In-Reply-To: <20180815235514.GA23767@flamenco>

On Wed, Aug 15, 2018 at 19:55:14 -0400, Emilio G. Cota wrote:
> On Wed, Aug 15, 2018 at 00:53:23 -0400, Emilio G. Cota wrote:
> > On Wed, Aug 15, 2018 at 11:09:42 +0800, Fam Zheng wrote:
> > > On Mon, 08/13 13:11, Emilio G. Cota wrote:
> > > > +  --enable-sync-profiler) sync_profiler="yes"
> > > > +  ;;
> > > 
> > > Curious, not asking for a change: can this be made a runtime option instead of
> > > compile time, since there's no library dependencies? That should make this
> > > somewhat easier to use.
> > 
> > Good point. I'll do some profiling tomorrow to see how the latency
> > of the locking primitives could be minimized (ideally, not using
> > the profiler should just add a well-predicted branch).
> 
> I reduced it to just a branch, but still, I measured a few percentage
> points (1-2%, depending on the machine) slowdown when this is a
> run-time option. (This is for a bootup+shutdown test of a guest.)
> 
> So I'll keep it as a build-time option, then.

I looked further into this. Turns out we don't need the branch at all;
we can make indirect calls via function pointers, where the
pointers are set by qsp_enable/disable().

Overhead of doing things this way is within noise range, since
compilers and CPUs are so good at dealing with indirect calls.

I'll send a v2 tomorrow.

		Emilio

  reply	other threads:[~2018-08-16  4:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 17:11 [Qemu-devel] [PATCH 0/3] synchronization profiler Emilio G. Cota
2018-08-13 17:11 ` [Qemu-devel] [PATCH 1/3] qsp: QEMU's Synchronization Profiler Emilio G. Cota
2018-08-14  8:13   ` Paolo Bonzini
2018-08-15  0:44     ` Emilio G. Cota
2018-08-15  4:29       ` Markus Armbruster
2018-08-15  3:09   ` Fam Zheng
2018-08-15  4:53     ` Emilio G. Cota
2018-08-15  7:04       ` Fam Zheng
2018-08-15 23:55       ` Emilio G. Cota
2018-08-16  4:29         ` Emilio G. Cota [this message]
2018-08-16  4:36           ` Fam Zheng
2018-08-13 17:11 ` [Qemu-devel] [PATCH 2/3] monitor: show sync profiling info with 'info sync' Emilio G. Cota
2018-08-14  8:14   ` Paolo Bonzini
2018-08-15  1:26     ` Emilio G. Cota
2018-08-16 13:20       ` Peter Xu
2018-08-14  9:43   ` Dr. David Alan Gilbert
2018-08-15  1:33     ` Emilio G. Cota
2018-08-14 16:03   ` Markus Armbruster
2018-08-13 17:11 ` [Qemu-devel] [PATCH 3/3] qsp: track BQL callers directly Emilio G. Cota
2018-08-15 23:30 ` [Qemu-devel] [PATCH 0/3] synchronization profiler no-reply

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=20180816042933.GA17638@flamenco \
    --to=cota@braap.org \
    --cc=armbru@redhat.com \
    --cc=crosthwaite.peter@gmail.com \
    --cc=dgilbert@redhat.com \
    --cc=famz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=sw@weilnetz.de \
    /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).