Stefan Hajnoczi writes:
> On Mon, Sep 05, 2016 at 04:37:01PM +0200, Lluís Vilanova wrote:
>> I suppose that if you execute the stap script I pasted it will show the
>> proper
>> values. Then it's definitely a problem with Debian's userspace probes.
> Sorry for the delay. SystemTap static probes
On Mon, Sep 05, 2016 at 04:37:01PM +0200, Lluís Vilanova wrote:
> I suppose that if you execute the stap script I pasted it will show the proper
> values. Then it's definitely a problem with Debian's userspace probes.
Sorry for the delay. SystemTap static probes appear to work correctly on
Fedora
Masami Hiramatsu writes:
> On Mon, 05 Sep 2016 16:37:01 +0200
> Lluís Vilanova wrote:
>> Stefan Hajnoczi writes:
>>
>> > On Mon, Aug 29, 2016 at 08:46:02PM +0200, Lluís Vilanova wrote:
>> >> >> Also, I'm still not sure how to interact with QEMU's monitor interface
>> >> >> from
>> >> >> within
Daniel P Berrange writes:
> On Mon, Sep 05, 2016 at 08:29:54PM +0200, Lluís Vilanova wrote:
>> Daniel P Berrange writes:
>>
>> > On Mon, Aug 29, 2016 at 08:46:02PM +0200, Lluís Vilanova wrote:
>> >> Stefan Hajnoczi writes:
>> >>
>> >> > When SystemTap is used the QEMU monitor interface does noth
On Mon, 05 Sep 2016 16:37:01 +0200
Lluís Vilanova wrote:
> Stefan Hajnoczi writes:
>
> > On Mon, Aug 29, 2016 at 08:46:02PM +0200, Lluís Vilanova wrote:
> >> >> Also, I'm still not sure how to interact with QEMU's monitor interface
> >> >> from
> >> >> within the probe code (probes execute in k
On Mon, Sep 05, 2016 at 08:29:54PM +0200, Lluís Vilanova wrote:
> Daniel P Berrange writes:
>
> > On Mon, Aug 29, 2016 at 08:46:02PM +0200, Lluís Vilanova wrote:
> >> Stefan Hajnoczi writes:
> >>
> >> > When SystemTap is used the QEMU monitor interface does nothing.
> >>
> >> That's not what I'v
Daniel P Berrange writes:
> On Mon, Aug 29, 2016 at 08:46:02PM +0200, Lluís Vilanova wrote:
>> Stefan Hajnoczi writes:
>>
>> > When SystemTap is used the QEMU monitor interface does nothing.
>>
>> That's not what I've experienced. I was able to use a stap script to change
>> the
>> tracing stat
On Mon, Aug 29, 2016 at 08:46:02PM +0200, Lluís Vilanova wrote:
> Stefan Hajnoczi writes:
>
> > When SystemTap is used the QEMU monitor interface does nothing.
>
> That's not what I've experienced. I was able to use a stap script to change
> the
> tracing state of events:
>
>#!/usr/bin/env
Stefan Hajnoczi writes:
> On Mon, Aug 29, 2016 at 08:46:02PM +0200, Lluís Vilanova wrote:
>> >> Also, I'm still not sure how to interact with QEMU's monitor interface
>> >> from
>> >> within the probe code (probes execute in kernel mode, including "guru
>> >> mode"
>> >> code).
>>
>> > When Sys
On Mon, Aug 29, 2016 at 08:46:02PM +0200, Lluís Vilanova wrote:
> >> Also, I'm still not sure how to interact with QEMU's monitor interface from
> >> within the probe code (probes execute in kernel mode, including "guru mode"
> >> code).
>
> > When SystemTap is used the QEMU monitor interface does
Stefan Hajnoczi writes:
> On Wed, Aug 24, 2016 at 12:25:54PM +0200, Lluís Vilanova wrote:
>> Stefan Hajnoczi writes:
>>
>> > On Sun, Aug 21, 2016 at 02:32:34PM +0200, Lluís Vilanova wrote:
>> >> Unfortuntely, I've been unable to to make dtrace recognise QEMU's events
>> >> (I'm
>> >> only able t
On Wed, Aug 24, 2016 at 12:25:54PM +0200, Lluís Vilanova wrote:
> Stefan Hajnoczi writes:
>
> > On Sun, Aug 21, 2016 at 02:32:34PM +0200, Lluís Vilanova wrote:
> >> Unfortuntely, I've been unable to to make dtrace recognise QEMU's events
> >> (I'm
> >> only able to see the host kernel events). If
Stefan Hajnoczi writes:
> On Sun, Aug 21, 2016 at 02:32:34PM +0200, Lluís Vilanova wrote:
>> Unfortuntely, I've been unable to to make dtrace recognise QEMU's events (I'm
>> only able to see the host kernel events). If someone with more experience on
>> it
>> can help me use dtrace with QEMU's ev
On Sun, Aug 21, 2016 at 02:32:34PM +0200, Lluís Vilanova wrote:
> Unfortuntely, I've been unable to to make dtrace recognise QEMU's events (I'm
> only able to see the host kernel events). If someone with more experience on
> it
> can help me use dtrace with QEMU's events, I'll also add the support
Stefan Hajnoczi writes:
> On Fri, Aug 05, 2016 at 06:59:23PM +0200, Lluís Vilanova wrote:
>> The hypertrace channel allows guest code to emit events in QEMU (the host)
>> using
>> its tracing infrastructure (see "docs/trace.txt"). This works in both
>> 'system'
>> and 'user' modes. That is, hype
Luiz Capitulino writes:
> On Thu, 18 Aug 2016 14:53:27 +0100
> Stefan Hajnoczi wrote:
>> On Thu, Aug 18, 2016 at 12:22:18PM +0200, Lluís Vilanova wrote:
>> > Stefan Hajnoczi writes:
>> >
>> > > On Fri, Aug 05, 2016 at 06:59:23PM +0200, Lluís Vilanova wrote:
>> > >> The hypertrace channel al
On Fri, 19 Aug 2016 11:02:07 +0100
Stefan Hajnoczi wrote:
> > [1]
> > https://lcccna2016.sched.org/event/7JWL/trace-cmd-virt-server-a-status-update-steven-rostedt-red-hat?iframe=no&w=i:100;&sidebar=yes&bg=no
> >
>
> Cool, that's very interesting! I'll try to attend.
Good, see you then!
>
On Thu, Aug 18, 2016 at 12:19:50PM -0400, Steven Rostedt wrote:
> On Thu, 18 Aug 2016 11:54:24 +0100
> Stefan Hajnoczi wrote:
>
> > Steven is working on a host/guest solution for trace-cmd. It is also
> > asynchronous. No new paravirt hardware is needed and it makes me wonder
> > whether the hy
On Thu, 18 Aug 2016 09:37:11 -0400
Luiz Capitulino wrote:
> On Thu, 18 Aug 2016 11:54:24 +0100
> Stefan Hajnoczi wrote:
>
> > On Fri, Aug 05, 2016 at 06:59:23PM +0200, Lluís Vilanova wrote:
> > > The hypertrace channel allows guest code to emit events in QEMU (the
> > > host) using
> > > its t
On Thu, 18 Aug 2016 11:54:24 +0100
Stefan Hajnoczi wrote:
> Steven is working on a host/guest solution for trace-cmd. It is also
> asynchronous. No new paravirt hardware is needed and it makes me wonder
> whether the hypertrace PCI device is trying to solve the problem at the
> wrong layer.
Ye
On Thu, 18 Aug 2016 14:53:27 +0100
Stefan Hajnoczi wrote:
> On Thu, Aug 18, 2016 at 12:22:18PM +0200, Lluís Vilanova wrote:
> > Stefan Hajnoczi writes:
> >
> > > On Fri, Aug 05, 2016 at 06:59:23PM +0200, Lluís Vilanova wrote:
> > >> The hypertrace channel allows guest code to emit events in
On Thu, Aug 18, 2016 at 12:22:18PM +0200, Lluís Vilanova wrote:
> Stefan Hajnoczi writes:
>
> > On Fri, Aug 05, 2016 at 06:59:23PM +0200, Lluís Vilanova wrote:
> >> The hypertrace channel allows guest code to emit events in QEMU (the host)
> >> using
> >> its tracing infrastructure (see "docs/tra
On Thu, 18 Aug 2016 11:54:24 +0100
Stefan Hajnoczi wrote:
> On Fri, Aug 05, 2016 at 06:59:23PM +0200, Lluís Vilanova wrote:
> > The hypertrace channel allows guest code to emit events in QEMU (the host)
> > using
> > its tracing infrastructure (see "docs/trace.txt"). This works in both
> > 'sys
On Fri, Aug 05, 2016 at 06:59:23PM +0200, Lluís Vilanova wrote:
> The hypertrace channel allows guest code to emit events in QEMU (the host)
> using
> its tracing infrastructure (see "docs/trace.txt"). This works in both 'system'
> and 'user' modes. That is, hypertrace is to tracing, what hypercal
Stefan Hajnoczi writes:
> On Fri, Aug 05, 2016 at 06:59:23PM +0200, Lluís Vilanova wrote:
>> The hypertrace channel allows guest code to emit events in QEMU (the host)
>> using
>> its tracing infrastructure (see "docs/trace.txt"). This works in both
>> 'system'
>> and 'user' modes. That is, hype
On Fri, Aug 05, 2016 at 06:59:23PM +0200, Lluís Vilanova wrote:
> The hypertrace channel allows guest code to emit events in QEMU (the host)
> using
> its tracing infrastructure (see "docs/trace.txt"). This works in both 'system'
> and 'user' modes. That is, hypertrace is to tracing, what hypercal
26 matches
Mail list logo
