linux-kernel - Re: [RFC PATCH] Exporting extra tables for machines without /dev/mem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 5 Aug 2015 14:25:06 -0600
From:	Al Stone <ahs3@...hat.com>
To:	Graeme Gregory <graeme.gregory@...aro.org>, rjw@...ysocki.net,
	lenb@...nel.org, linux-acpi@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] Exporting extra tables for machines without /dev/mem

On 07/21/2015 07:31 AM, Graeme Gregory wrote:
> Hi,
> 
> I thought I would send this patch as an RFC. It is something I did when
> another linaro engineer was modifying acpica-tools to not require /dev/mem.
> 
> It exports the 3 tables that are not currenly exported in sysfs.
> 
> Currently I do not think there is any user of this because acpica-tools can
> can recover the information in the other tables without these three being
> exported, fwts also works fine without the patch so the only use case I have
> is the vague "might be useful for debug"

Right -- and I personally would like to have that debug use case.  AFAICT,
the RSDP and RSDT/XSDT are recreated by acpidump; i.e., based on knowledge
of the mapped tables, acpidump builds what it believes these tables should
look like.  But, the /dev/mem mappings would give me what ACPI is actually
using (what was directly passed to the kernel).  Should there be a bug in
table mapping or ACPI startup, this info might help.

-- 
ciao,
al
-----------------------------------
Al Stone
Software Engineer
Red Hat, Inc.
ahs3@...hat.com
-----------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/