Linux EDAC development
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Borislav Petkov <bp@alien8.de>,
	qiuxu.zhuo@intel.com, aris@redhat.com, mchehab@s-opensource.com,
	"open list:EDAC-CORE" <linux-edac@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: [1/3] ACPI / adxl: Address translation interface using ACPI DSM
Date: Wed, 10 Oct 2018 14:25:53 -0700	[thread overview]
Message-ID: <20181010212552.GA7432@agluck-desk> (raw)

On Wed, Oct 10, 2018 at 11:08:37PM +0200, Rafael J. Wysocki wrote:
> > +config ACPI_ADXL
> > +       bool "Physical address to DIMM address translation"
> > +       def_bool n
> > +       help
> > +         Enable interface that calls into BIOS using a DSM (device
> > +         specific method) to convert system physical addresses
> > +         to DIMM (socket, channel, rank, dimm, etc.).
> > +         Only available on some servers.
> > +         Used by newer EDAC drivers.
> 
> I'm still not sure why this has to be a user-selectable option.  If
> the plan is to select it from the drivers that need it, why do we need
> to ask about it?  And what if it is enabled, but no drivers use it?
> Will it just be dead code then?

Ah, now I see what you mean.  I should make this:

config ACPI_ADXL
        def_bool n

right? So the user isn't plagued by a question they don't understand.
It will only be set if some other driver that need it selects it. So
no way to include dead code.

> > +       obj = acpi_evaluate_dsm_typed(handle, &adxl_guid, ADXL_REVISION,
> > +                                     cmd, argv, ACPI_TYPE_PACKAGE);
> > +       if (!obj) {
> > +               pr_info("Empty obj\n");
> 
> pr_debug() perhaps?  It is somewhat devoid of details anyway.

I'll make the message more meaningful. I think I want to keep it
at higher than "debug" threshold so that we can diagnose problems
from the first report, without having to ask for a rerun with a
new "dmesg" level.

Realistically this should never happen. If it does, its likely
a BIOS bug.

Thanks for the review.

-Tony

             reply	other threads:[~2018-10-10 21:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-10 21:25 Luck, Tony [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-10 21:43 [1/3] ACPI / adxl: Address translation interface using ACPI DSM Rafael J. Wysocki
2018-10-10 21:08 Rafael J. Wysocki
2018-10-09 18:33 Luck, Tony

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=20181010212552.GA7432@agluck-desk \
    --to=tony.luck@intel.com \
    --cc=aris@redhat.com \
    --cc=bp@alien8.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=mchehab@s-opensource.com \
    --cc=qiuxu.zhuo@intel.com \
    --cc=rafael@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox