diff options
| author | Michel Lespinasse <walken@google.com> | 2014-01-28 17:06:22 +0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-02-15 23:30:28 +0400 |
| commit | cb88759107292b4bf36d13c73129add580d4e26e (patch) | |
| tree | 5dfc70e1d1692a705fc35acb48af63c06c6a9867 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | b12b73f1ca7763a94e0949a0d86eea40b5f69ea6 (diff) | |
| download | linux-cb88759107292b4bf36d13c73129add580d4e26e.tar.xz | |
firmware: google memconsole driver fixes
The google memconsole driver is currently broken upstream, as it tries
to read memory that is described as reserved in /proc/iomem, by
dereferencing a pointer obtained through phys_to_virt(). This triggers
a kernel fault as such regions are unmapped after early boot.
The proper workaround is to use ioremap_cache() / iounmap() around such
accesses.
As some unrelated changes, I also converted some printks to use pr_info()
and added some missing __init annotations.
Tested: booted dbg build, verified I could read /sys/firmware/log
Signed-off-by: Michel Lespinasse <walken@google.com>
Acked-by: Mike Waychison <mikew@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions