[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87tvxzvvf8.fsf@concordia.ellerman.id.au>
Date: Mon, 13 Nov 2017 12:06:51 +1100
From: Michael Ellerman <mpe@...erman.id.au>
To: Frank Rowand <frowand.list@...il.com>, "Tobin C. Harding" <me@...in.cc>, kernel-hardening@...ts.openwall.com
Cc: "Jason A. Donenfeld" <Jason@...c4.com>, Theodore Ts'o <tytso@....edu>, Linus Torvalds <torvalds@...ux-foundation.org>, Kees Cook <keescook@...omium.org>, Paolo Bonzini <pbonzini@...hat.com>, Tycho Andersen <tycho@...ker.com>, "Roberts\, William C" <william.c.roberts@...el.com>, Tejun Heo <tj@...nel.org>, Jordan Glover <Golden_Miller83@...tonmail.ch>, Greg KH <gregkh@...uxfoundation.org>, Petr Mladek <pmladek@...e.com>, Joe Perches <joe@...ches.com>, Ian Campbell <ijc@...lion.org.uk>, Sergey Senozhatsky <sergey.senozhatsky@...il.com>, Catalin Marinas <catalin.marinas@....com>, Will Deacon <wilal.deacon@....com>, Steven Rostedt <rostedt@...dmis.org>, Chris Fries <cfries@...gle.com>, Dave Weinstein <olorin@...gle.com>, Daniel Micay <danielmicay@...il.com>, Djalal Harouni <tixxdz@...il.com>, linux-kernel@...r.kernel.org, Network Development <netdev@...r.kernel.org>, David Miller <davem@...emloft.net>
Subject: Re: [PATCH v4] scripts: add leaking_addresses.pl
Frank Rowand <frowand.list@...il.com> writes:
> Hi Michael,
>
> On 11/12/17 03:49, Michael Ellerman wrote:
...
>>
>> On our bare metal machines the device tree comes from skiboot
>> (firmware), with some of the content provided by hostboot (other
>> firmware), both of which are open source, so in theory most of the
>> information is available in *some* source tree. But there's still
>> information about runtime allocations etc. that is not available in the
>> source anywhere.
>
> Thanks for the additional information.
>
> Can you explain a little bit what "runtime allocations" are? Are you
> referring to the memory reservation block, the memory node(s) and the
> chosen node? Or other information?
Yeah I was thinking of memory reservations. They're under the
reserved-memory node as well as the reservation block, eg:
$ ls -1 /proc/device-tree/reserved-memory/
ibm,firmware-allocs-memory@...0000000
ibm,firmware-allocs-memory@...0000000
ibm,firmware-allocs-memory@...00000
ibm,firmware-allocs-memory@...000000
ibm,firmware-code@...00000
ibm,firmware-data@...00000
ibm,firmware-heap@...00000
ibm,firmware-stacks@...00000
ibm,hbrt-code-image@...d510000
ibm,hbrt-target-image@...d6a0000
ibm,hbrt-vpd-image@...d700000
ibm,slw-image@...da00000
ibm,slw-image@...de00000
ibm,slw-image@...e200000
ibm,slw-image@...e600000
There's also some new systems where a catalog of PMU events is stored in
flash as a DTB and then stitched into the device tree by skiboot before
booting Linux.
Anyway my point was mainly just that the device tree is not simply a
copy of something in the kernel source.
cheers
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
