From: Russ Anderson <rja@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/3] x86: Add UV memory protection bios call
Date: Wed, 22 Oct 2008 09:40:22 -0500 [thread overview]
Message-ID: <20081022144021.GB201004@sgi.com> (raw)
In-Reply-To: <20081022062235.GD651@elte.hu>
On Wed, Oct 22, 2008 at 08:22:35AM +0200, Ingo Molnar wrote:
>
> * Russ Anderson <rja@sgi.com> wrote:
>
> > Add UV bios call to change memory protections.
> >
> > Signed-off-by: Russ Anderson <rja@sgi.com>
> >
> > ---
> > arch/x86/kernel/bios_uv.c | 8 ++++++++
> > include/asm-x86/uv/bios.h | 10 +++++++++-
> > 2 files changed, 17 insertions(+), 1 deletion(-)
>
> > - UV_BIOS_WATCHLIST_FREE
> > + UV_BIOS_WATCHLIST_FREE,
> > + UV_BIOS_MEMPROTECT
>
> > +enum uv_memprotect {
> > + UV_MEMPROT_RESTRICT_ACCESS,
> > + UV_MEMPROT_ALLOW_AMO,
> > + UV_MEMPROT_ALLOW_RW
>
> hm, what does this do? Does it twiddle the southbridge to protect given
> physical RAM rages from the CPU altogether?
The SGI UV hardware has memory protection to control what types of memory
references are allowed to specific physical RAM ranges. This bios call
is used to change the protection settings.
This is used by the xp driver (drivers/misc/sgi-xp/xp_sn2.c).
Dean Nelson submitted a patch yesterday that uses this bios call.
http://marc.info/?l=linux-kernel&m=122462425819289&w=2
Thanks,
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
prev parent reply other threads:[~2008-10-22 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 20:01 [PATCH 2/3] x86: Add UV memory protection bios call Russ Anderson
2008-10-22 6:22 ` Ingo Molnar
2008-10-22 14:40 ` Russ Anderson [this message]
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=20081022144021.GB201004@sgi.com \
--to=rja@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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