From: Simon Jeons <simon.jeons@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Frantisek Hrbata <fhrbata@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
oleg@redhat.com, kamaleshb@in.ibm.com
Subject: Re: [PATCH] x86: add phys addr validity check for /dev/mem mmap
Date: Thu, 11 Apr 2013 10:40:29 +0800 [thread overview]
Message-ID: <5166229D.2090904@gmail.com> (raw)
In-Reply-To: <515CD3BF.5010104@zytor.com>
Hi H.Peter,
On 04/04/2013 09:13 AM, H. Peter Anvin wrote:
> On 04/03/2013 06:11 PM, Simon Jeons wrote:
>> Why we consider boot_cpu_data.x86_phys_bits instead of e820 map here?
>>
> Because x86_phys_bits is what controls how much address space the
> processor has. e820 tells us how much *RAM* the machine has, or
> specifically, how much RAM the machine had on boot.
I have 8GB memory in my machine, but when I accumulated every e820
ranges which dump in dmesg, there are 25MB memory less then 8GB(1024*8)
memory, why 25MB miss?
>
> -hpa
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-04-11 2:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 12:28 [PATCH] x86: add phys addr validity check for /dev/mem mmap Frantisek Hrbata
2013-04-02 18:02 ` Oleg Nesterov
2013-04-02 18:48 ` H. Peter Anvin
2013-04-02 19:10 ` Frantisek Hrbata
2013-04-02 20:29 ` H. Peter Anvin
2013-04-02 20:52 ` Frantisek Hrbata
2013-04-24 11:36 ` Frantisek Hrbata
2013-04-04 1:11 ` Simon Jeons
2013-04-04 1:13 ` H. Peter Anvin
2013-04-04 1:17 ` Simon Jeons
2013-04-04 1:32 ` H. Peter Anvin
2013-04-04 1:53 ` Simon Jeons
2013-04-04 2:14 ` H. Peter Anvin
2013-04-04 2:17 ` Simon Jeons
2013-04-04 5:20 ` Simon Jeons
2013-04-11 2:40 ` Simon Jeons [this message]
2013-04-11 2:48 ` H. Peter Anvin
2013-04-11 2:58 ` Simon Jeons
2013-04-03 2:46 ` Cheng Jie He
2013-04-26 5:21 ` Will Huck
2013-04-26 15:35 ` Frantisek Hrbata
2013-04-27 7:00 ` Will Huck
2013-04-27 19:13 ` Frantisek Hrbata
2013-04-28 3:17 ` Will Huck
2013-04-28 4:00 ` H. Peter Anvin
2013-04-28 8:03 ` Will Huck
2013-05-01 18:19 ` Dave Hansen
2013-05-01 19:04 ` Frantisek Hrbata
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=5166229D.2090904@gmail.com \
--to=simon.jeons@gmail.com \
--cc=fhrbata@redhat.com \
--cc=hpa@zytor.com \
--cc=kamaleshb@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).