MmioTrace: Using the Instruction Decoder, etc.

[Eugene Shatokhin]

Hi,

That's OK.

The first rule of a good software developer is, they say, 'if that works -
don't touch it'. :-)

There are definitely many other things to do.

Thanks for your feedback!

Regards,
Eugene



2013/10/28 Pekka Paalanen <pq at iki.fi>

> On Fri, 25 Oct 2013 17:19:56 +0400
> Eugene Shatokhin <euspectre at gmail.com> wrote:
>
> > Hi,
> >
> > 2013/10/25 Pekka Paalanen <pq at iki.fi>
> >
> ...
> > > We could use some comments from the real reverse-engineers. I used
> > > to be mostly a tool writer.
> > >
> >
> > Yes, if some experts could share their knowledge of this matter, this
> would
> > be most welcome!
>
> Hi,
>
> I got one comment in IRC, saying that a faster mmiotrace would be
> nice, but probably not something he would invest time in.
>
> Looking at it from that point of view, I guess mmiotrace works well enough,
> and is "only" a reverse-engineering tool, not something used daily.
> That, and the lack of replies here indicate that rewriting mmiotrace
> with your approach might not be worth it. I don't think anyone
> opposes to the idea, they just have better things to do.
>
> It's all up to you, I believe.
>
>
> Thanks,
> pq
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20131028/943ff901/attachment-0001.html>