linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: Zi Yan <ziy@nvidia.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	Michal Hocko <mhocko@kernel.org>,
	Jesper Dangaard Brouer <brouer@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH 2/2] mm/page_alloc: Allow high-order pages to be stored on the per-cpu lists
Date: Thu, 10 Jun 2021 12:18:21 +0100	[thread overview]
Message-ID: <20210610111821.GY30378@techsingularity.net> (raw)
In-Reply-To: <88FCC7AA-FAAA-4B87-B382-50BD54B2886B@nvidia.com>

On Wed, Jun 09, 2021 at 02:30:18PM -0400, Zi Yan wrote:
> On 3 Jun 2021, at 10:22, Mel Gorman wrote:
> > Signed-off-by: Mel Gorman <mgorman@techsingularity.net>
> > Acked-by: Vlastimil Babka <vbabka@suse.cz>
> > ---
> >  include/linux/mmzone.h |  20 +++++-
> >  mm/internal.h          |   2 +-
> >  mm/page_alloc.c        | 159 +++++++++++++++++++++++++++++------------
> >  mm/swap.c              |   2 +-
> >  4 files changed, 135 insertions(+), 48 deletions(-)
> >
> 
> Hi Mel,
> 
> I am not able to boot my QEMU VM with v5.13-rc5-mmotm-2021-06-07-18-33.
> git bisect points to this patch. The VM got stuck at ???Booting from ROM??????.
> 
> My kernel config is attached and my qemu command is:
> 
> qemu-system-x86_64 -kernel ~/repos/linux-1gb-thp/arch/x86/boot/bzImage \
>     -drive file=~/qemu-image/vm.qcow2,if=virtio \
>     -append "nokaslr root=/dev/vda1 rw console=ttyS0 " \
>     -pidfile vm.pid \
>     -netdev user,id=mynet0,hostfwd=tcp::11022-:22 \
>     -device virtio-net-pci,netdev=mynet0 \
>     -m 16g -smp 6 -cpu host -enable-kvm -nographic \
>     -machine hmat=on -object memory-backend-ram,size=8g,id=m0 \
>     -object memory-backend-ram,size=8g,id=m1 \
>     -numa node,memdev=m0,nodeid=0 -numa node,memdev=m1,nodeid=1
> 
> The attached config has THP disabled. The VM cannot boot with THP enabled,
> either.
> 

There is not a lot of information to go on here. Can you confirm that a
revert of that specific patch from mmotm-2021-06-07-18-33 also boots? It
sounds like your console log is empty, does anything useful appear if
you add "earlyprintk=serial,ttyS0,115200" to the kernel command line?

-- 
Mel Gorman
SUSE Labs


  reply	other threads:[~2021-06-10 11:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 14:22 [PATCH 0/2] Allow high order pages to be stored on PCP v2 Mel Gorman
2021-06-03 14:22 ` [PATCH 1/2] mm/page_alloc: Move free_the_page Mel Gorman
2021-06-03 14:22 ` [PATCH 2/2] mm/page_alloc: Allow high-order pages to be stored on the per-cpu lists Mel Gorman
2021-06-09 18:30   ` Zi Yan
2021-06-10 11:18     ` Mel Gorman [this message]
2021-06-10 11:40       ` Zi Yan
     [not found]         ` <20210611083433.GA30378@techsingularity.net>
     [not found]           ` <7E7AFAD1-A08E-4DE1-B307-C604A01BDC8C@nvidia.com>
2021-06-11 13:58             ` Mel Gorman
  -- strict thread matches above, loose matches on Subject: below --
2021-06-03  8:46 [PATCH 0/2] Allow high order pages to be stored on PCP Mel Gorman
2021-06-03  8:46 ` [PATCH 2/2] mm/page_alloc: Allow high-order pages to be stored on the per-cpu lists Mel Gorman
2021-06-03 11:12   ` Vlastimil Babka
2021-06-03 12:34     ` Mel Gorman
2021-06-03 13:04       ` Vlastimil Babka
2021-05-31 12:04 [RFC PATCH 0/2] Allow high order pages to be stored on PCP Mel Gorman
2021-05-31 12:04 ` [PATCH 2/2] mm/page_alloc: Allow high-order pages to be stored on the per-cpu lists Mel Gorman
2021-05-31 15:23   ` Jesper Dangaard Brouer
2021-06-01 12:45     ` Mel Gorman
2021-06-02 13:53       ` Jesper Dangaard Brouer

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=20210610111821.GY30378@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=akpm@linux-foundation.org \
    --cc=brouer@redhat.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=vbabka@suse.cz \
    --cc=ziy@nvidia.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).