From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
Aristeu Rozanski <aris@redhat.com>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>,
linux-edac@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: [v2,1/3] ACPI / adxl: Address translation interface using ACPI DSM
Date: Fri, 12 Oct 2018 11:03:57 -0700 [thread overview]
Message-ID: <20181012180357.GB5625@agluck-desk> (raw)
On Fri, Oct 12, 2018 at 10:01:11AM +0200, Borislav Petkov wrote:
>
> > Subject: Re: [PATCH v2 1/3] ACPI / adxl: Address translation interface using ...
>
> Commit name needs a verb: "Add address translation..."
>
> On Thu, Oct 11, 2018 at 02:12:34PM -0700, Tony Luck wrote:
> > Some new servers provide an interface so that the OS can ask the
> > BIOS to translate a system physical address to a memory address
> > (socket, memory controller, channel, rank, dimm, etc.). This is
> > useful for EDAC drivers that want to take the address of an error
> > reported in a machine check bank and let the user know which
> > DIMM may need to be replaced.
> >
> > Specification for this interface is available at:
> >
> > https://cdrdv2.intel.com/v1/dl/getContent/603354
>
> What do we do when that link dies?
>
> (And I've seen them die).
>
> Normally we upload those docs in bugzilla.kernel.org but that link wants
> me to "Accept".
I'm still working to get the page out from behind a click
to accept. The interface is pretty simple though. I think
it is now pretty easy to reverse engineer from the code. So
if the link does go away it won't be a disaster.
-Tony
next reply other threads:[~2018-10-12 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 18:03 Luck, Tony [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-10-12 8:01 [v2,1/3] ACPI / adxl: Address translation interface using ACPI DSM Borislav Petkov
2018-10-11 21:12 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=20181012180357.GB5625@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.j.wysocki@intel.com \
/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