On Thu, Oct 01, 2009 at 02:53:11PM -0500, Robert Jennings wrote:
Memory balloon drivers can allocate a large amount of memory which
is not movable but could be freed to accommodate memory hotplug remove.
Prior to calling the memory hotplug notifier chain the memory in the
pageblock is
Just wondering - is there a case where using volatile for UCC parameter RAM for
example will not work, or is the use of I/O accessors everywhere an attempt to
be portable to other architectures?
I'm asking because I really want to know ;)
--
Michael Barkowski
905-482-4577
Michael Barkowski wrote:
Just wondering - is there a case where using volatile for UCC parameter RAM
for example will not work, or is the use of I/O accessors everywhere an
attempt to be portable to other architectures?
'volatile' just doesn't really do what you think it should do. The
On Wed, 2009-09-30 at 07:35 +0100, Jan Beulich wrote:
Hollis Blanchard holl...@us.ibm.com 30.09.09 01:39
On Tue, 2009-09-29 at 10:28 +0100, Jan Beulich wrote:
Hollis Blanchard 09/29/09 2:00 AM
First, I think there is a real bug here, and the code should read like
this (to match the
On Oct 2, 2009, at 9:46 AM, Timur Tabi wrote:
Michael Barkowski wrote:
Just wondering - is there a case where using volatile for UCC
parameter RAM for example will not work, or is the use of I/O
accessors everywhere an attempt to be portable to other
architectures?
'volatile' just
Kumar Gala wrote:
On Oct 2, 2009, at 9:46 AM, Timur Tabi wrote:
Michael Barkowski wrote:
Just wondering - is there a case where using volatile for UCC
parameter RAM for example will not work, or is the use of I/O
accessors everywhere an attempt to be portable to other architectures?
It's seems a RAM initialize problem. Try to use ICE or your bootloader
to test initialized RAM wirh write/read operation.
Ex, use mtest in uboot to check memory. For ICE, it should be an
detailed memory test function like hardware diagnostic.
2009/9/24 Benjamin Herrenschmidt
Benjamin Herrenschmidt b...@kernel.crashing.org wrote on 01/10/2009
00:35:59:
Had a look at linus tree and there is something I don't understand.
Your fix, e0908085fc2391c85b85fb814ae1df377c8e0dcb, fixes a problem
that was introduced by 8d30c14cab30d405a05f2aaceda1e9ad57800f36
Michael Barkowski wrote:
Kumar Gala wrote:
On Oct 2, 2009, at 9:46 AM, Timur Tabi wrote:
Michael Barkowski wrote:
Just wondering - is there a case where using volatile for UCC
parameter RAM for example will not work, or is the use of I/O
accessors everywhere an attempt to be
* Nathan Fontenot (nf...@austin.ibm.com) wrote:
Robert Jennings wrote:
Memory balloon drivers can allocate a large amount of memory which
is not movable but could be freed to accommodate memory hotplug remove.
Prior to calling the memory hotplug notifier chain the memory in the
pageblock is
* Mel Gorman (m...@csn.ul.ie) wrote:
On Thu, Oct 01, 2009 at 02:53:11PM -0500, Robert Jennings wrote:
Memory balloon drivers can allocate a large amount of memory which
is not movable but could be freed to accommodate memory hotplug remove.
Prior to calling the memory hotplug notifier
Memory balloon drivers can allocate a large amount of memory which
is not movable but could be freed to accomodate memory hotplug remove.
Prior to calling the memory hotplug notifier chain the memory in the
pageblock is isolated. If the migrate type is not MIGRATE_MOVABLE the
isolation will not
The Collaborative Memory Manager (CMM) module allocates individual pages
over time that are not migratable. On a long running system this can
severely impact the ability to find enough pages to support a hotplug
memory remove operation.
This patch adds a memory isolation notifier and a memory
Anton Blanchard an...@samba.org writes:
On 64bit applications the VDSO is the only thing in segment 0. Since the VDSO
is position independent we can remove the hint and let get_unmapped_area pick
an area.
This breaks gdb. The section table in the VDSO image when mapped into
the process no
On Thu, Oct 01, 2009 at 08:35:59AM +1000, Benjamin Herrenschmidt wrote:
From what I can see, the TLB miss code will check _PAGE_PRESENT, and
when not set, it will -still- insert something into the TLB (unlike
all other CPU types that go straight to data access faults from there).
So we end
On Fri, 2009-10-02 at 16:49 -0500, Scott Wood wrote:
Adding a tlbil_va to do_page_fault makes the problem go away for me (on
top of your merge branch) -- none of the other changes in this thread
do (assuming I didn't miss any). FWIW, when it gets stuck on a fault,
DSISR is 0xc000, and
16 matches
Mail list logo
