From: Erik de Castro Lopo <mle+tools@mega-nerd.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] tracing memory accesses
Date: Tue, 11 Nov 2008 22:10:20 +1100 [thread overview]
Message-ID: <20081111221020.6a57d17f.mle+tools@mega-nerd.com> (raw)
In-Reply-To: <49195809.6010702@uab.cat>
Màrius Montón wrote:
> I've been working for a while adding SystemC capabilities to QEMU
> (in short, SystemC is a C++ extension to describe HW and we are
> using it to add new peripherals to QEMU)
>(http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=4374971)
I'd love to read that article but is seems to be locked behind some
sort of knowledge firewall. Is that article available elsewhere?
Erik
--
-----------------------------------------------------------------
Erik de Castro Lopo
-----------------------------------------------------------------
"Testing can prove the presence of bugs, but never their absence."
-- Edsger Dijkstra
next prev parent reply other threads:[~2008-11-11 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 10:01 [Qemu-devel] tracing memory accesses Màrius Montón
2008-11-11 11:10 ` Erik de Castro Lopo [this message]
2008-11-11 11:21 ` Laurent Desnogues
2008-11-11 11:26 ` Màrius Montón
2008-11-11 18:51 ` Blue Swirl
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=20081111221020.6a57d17f.mle+tools@mega-nerd.com \
--to=mle+tools@mega-nerd.com \
--cc=qemu-devel@nongnu.org \
/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).