Aggregated address spaces in libkdumpfile

["Petr Tesařík" <petr@tesarici.cz>]

Hi Alexander,

I'm taking this discussion to the linux-debugging ML, because I think
other people may be interested.

It's about this pull request:

https://github.com/ptesarik/libkdumpfile/pull/77

If my understanding is correct, it is sometimes useful to have a single
address translation which covers both kernel-space and user-space
addresses, but uses a different method to translate each.

For one thing, kernel-space and user-space cannot be distinguished by
address value alone on some architectures (hi there, S/390!), so I
wonder how to deal with the kernel-space/user-space boundary in the
general case.

If there are use cases for aggregating multiple "low-level" address
spaces into a synthetic "high-level" one, then libaddrxlat may provide
a better mechanism. OTOH this could be over-engineering if there is
only one potential use for the feature.

Has anyone else run into a similar need as Alexander?

Petr T