linux-kernel - Re: [PATCH 2.6.19-rc6-git2] EFI: mapping memory region of runtime services when using memmap kernel parameter

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]

Message-ID: <456327B4.6000904@oracle.com>
Date:	Tue, 21 Nov 2006 08:22:12 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	"Myaskouvskey, Artiom" <artiom.myaskouvskey@...el.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2.6.19-rc6-git2] EFI: mapping memory region of runtime
 services when using memmap kernel parameter

Myaskouvskey, Artiom wrote:
> From: Artiom Myaskouvskey <artiom.myaskouvskey@...el.com>
> 
> When using memmap kernel parameter in EFI boot we should also add to memory map 
> memory regions of runtime services to enable their mapping later.
> 
> Signed-off-by: Artiom Myaskouvskey <artiom.myaskouvskey@...el.com>
> ---

Thanks, I can actually apply the patch now, as opposed to the apparently
base64-encoded version that was just junk to me.

Of course, we can't review it easily when it's an attachment.
It would be a Good Thing for you to experiment with some email clients
that can send patches inline (not as attachments, not as base64) and
which do not mangle the whitespace and do not encode the text.

Back to the patch:  it's only for i386.  Does x86_64 need
similar treatment?

-- 
~Randy
-
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/