From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from terminus.zytor.com ([2001:1868:205::10] helo=mail.zytor.com) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1UQfOw-0005yR-Jm for kexec@lists.infradead.org; Fri, 12 Apr 2013 14:56:31 +0000 Message-ID: <5168208B.7050107@zytor.com> Date: Fri, 12 Apr 2013 07:56:11 -0700 From: "H. Peter Anvin" MIME-Version: 1.0 Subject: Re: [PATCH 5/5] kexec: X86: Pass memory ranges via e820 table instead of memmap= boot parameter References: <1365683207-42425-1-git-send-email-trenn@suse.de> <1365683207-42425-6-git-send-email-trenn@suse.de> <5166D18A.7090800@zytor.com> <20130412143104.GA4301@redhat.com> In-Reply-To: <20130412143104.GA4301@redhat.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "kexec" Errors-To: kexec-bounces+dwmw2=twosheds.infradead.org@lists.infradead.org To: Vivek Goyal Cc: Dave Hansen , "kexec@lists.infradead.org" , Linux Kernel Mailing List , Thomas Renninger , Simon Horman , "Eric W. Biederman" , Yinghai Lu , Cliff Wickman On 04/12/2013 07:31 AM, Vivek Goyal wrote: >> >> I also have to admit that I don't see the difference between /dev/mem >> and /dev/oldmem, as the former allows access to memory ranges outside >> the ones used by the current kernel, which is what the oldmem device >> seems to be intended to od. > > I think one difference seems to be that /dev/mem assumes that validly > accessed memory is already mapped in kernel while /dev/oldmeme assumes > it is not mapped and creates temporary mappings explicitly. > Dave Hansen has been working on fixing /dev/mem for HIGHMEM. -hpa _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec