On Sat, Oct 12, 2002 at 08:24:05PM +0000, Philippe Elie wrote:
> IMHO you would prioritize test suite and op_export, publying
> an abi for the interface between dae/module/pp tools is
> usefull but also look like a promise we remain compatible with
> this abi in future, we probably can do this in future but oprofile
> is an alpha version for now. Impact of db performance is greater
> in 2.5 oprofile (cause we no longer have a hash table in module).
> The abi is likely to be broken if we want to improve db
I've been thinking too. What I think would be best is to have an
op_export that can export a platform-specific sample file into something
that can be debugged on another system. Basically we build an op_export
on the source machine, therefore it "instinctively" understands the
binary format. And it can then export to a platform-agnostic format
(which could have the ABI header stuff, or hdf5, or whatever)
No complication on the 99% path of using the same machine
No performance concerns
Flexibility of changes in platform-specific and op_export code
Possibility of op_export bugs interfering with the debug effort
Graydon, what do you think ? Sorry I didn't object too much earlier, but
I really think this would be the preferable approach.
"That's just kitten-eating wrong."
- Richard Henderson