qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] GSoC mentor summit QEMU users session


From: Fabien Chouteau
Subject: Re: [Qemu-devel] GSoC mentor summit QEMU users session
Date: Fri, 04 Nov 2011 10:53:28 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.23) Gecko/20110922 Lightning/1.0b2 Mnenhy/0.8.4 Thunderbird/3.1.15

On 04/11/2011 09:36, Stefan Hajnoczi wrote:
> On Thu, Nov 03, 2011 at 10:35:28AM +0100, Fabien Chouteau wrote:
>> On 03/11/2011 08:44, Stefan Hajnoczi wrote:
>>> On Wed, Nov 2, 2011 at 5:39 PM, Fabien Chouteau <address@hidden> wrote:
>>>> On 29/10/2011 15:52, Alexander Graf wrote:
>>> I took a quick peak at the qemu-trace.[ch] from couverture and it
>>> looks along the lines of the instrumentation that others have been
>>> doing too.  I hope you have time to propose the coverage
>>> instrumentation for upstream QEMU.
>>>
>>
>> I don't know much about other instrumentations in Qemu (pointers are
>> welcome :), but what we have in couverture-qemu is not trivial,
>> especially when it comes to MC/DC analysis. You should take a look at
>> 201005-erts2.pdf if you want technical details.
> 
> My impression was that the QEMU portion of instrumentation was fairly
> simple - it writes out trace records at various interesting points
> during guest execution in TCG.

It's not rocket science but for MC/DC you have to log history of
branches (taken or not), but if you record everything the output will
unreasonably grow.

>
> I think fancy analysis scripts do not have to be part of QEMU but they
> could be added to scripts/ or put in a new contrib/ directory.

What script are you talking about? GNATcoverage is far more complex than
a fancy script :)

> 
> On the train, can't access the PDF you mentioned right now.

Can't you checkout the repository?

-- 
Fabien Chouteau



reply via email to

[Prev in Thread] Current Thread [Next in Thread]