From: Jes Sorensen <jes@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Allocating uncacheable memory from OS
Date: Wed, 18 May 2005 08:15:03 +0000 [thread overview]
Message-ID: <yq04qd1rlvc.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <11503.1116315459@kao2.melbourne.sgi.com>
>>>>> "David" = David Mosberger <davidm@napali.hpl.hp.com> writes:
>>>>> On Tue, 17 May 2005 17:37:39 +1000, Keith Owens <kaos@sgi.com> said:
Keith> Is there any ia64 OS routine for allocating uncacheable memory?
Keith> I am trying to simulate the SAL/OS interface for MCA handling
Keith> and the min-state area is expected to be uncacheable.
David> Jes Sorensen was/has been working on such a thing.
Yep,
I have something in the works, it used to be part of the mspec driver
but I am in the process of pulling it out and making it a seperate
entity.
Currently the thing operates at page size entries only, is that
sufficient for you Keith?
Cheers,
Jes
next prev parent reply other threads:[~2005-05-18 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 7:37 Allocating uncacheable memory from OS Keith Owens
2005-05-17 8:01 ` David Mosberger
2005-05-18 8:15 ` Jes Sorensen [this message]
2005-05-18 10:25 ` Keith Owens
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=yq04qd1rlvc.fsf@jaguar.mkp.net \
--to=jes@wildopensource.com \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox