On Sat, Sep 3, 2011 at 9:26 AM, Dhaval Giani wrote:
> On Sat, Sep 3, 2011 at 1:53 AM, Blue Swirl wrote:
>> On Wed, Aug 31, 2011 at 6:00 PM, Dhaval Giani wrote:
>>> On Wed, Aug 31, 2011 at 10:58 AM, Blue Swirl wrote:
On Wed, Aug 31, 2011 at 8:38 AM, Avi Kivity wrote:
> On 08/26/2011 10
On Sat, Sep 3, 2011 at 1:53 AM, Blue Swirl wrote:
> On Wed, Aug 31, 2011 at 6:00 PM, Dhaval Giani wrote:
>> On Wed, Aug 31, 2011 at 10:58 AM, Blue Swirl wrote:
>>> On Wed, Aug 31, 2011 at 8:38 AM, Avi Kivity wrote:
On 08/26/2011 10:06 PM, Blue Swirl wrote:
>
> Let guests inject tra
On Wed, Aug 31, 2011 at 6:00 PM, Dhaval Giani wrote:
> On Wed, Aug 31, 2011 at 10:58 AM, Blue Swirl wrote:
>> On Wed, Aug 31, 2011 at 8:38 AM, Avi Kivity wrote:
>>> On 08/26/2011 10:06 PM, Blue Swirl wrote:
Let guests inject tracepoint data via fw_cfg device.
>>>
>>> At least
On Wed, Aug 31, 2011 at 6:38 AM, Stefan Hajnoczi wrote:
> On Wed, Aug 31, 2011 at 10:11 AM, Avi Kivity wrote:
>> On 08/31/2011 12:08 PM, Stefan Hajnoczi wrote:
>>>
>>> >
>>> > At least on x86, fw_cfg is pretty slow, involving multiple exits.
>>> > IMO, for kvm, even one exit per tracepoint is t
On Wed, Aug 31, 2011 at 10:58 AM, Blue Swirl wrote:
> On Wed, Aug 31, 2011 at 8:38 AM, Avi Kivity wrote:
>> On 08/26/2011 10:06 PM, Blue Swirl wrote:
>>>
>>> Let guests inject tracepoint data via fw_cfg device.
>>>
>>>
>>
>> At least on x86, fw_cfg is pretty slow, involving multiple exits. IMO,
On Wed, Aug 31, 2011 at 8:38 AM, Avi Kivity wrote:
> On 08/26/2011 10:06 PM, Blue Swirl wrote:
>>
>> Let guests inject tracepoint data via fw_cfg device.
>>
>>
>
> At least on x86, fw_cfg is pretty slow, involving multiple exits. IMO, for
> kvm, even one exit per tracepoint is too high. We need
On Wed, Aug 31, 2011 at 10:11 AM, Avi Kivity wrote:
> On 08/31/2011 12:08 PM, Stefan Hajnoczi wrote:
>>
>> >
>> > At least on x86, fw_cfg is pretty slow, involving multiple exits.
>> > IMO, for kvm, even one exit per tracepoint is too high. We need to
>> > use a shared memory transport with a
On 2011-08-31 11:08, Stefan Hajnoczi wrote:
> On Wed, Aug 31, 2011 at 11:38:50AM +0300, Avi Kivity wrote:
>> On 08/26/2011 10:06 PM, Blue Swirl wrote:
>>> Let guests inject tracepoint data via fw_cfg device.
>>>
>>>
>>
>> At least on x86, fw_cfg is pretty slow, involving multiple exits.
>> IMO, for
On 08/31/2011 12:08 PM, Stefan Hajnoczi wrote:
>
> At least on x86, fw_cfg is pretty slow, involving multiple exits.
> IMO, for kvm, even one exit per tracepoint is too high. We need to
> use a shared memory transport with a way to order guest/host events
> later on (by using a clock).
It d
On Wed, Aug 31, 2011 at 11:38:50AM +0300, Avi Kivity wrote:
> On 08/26/2011 10:06 PM, Blue Swirl wrote:
> >Let guests inject tracepoint data via fw_cfg device.
> >
> >
>
> At least on x86, fw_cfg is pretty slow, involving multiple exits.
> IMO, for kvm, even one exit per tracepoint is too high. W
On 08/26/2011 10:06 PM, Blue Swirl wrote:
Let guests inject tracepoint data via fw_cfg device.
At least on x86, fw_cfg is pretty slow, involving multiple exits. IMO,
for kvm, even one exit per tracepoint is too high. We need to use a
shared memory transport with a way to order guest/host
On Tue, Aug 30, 2011 at 7:43 PM, Blue Swirl wrote:
> On Mon, Aug 29, 2011 at 12:17 PM, Stefan Hajnoczi wrote:
>> On Fri, Aug 26, 2011 at 8:06 PM, Blue Swirl wrote:
>>> Let guests inject tracepoint data via fw_cfg device.
>>>
>>> Signed-off-by: Blue Swirl
>>> ---
>>> The patch is used like this:
On Mon, Aug 29, 2011 at 12:51 PM, Lluís wrote:
> Stefan Hajnoczi writes:
>
>> The ability to trace from the guest can be handy, so I think we should
>> have this feature. Please add documentation on how to hook it up
>> (e.g. how people would use this for other firmware/guest code and/or
>> other
On Mon, Aug 29, 2011 at 12:17 PM, Stefan Hajnoczi wrote:
> On Fri, Aug 26, 2011 at 8:06 PM, Blue Swirl wrote:
>> Let guests inject tracepoint data via fw_cfg device.
>>
>> Signed-off-by: Blue Swirl
>> ---
>> The patch is used like this:
>> ../configure --with-guest-trace-file=/src/openbios-devel
Stefan Hajnoczi writes:
> The ability to trace from the guest can be handy, so I think we should
> have this feature. Please add documentation on how to hook it up
> (e.g. how people would use this for other firmware/guest code and/or
> other architectures).
> Guest and QEMU need to agree on eve
On Fri, Aug 26, 2011 at 8:06 PM, Blue Swirl wrote:
> Let guests inject tracepoint data via fw_cfg device.
>
> Signed-off-by: Blue Swirl
> ---
> The patch is used like this:
> ../configure --with-guest-trace-file=/src/openbios-devel/trace-events
> make
> sparc64-softmmu/qemu-system-sparc64 -trace
16 matches
Mail list logo
