From: Bob Picco <bpicco@meloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH v2 0/8] sparc64: MM/IRQ patch queue.
Date: Mon, 29 Sep 2014 22:35:22 +0000 [thread overview]
Message-ID: <20140929223522.GM4211@zareason> (raw)
In-Reply-To: <20140927.142812.2031647355756795530.davem@davemloft.net>
David Miller wrote: [Mon Sep 29 2014, 05:33:17PM EDT]
> From: Bob Picco <bob.picco@oracle.com>
> Date: Mon, 29 Sep 2014 17:03:22 -0400
>
> > My local T4-2 and T5-2 seem solid for THP "always" and large kernel parallel
> > makes. I've seen no issues.
>
> Ok, how about the T5-8? Does it at least boot properly with
> DEBUG_PAGEALLOC disabled?
>
Sorry family issue on top of work!
It would require time to get on this machine but not required.
This is debug from the T5-8 from a while ago:
From the next line
PERCPU: static=0x5d80 reserved=0x2000 dyn=0x6280 unit=0x10000
PERCPU: atom=0x400000 alloc=0x400000 __ai=0x2000 nr=8
PERCPU: group=0 ptr=0xffff803f5d000000 nid=0 nr_units\x128 cpu=0
PERCPU: group=1 ptr=0xffff883f7f000000 nid=1 nr_units\x128 cpu\x128
PERCPU: group=2 ptr=0xffff903f7f000000 nid=2 nr_units\x128 cpu%6
PERCPU: group=3 ptr=0xffff983f7f000000 nid=3 nr_units\x128 cpu84
PERCPU: group=4 ptr=0xffffa03f7f000000 nid=4 nr_units\x128 cpuQ2
PERCPU: group=5 ptr=0xffffa83f7f000000 nid=5 nr_units\x128 cpud0
PERCPU: group=6 ptr=0xffffb03f7f000000 nid=6 nr_units\x128 cpuv8
PERCPU: group=7 ptr=0xffffb83f5ec00000 nid=7 nr_units\x128 cpu‰6
PERCPU: base=0xffff803f5d000000
to the previous line is from percpu-debug.patch.
PERCPU: max_distance=0x380001c10000 too large for vmalloc space 0xff00000000
. So just subtract 0xffff800000000000UL from "ptr".
This from a SMI/Oracle hardware engineer and also contained within the
T5 hardware specification:
"But on T5 this has changed. Memory on T5 is spread out based on PA[45:43]. So,
that means same situation as above will see physical addresses as :"
.
This is current from my T5-2:
[ 0.000000] MM: PAGE_OFFSET is 0xffff800000000000 (max_phys_bits = 47)
[ 0.000000] MM: VMALLOC [0x0000000100000000 --> 0x0000400000000000]
[ 0.000000] MM: VMEMMAP [0x0000400000000000 --> 0x0000800000000000]
[ 0.000000] Kernel: Using 2 locked TLB entries for main kernel image.
...
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x30400000-0x1fef781fff]
[ 0.000000] node 0: [mem 0x1fef788000-0x1fef789fff]
[ 0.000000] node 1: [mem 0x80000000000-0x81ffff0ffff]
[ 0.000000] node 1: [mem 0x81ffff20000-0x81ffff43fff]
You can see the MCU increases linearly within bits positions PA[45:43] by
node. VMALLOC range is based on VMALLOC_END = (~PAGE_OFFSET + 1) >> 1;.
So it would seem to fail for T5-8. It indeed does for M7-4 but other
issues manifest too.
This is M7-4:
MM: PAGE_OFFSET is 0xfffe000000000000 (max_phys_bits = 49)^M
MM: VMALLOC [0x0000000100000000 --> 0x0001000000000000]^M
MM: VMEMMAP [0x0001000000000000 --> 0x0002000000000000]^M
Kernel: Using 3 locked TLB entries for main kernel image.^M
Remapping the kernel... done.^M
..
Early memory node ranges^M
node 0: [mem 0x50400000-0x3fbf6bdfff]^M
node 0: [mem 0x3fbf6c4000-0x3fbf6c5fff]^M
node 1: [mem 0x400000000000-0x403bffffffff]^M
node 2: [mem 0x800000000000-0x803fffffffff]^M
node 3: [mem 0xc00000000000-0xc03fffd5dfff]^M
node 3: [mem 0xc03fffd90000-0xc03fffdaffff]^M
node 3: [mem 0xc03fffdc0000-0xc03fffdc3fff]^M
Booting Linux...^M
CPU CAPS: [flush,stbar,swap,muldiv,v9,mul32,div32,v8plus]^M
CPU CAPS: [popc,vis,vis2,ASIBlkInit,fmaf,vis3,hpc,ima]^M
CPU CAPS: [pause,cbcond,aes,des,camellia,md5,sha1,sha256]^M
CPU CAPS: [sha512,mpmul,montmul,montsqr,crc32c]^M
PERCPU: max_distance=0xc000c2410000 too large for vmalloc space 0xffff00000000^M
PERCPU: auto allocator failed (-22), falling back to page size^M
PERCPU: 6 8K pages/cpu @0000000100000000 s23552 r8192 d17408^M
Let me look at this in the morning when NOT distracted by family issue.
thanx,
bob
next prev parent reply other threads:[~2014-09-29 22:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 18:28 [PATCH v2 0/8] sparc64: MM/IRQ patch queue David Miller
2014-09-27 20:46 ` Bob Picco
2014-09-28 4:35 ` David Miller
2014-09-29 20:15 ` David Miller
2014-09-29 21:03 ` Bob Picco
2014-09-29 21:33 ` David Miller
2014-09-29 22:35 ` Bob Picco [this message]
2014-09-30 1:52 ` David Miller
2014-09-30 1:56 ` David Miller
2014-09-30 1:57 ` David Miller
2014-09-30 2:16 ` David Miller
2014-09-30 10:36 ` Bob Picco
2014-09-30 13:17 ` Bob Picco
2014-09-30 13:53 ` Bob Picco
2014-09-30 18:55 ` David Miller
2014-09-30 20:58 ` Bob Picco
2014-09-30 22:28 ` Bob Picco
2014-10-01 2:29 ` David Miller
2014-10-01 2:57 ` David Miller
2014-10-01 11:51 ` Bob Picco
2014-10-01 14:29 ` Bob Picco
2014-10-01 20:42 ` David Miller
2014-10-01 20:44 ` David Miller
2014-10-01 21:51 ` Bob Picco
2014-10-02 14:24 ` Bob Picco
2014-10-03 22:53 ` David Miller
2014-10-04 19:12 ` David Miller
2014-10-04 20:00 ` David Miller
2014-10-05 13:51 ` Bob Picco
2014-10-05 13:58 ` Bob Picco
2014-10-13 3:53 ` David Miller
2014-10-15 2:40 ` David Miller
2014-10-16 12:36 ` Bob Picco
2014-10-16 16:12 ` David Miller
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=20140929223522.GM4211@zareason \
--to=bpicco@meloft.net \
--cc=sparclinux@vger.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 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.