qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabien Chouteau <chouteau@adacore.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Lluís Vilanova" <vilanova@ac.upc.edu>,
	"Alexander Graf" <agraf@suse.de>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] GSoC mentor summit QEMU users session
Date: Fri, 04 Nov 2011 15:36:12 +0100	[thread overview]
Message-ID: <4EB3F85C.6010709@adacore.com> (raw)
In-Reply-To: <CAJSP0QVxcrs0ewJYRKr=UZ5MmpF0frUMSYhkd2vs=UBFvd+yPQ@mail.gmail.com>

On 04/11/2011 13:04, Stefan Hajnoczi wrote:
> On Fri, Nov 4, 2011 at 9:53 AM, Fabien Chouteau <chouteau@adacore.com> wrote:
>> 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 <chouteau@adacore.com> 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 :)
>
> I'm not up to speed on GNATcoverage or couverture, so apologies if I'm
> wrong - please let me know.  Still, I think we're talking about the
> same thing here:
>
> http://www.adacore.com/home/products/gnatpro/add-on_technologies/gnatcoverage/
>
> Looks like GNATemulator is QEMU with additional instrumentation.
> GNATcoverage takes the execution traces that the instrumented QEMU
> produced.  So when I said "fancy analysis scripts", I meant the tool
> that analyzes the trace.
>

In your previous message you seemed to say that GNATcoverage could be
included in Qemu. I just wanted to explain that GNATcoverage is a
project on its own and will not be a part of Qemu.

>>> On the train, can't access the PDF you mentioned right now.
>>
>> Can't you checkout the repository?
>
> Sorry, I was reading/replying to mail offline.  I now grabbed the git
> repo and looked at commit b82469c906829865693b4fad0edb0a069604a8d9,
> which I believe is the main change needed to add couverture tracing to
> QEMU.

Right this is the main commit, there are few others to fix corner cases.

>
> I'm trying to see if you want to send QEMU changes upstream?

As I said it's in our plan, but we don't have time for now. You are
welcome to help if you want to.

-- 
Fabien Chouteau

  reply	other threads:[~2011-11-04 14:36 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29 13:52 [Qemu-devel] GSoC mentor summit QEMU users session Alexander Graf
2011-10-31 13:12 ` Peter Maydell
2011-11-01  0:08   ` Alexander Graf
2011-11-01  1:35     ` Peter Maydell
2011-11-01  4:29       ` Alexander Graf
2011-11-01 10:05   ` Gerd Hoffmann
2011-11-01 23:11     ` Chris Johns
2011-11-02 17:44   ` Fabien Chouteau
2011-11-02 18:17     ` Jan Kiszka
2011-11-02 18:29       ` Anthony Liguori
2011-11-02 18:34         ` Alexander Graf
2011-11-02 18:46           ` Jan Kiszka
2011-11-02 18:47             ` Alexander Graf
2011-11-02 19:07               ` Peter Maydell
2011-11-02 19:27                 ` Alexander Graf
2011-11-02 19:35                   ` Anthony Liguori
2011-11-02 20:24                     ` Blue Swirl
2011-11-02 20:42                       ` Anthony Liguori
2011-11-03  7:34                         ` Markus Armbruster
2011-11-03  7:46                     ` Markus Armbruster
2011-11-03  8:36                       ` Andreas Färber
2011-11-04 15:47                         ` Alexander Graf
2011-11-02 18:50             ` Anthony Liguori
2011-11-02 18:52               ` Jan Kiszka
2011-11-02 18:51           ` Anthony Liguori
2011-11-03  7:38             ` Stefan Hajnoczi
2011-11-03  7:44           ` Markus Armbruster
2011-11-01 14:28 ` Andreas Färber
2011-11-01 14:50   ` Anthony Liguori
2011-11-02 17:39 ` Fabien Chouteau
2011-11-03  7:44   ` Stefan Hajnoczi
2011-11-03  9:35     ` Fabien Chouteau
2011-11-04  8:36       ` Stefan Hajnoczi
2011-11-04  9:53         ` Fabien Chouteau
2011-11-04 12:04           ` Stefan Hajnoczi
2011-11-04 14:36             ` Fabien Chouteau [this message]
2011-11-04 18:45         ` Lluís Vilanova
2011-11-07 10:16           ` Fabien Chouteau
2011-11-07 11:50             ` Lluís Vilanova
2011-11-07 13:51               ` Fabien Chouteau
2011-11-07 14:17                 ` Lluís Vilanova

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=4EB3F85C.6010709@adacore.com \
    --to=chouteau@adacore.com \
    --cc=agraf@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=vilanova@ac.upc.edu \
    /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).