From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] [PATCH] quick_dump: A dump utility different than reg_dumper
Date: Wed, 26 Sep 2012 13:51:01 +0200 [thread overview]
Message-ID: <20120926115101.GC1980@bremse> (raw)
In-Reply-To: <617390e2a10e9c1fd7682455538f9659@bwidawsk.net>
On Sat, Sep 22, 2012 at 01:58:37PM -0700, Ben Widawsky wrote:
> On 2012-09-22 11:05, Daniel Vetter wrote:
> >And a quick comment on your approach here: I'm not too sure
> >whether the
> >file-base register block approach scales, respectively why exactly
> >this is
> >better than frobbing the reg_dumper tool. Since that one has the
> >concept
> >of register blocks already, too.
>
> It doesn't scale. It scales better than reg_dumper was my goal and
> point (IMO).
>
> The exact problem that was trying to be solved is Valleyview (and I
> assure you there will be more such products coming). Valleyview took
> a huge chunk of well known registers, and changed their offsets.
> Modifying this in reg dumper is of course possible, but it's
> tedious. I wanted to have easy to modify text files with an easy
> python front end (the offsets could even be applied in the script
> extremely easily).
If the issue is just the base-address moving around, I think we could
solve that with some refactoring ...
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2012-09-26 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 19:46 [RFC] [PATCH] quick_dump: A dump utility different than reg_dumper Ben Widawsky
2012-09-22 18:05 ` Daniel Vetter
2012-09-22 20:58 ` Ben Widawsky
2012-09-26 11:51 ` Daniel Vetter [this message]
2012-09-26 18:40 ` Ben Widawsky
2012-09-27 11:51 ` Daniel Vetter
2013-01-20 2:03 ` Ben Widawsky
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=20120926115101.GC1980@bremse \
--to=daniel@ffwll.ch \
--cc=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.