All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lluís Vilanova" <vilanova@ac.upc.edu>
To: "Emilio G. Cota" <cota@braap.org>
Cc: Richard Henderson <rth@twiddle.net>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v7 0/7] trace: [tcg] Optimize per-vCPU tracing states with separate TB caches
Date: Sun, 11 Jun 2017 15:31:18 +0300	[thread overview]
Message-ID: <871sqqpuy1.fsf@frigg.lan> (raw)
In-Reply-To: <20170601195544.GB10517@flamenco> (Emilio G. Cota's message of "Thu, 1 Jun 2017 15:55:44 -0400")

Emilio G Cota writes:

> On Fri, Jan 13, 2017 at 21:48:09 +0100, Lluís Vilanova wrote:
> (snip)
>> To handle both issues, this series integrates the dynamic tracing event state
>> into the TB hashing function, so that vCPUs tracing different events will use
>> separate TBs. Note that only events with the 'vcpu' property are used for
>> hashing (as stored in the bitmap of CPUState->trace_dstate).

> Is this going to be picked up by anyone? AFAICT the patchset is close
> to being merge-ready.

> Lluís: I'm very interested in your instrumentation work [1]:

> - How much up to date are the branches in [1]? I couldn't find this
>   v7 iteration in there, although maybe I didn't look carefully enough.

> - Are you planning on upstreaming it? I have some time to help with
>   that if you're interested.

After your latest re-spin on this series, there's two basic pieces missing
upstream to have instrumentation:

* An interface to insert user callbacks on events.

* A useful mechanism to pass value place holders (values are later calculated)
  to these callbacks. This is useful when instrumenting an event before it
  happens (e.g., before an instruction is executed) to pass it some values that
  are only known afterwards (e.g., number of instructions in a BBL). I called
  them promises, and you can see an example in [2] (using an older API of QDBI).


> - Do you have instrumentation examples beyond what's in
>   docs/instrumentation.txt? In particular I'd like to see how the basic
>   block (BBL) instrumentation works, i.e. how a 'skeleton' simulator
>   would work to decode the guest instructions and also track their
>   dependences.

No, sorry, I never got around to writing such type of instrumentation
example. The closest I have is [2].


[2] https://projects.gso.ac.upc.edu/projects/qdbi-simpoint


> Thanks,

> 		Emilio

> [1] https://projects.gso.ac.upc.edu/projects/qemu-dbi


Cheers,
  Lluis

      parent reply	other threads:[~2017-06-11 12:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-13 20:48 [Qemu-devel] [PATCH v7 0/7] trace: [tcg] Optimize per-vCPU tracing states with separate TB caches Lluís Vilanova
2017-01-13 20:48 ` [Qemu-devel] [PATCH v7 1/7] exec: [tcg] Refactor flush of per-CPU virtual TB cache Lluís Vilanova
2017-01-13 20:48 ` [Qemu-devel] [PATCH v7 2/7] trace: Make trace_get_vcpu_event_count() inlinable Lluís Vilanova
2017-01-14  3:30   ` Richard Henderson
2017-01-15  2:00     ` Lluís Vilanova
2017-01-29 14:51       ` Lluís Vilanova
2017-01-13 20:48 ` [Qemu-devel] [PATCH v7 3/7] trace: [tcg] Delay changes to dynamic state when translating Lluís Vilanova
2017-01-14  3:38   ` Richard Henderson
2017-01-13 20:48 ` [Qemu-devel] [PATCH v7 4/7] exec: [tcg] Use different TBs according to the vCPU's dynamic tracing state Lluís Vilanova
2017-06-01 19:33   ` Emilio G. Cota
2017-01-13 20:48 ` [Qemu-devel] [PATCH v7 5/7] trace: [tcg] Do not generate TCG code to trace dinamically-disabled events Lluís Vilanova
2017-01-13 20:48 ` [Qemu-trivial] [PATCH v7 6/7] trace: [tcg, trivial] Re-align generated code Lluís Vilanova
2017-01-13 20:48   ` [Qemu-devel] " Lluís Vilanova
2017-01-13 20:48 ` [Qemu-trivial] [PATCH v7 7/7] trace: [trivial] Statically enable all guest events Lluís Vilanova
2017-01-13 20:48   ` [Qemu-devel] " Lluís Vilanova
2017-06-01 19:55 ` [Qemu-devel] [PATCH v7 0/7] trace: [tcg] Optimize per-vCPU tracing states with separate TB caches Emilio G. Cota
2017-06-06  9:54   ` Stefan Hajnoczi
2017-06-11 12:31   ` Lluís Vilanova [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=871sqqpuy1.fsf@frigg.lan \
    --to=vilanova@ac.upc.edu \
    --cc=cota@braap.org \
    --cc=ehabkost@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=stefanha@redhat.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 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.