From: Mikulas Patocka <mpatocka@redhat.com>
To: John David Anglin <dave.anglin@bell.net>
Cc: Helge Deller <deller@gmx.de>, linux-parisc@vger.kernel.org
Subject: Re: [PATCH][RFC] parisc: Use per-pagetable spinlock (v2)
Date: Thu, 2 May 2019 09:43:25 -0400 (EDT) [thread overview]
Message-ID: <alpine.LRH.2.02.1905020920560.18084@file01.intranet.prod.int.rdu2.redhat.com> (raw)
In-Reply-To: <7dfcef75-193f-6373-92f3-f448c59bba63@bell.net>
On Wed, 1 May 2019, John David Anglin wrote:
> On 2019-05-01 12:21 p.m., Mikulas Patocka wrote:
> > On Wed, 1 May 2019, Helge Deller wrote:
> >
> >> Hi Mikulas,
> >>
> >> On 01.05.19 16:22, Mikulas Patocka wrote:
> >>> I tested it on C8000 and confim that it works.
> >> Thanks for testing!
> >>
> >> By the way, I made you the author of the patch in git:
> >> https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/commit/?h=for-next&id=f1abe94b271807902d5b286c7216b812645713e2
> >>
> >> In general, there are so many new cool features and patches pending
> >> in the for-next tree, so I appreciate every kind of testing:
> >> https://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git/log/?h=for-next
> >>
> >> Helge
> > The new kernel hangs on boot here:
> My c8000 booted okay using above tree.
>
> Dave
My obeservation is:
CONFIG_FLATMEM_MANUAL=y - doesn't compile. With the Helge's patch, it
compiles and works - but it only sees the first 1GiB of memory.
CONFIG_SPARSEMEM_MANUAL=y, CONFIG_SPARSEMEM_VMEMMAP=n - works.
CONFIG_SPARSEMEM_MANUAL=y, CONFIG_SPARSEMEM_VMEMMAP=y - hangs on boot.
Mikulas
next prev parent reply other threads:[~2019-05-02 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 17:34 [PATCH][RFC] parisc: Use per-pagetable spinlock (v2) Helge Deller
2019-05-01 14:22 ` Mikulas Patocka
2019-05-01 14:34 ` Helge Deller
2019-05-01 16:21 ` Mikulas Patocka
2019-05-02 1:27 ` John David Anglin
2019-05-02 13:43 ` Mikulas Patocka [this message]
2019-05-02 14:34 ` John David Anglin
2019-05-02 16:14 ` Helge Deller
2019-05-02 17:40 ` Mikulas Patocka
2019-05-03 11:58 ` John David Anglin
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=alpine.LRH.2.02.1905020920560.18084@file01.intranet.prod.int.rdu2.redhat.com \
--to=mpatocka@redhat.com \
--cc=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=linux-parisc@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 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).