All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Vivek Goyal <vgoyal@redhat.com>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: Dave Young <dyoung@redhat.com>,
	Kexec Mailing List <kexec@lists.infradead.org>,
	WANG Chao <chaowang@redhat.com>, Baoquan He <bhe@redhat.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: /proc/vmcore mmap() failure issue
Date: Wed, 13 Nov 2013 13:14:53 -0800	[thread overview]
Message-ID: <5283EBCD.6070305@zytor.com> (raw)
In-Reply-To: <20131113210432.GE7613@redhat.com>

On 11/13/2013 01:04 PM, Vivek Goyal wrote:
> [CC hpa ]
> 
> And this issue brings me to the question that why do we allow sytem RAM
> ranges which do not start on page boundary or do not end on page boundary. 
> Can't we truncate the BIOS reported RAM ranges in such a way so that
> they start and end at PAGE boundary and rest of the kernel will never see
> unaligned portion of RAM and this will make life so much simpler for
> other tools.
> 

That is a bit of a headache for doing in the memblock space.  We do, in
fact, truncate partial pages, but later in the game.  It is possible we
should push that sooner in the stack.  The fact that it makes into the
rbtrees is fishy, but it also makes me wonder if we're doing something
totally stupid with regards to the memory mappings -- if this means
we're mapping ACPI data as noncacheable, that is not just a performance
problem but just plain wrong.  I don't even think the MTRRs can
represent different caching attributes for different parts of a page, so
this is something that we are doing.

	-hpa



_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Vivek Goyal <vgoyal@redhat.com>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: Kexec Mailing List <kexec@lists.infradead.org>,
	Baoquan He <bhe@redhat.com>, WANG Chao <chaowang@redhat.com>,
	Dave Young <dyoung@redhat.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: /proc/vmcore mmap() failure issue
Date: Wed, 13 Nov 2013 13:14:53 -0800	[thread overview]
Message-ID: <5283EBCD.6070305@zytor.com> (raw)
In-Reply-To: <20131113210432.GE7613@redhat.com>

On 11/13/2013 01:04 PM, Vivek Goyal wrote:
> [CC hpa ]
> 
> And this issue brings me to the question that why do we allow sytem RAM
> ranges which do not start on page boundary or do not end on page boundary. 
> Can't we truncate the BIOS reported RAM ranges in such a way so that
> they start and end at PAGE boundary and rest of the kernel will never see
> unaligned portion of RAM and this will make life so much simpler for
> other tools.
> 

That is a bit of a headache for doing in the memblock space.  We do, in
fact, truncate partial pages, but later in the game.  It is possible we
should push that sooner in the stack.  The fact that it makes into the
rbtrees is fishy, but it also makes me wonder if we're doing something
totally stupid with regards to the memory mappings -- if this means
we're mapping ACPI data as noncacheable, that is not just a performance
problem but just plain wrong.  I don't even think the MTRRs can
represent different caching attributes for different parts of a page, so
this is something that we are doing.

	-hpa



  reply	other threads:[~2013-11-13 21:15 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 20:41 /proc/vmcore mmap() failure issue Vivek Goyal
2013-11-13 20:41 ` Vivek Goyal
2013-11-13 21:04 ` Vivek Goyal
2013-11-13 21:04   ` Vivek Goyal
2013-11-13 21:14   ` H. Peter Anvin [this message]
2013-11-13 21:14     ` H. Peter Anvin
2013-11-13 22:41     ` Vivek Goyal
2013-11-13 22:41       ` Vivek Goyal
2013-11-13 22:44       ` H. Peter Anvin
2013-11-13 22:44         ` H. Peter Anvin
2013-11-13 23:00         ` Vivek Goyal
2013-11-13 23:00           ` Vivek Goyal
2013-11-13 23:08           ` H. Peter Anvin
2013-11-13 23:08             ` H. Peter Anvin
2013-11-14 10:31 ` HATAYAMA Daisuke
2013-11-14 10:31   ` HATAYAMA Daisuke
2013-11-14 15:13   ` Vivek Goyal
2013-11-14 15:13     ` Vivek Goyal
2013-11-15  9:41     ` HATAYAMA Daisuke
2013-11-15  9:41       ` HATAYAMA Daisuke
2013-11-15 14:26       ` Vivek Goyal
2013-11-15 14:26         ` Vivek Goyal
2013-11-18  0:51         ` Atsushi Kumagai
2013-11-18  0:51           ` Atsushi Kumagai
2013-11-18 13:55           ` Vivek Goyal
2013-11-18 13:55             ` Vivek Goyal
2013-11-20  5:29             ` Atsushi Kumagai
2013-11-20  5:29               ` Atsushi Kumagai
2013-11-20 14:59               ` Vivek Goyal
2013-11-20 14:59                 ` Vivek Goyal
2013-11-21  5:00                 ` Atsushi Kumagai
2013-11-21  5:00                   ` Atsushi Kumagai
2013-11-21  8:31                   ` HATAYAMA Daisuke
2013-11-21  8:31                     ` HATAYAMA Daisuke
2013-11-21 16:52                     ` Vivek Goyal
2013-11-21 16:52                       ` Vivek Goyal
2013-11-25  8:10                       ` Atsushi Kumagai
2013-11-25  8:10                         ` Atsushi Kumagai
2013-11-25  9:01                         ` HATAYAMA Daisuke
2013-11-25  9:01                           ` HATAYAMA Daisuke
2013-11-25 14:41                           ` Vivek Goyal
2013-11-25 14:41                             ` Vivek Goyal
2013-11-26  1:51                             ` Atsushi Kumagai
2013-11-26  1:51                               ` Atsushi Kumagai
2013-11-26  5:16                             ` HATAYAMA Daisuke
2013-11-26  5:16                               ` HATAYAMA Daisuke
2013-11-19  9:55           ` HATAYAMA Daisuke
2013-11-19  9:55             ` HATAYAMA Daisuke
2013-11-20  5:27             ` Atsushi Kumagai
2013-11-20  5:27               ` Atsushi Kumagai
2013-11-20  6:43               ` HATAYAMA Daisuke
2013-11-20  6:43                 ` HATAYAMA Daisuke
2013-11-26  1:52                 ` Atsushi Kumagai
2013-11-26  1:52                   ` Atsushi Kumagai
2013-11-21  7:14               ` chaowang
2013-11-21  7:14                 ` chaowang
2013-11-25  8:09                 ` Atsushi Kumagai
2013-11-25  8:09                   ` Atsushi Kumagai
2013-11-26  3:29                   ` chaowang
2013-11-26  3:29                     ` chaowang

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=5283EBCD.6070305@zytor.com \
    --to=hpa@zytor.com \
    --cc=bhe@redhat.com \
    --cc=chaowang@redhat.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.