From: Borislav Petkov <bp@alien8.de>
To: akpm@linux-foundation.org
Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, ard.biesheuvel@linaro.org,
arnd@arndb.de, aryabinin@virtuozzo.com, benh@kernel.crashing.org,
borntraeger@de.ibm.com, cai@lca.pw, catalin.marinas@arm.com,
dave.hansen@linux.intel.com, dave.jiang@intel.com,
davem@davemloft.net, dvyukov@google.com, glider@google.com,
gor@linux.ibm.com, heiko.carstens@de.ibm.com, hpa@zytor.com,
james.morse@arm.com, jhogan@kernel.org,
kan.liang@linux.intel.com, linux-mm@kvack.org,
linux@armlinux.org.uk, luto@kernel.org, mark.rutland@arm.com,
mawilcox@microsoft.com, mingo@elte.hu,
mm-commits@vger.kernel.org, mpe@ellerman.id.au,
n-horiguchi@ah.jp.nec.com, palmer@sifive.com,
paul.burton@mips.com, paul.walmsley@sifive.com, paulus@samba.org,
peterz@infradead.org, ralf@linux-mips.org,
shashim@codeaurora.org, steven.price@arm.com, tglx@linutronix.de,
torvalds@linux-foundation.org, vgupta@synopsys.com,
will@kernel.org, zong.li@sifive.com
Subject: Re: [patch 064/158] mm: add generic ptdump
Date: Sun, 1 Dec 2019 10:07:24 +0100 [thread overview]
Message-ID: <20191201090724.GA6629@zn.tnic> (raw)
In-Reply-To: <20191201015304.cRPsmKUTM%akpm@linux-foundation.org>
On Sat, Nov 30, 2019 at 05:53:04PM -0800, akpm@linux-foundation.org wrote:
> From: Steven Price <steven.price@arm.com>
> Subject: mm: add generic ptdump
>
> Add a generic version of page table dumping that architectures can opt-in
> to
That generic ptdump stuff is probably causing a splat on 32-bit:
https://lkml.kernel.org/r/20191125144946.GA6628@duo.ucw.cz
.config is attached in that thread too and triggers pretty reliably in a
vm but I haven't poked at it further.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2019-12-01 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 1:53 [patch 064/158] mm: add generic ptdump akpm
2019-12-01 9:07 ` Borislav Petkov [this message]
2019-12-01 14:45 ` Linus Torvalds
2019-12-01 15:10 ` Borislav Petkov
2019-12-01 15:21 ` Borislav Petkov
2019-12-01 15:45 ` Borislav Petkov
2019-12-02 9:09 ` Steven Price
2019-12-02 15:42 ` Borislav Petkov
2019-12-03 10:47 ` David Hildenbrand
2019-12-03 11:00 ` David Hildenbrand
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=20191201090724.GA6629@zn.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=aryabinin@virtuozzo.com \
--cc=benh@kernel.crashing.org \
--cc=borntraeger@de.ibm.com \
--cc=cai@lca.pw \
--cc=catalin.marinas@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=jhogan@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=luto@kernel.org \
--cc=mark.rutland@arm.com \
--cc=mawilcox@microsoft.com \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=palmer@sifive.com \
--cc=paul.burton@mips.com \
--cc=paul.walmsley@sifive.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=ralf@linux-mips.org \
--cc=shashim@codeaurora.org \
--cc=steven.price@arm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vgupta@synopsys.com \
--cc=will@kernel.org \
--cc=zong.li@sifive.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 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).