From: Andi Kleen <andi at firstfloor.org>
To: devel@acpica.org
Subject: Re: [Devel] acpi_os_read_memory() from interrupt context
Date: Wed, 11 Aug 2010 11:25:25 +0200 [thread overview]
Message-ID: <87y6cd7b7e.fsf@basil.nowhere.org> (raw)
In-Reply-To: 201008041119.23633.bjorn.helgaas@hp.com
[-- Attachment #1: Type: text/plain, Size: 286 bytes --]
Bjorn Helgaas <bjorn.helgaas(a)hp.com> writes:
> require some redesign in the CA.
>
> Any suggestions?
pre-map. Ying developed a pre map infrastructure for this for the ERST
code. You could probably reuse that.
-Andi
--
ak(a)linux.intel.com -- Speaking for myself only.
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-acpi@vger.kernel.org, devel@acpica.org, ying.huang@intel.com
Subject: Re: acpi_os_read_memory() from interrupt context
Date: Wed, 11 Aug 2010 11:25:25 +0200 [thread overview]
Message-ID: <87y6cd7b7e.fsf@basil.nowhere.org> (raw)
In-Reply-To: <201008041119.23633.bjorn.helgaas@hp.com> (Bjorn Helgaas's message of "Wed, 4 Aug 2010 11:19:23 -0600")
Bjorn Helgaas <bjorn.helgaas@hp.com> writes:
> require some redesign in the CA.
>
> Any suggestions?
pre-map. Ying developed a pre map infrastructure for this for the ERST
code. You could probably reuse that.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next reply other threads:[~2010-08-11 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 9:25 Andi Kleen [this message]
2010-08-11 9:25 ` acpi_os_read_memory() from interrupt context Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2010-08-04 22:26 [Devel] " Moore, Robert
2010-08-04 22:26 ` Moore, Robert
2010-08-04 17:19 Bjorn Helgaas
2010-08-04 17:19 ` Bjorn Helgaas
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=87y6cd7b7e.fsf@basil.nowhere.org \
--to=devel@acpica.org \
/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.