lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 22 Oct 2008 09:40:22 -0500
From:	Russ Anderson <rja@....com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	tglx@...utronix.de, linux-kernel@...r.kernel.org,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 2/3] x86: Add UV memory protection bios call

On Wed, Oct 22, 2008 at 08:22:35AM +0200, Ingo Molnar wrote:
> 
> * Russ Anderson <rja@....com> wrote:
> 
> > Add UV bios call to change memory protections.
> > 
> > Signed-off-by: Russ Anderson <rja@....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@....com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ