All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Stone <ahs3@redhat.com>
To: Graeme Gregory <graeme.gregory@linaro.org>,
	rjw@rjwysocki.net, lenb@kernel.org, linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] Exporting extra tables for machines without /dev/mem
Date: Wed, 5 Aug 2015 14:25:06 -0600	[thread overview]
Message-ID: <55C27122.8040604@redhat.com> (raw)
In-Reply-To: <1437485468-17107-1-git-send-email-graeme.gregory@linaro.org>

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
-----------------------------------

  parent reply	other threads:[~2015-08-05 20:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21 13:31 [RFC PATCH] Exporting extra tables for machines without /dev/mem Graeme Gregory
2015-07-21 13:31 ` [RFC PATCH] ACPI: sysfs expose root tables RSDP/RSDT/XSDT Graeme Gregory
2015-08-05 20:25 ` Al Stone [this message]
2015-08-05 23:38   ` [RFC PATCH] Exporting extra tables for machines without /dev/mem Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55C27122.8040604@redhat.com \
    --to=ahs3@redhat.com \
    --cc=graeme.gregory@linaro.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.