Subject: Re: [RFC PATCH] Exporting extra tables for machines without /dev/mem
To: Graeme Gregory <graeme.gregory@linaro.org>, rjw@rjwysocki.net,
        lenb@kernel.org, linux-acpi@vger.kernel.org
References: <1437485468-17107-1-git-send-email-graeme.gregory@linaro.org>
Cc: linux-kernel@vger.kernel.org
From: Al Stone <ahs3@redhat.com>
Message-ID: <55C27122.8040604@redhat.com>
Date: Wed, 5 Aug 2015 14:25:06 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <1437485468-17107-1-git-send-email-graeme.gregory@linaro.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1372
Lines: 34

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@redhat.com
-----------------------------------
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/