From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>, dario.faggioli@citrix.com
Cc: xen-devel@lists.xenproject.org, julien.grall@arm.com,
sstabellini@kernel.org
Subject: Re: CONFIG_SCRUB_DEBUG=y + arm64 + livepatch = Xen BUG at page_alloc.c:738
Date: Tue, 12 Sep 2017 20:01:48 -0400 [thread overview]
Message-ID: <20170913000147.GA6632@localhost.localdomain> (raw)
In-Reply-To: <7b76a7a2-90fd-f016-53b0-a36ef68ba1a4@oracle.com>
On Mon, Sep 11, 2017 at 08:45:02PM -0400, Boris Ostrovsky wrote:
>
>
> On 09/11/2017 07:55 PM, Konrad Rzeszutek Wilk wrote:
> > Hey,
> >
> > I've only been able to reproduce this on ARM64 (trying right now ARM32
> > as well), and not on x86.
> >
> > If I compile Xen without CONFIG_SCRUB_DEBUG it works great. But if
> > enable it and try to load a livepatch it blows up in page_alloc.c:738
> >
> > This is with origin/staging (d0291f3391)
>
> Can you still reproduce this if you revert 307c3be?
Sadly yes - it still crashes. I didn't capture the serial output.
I honestly think the issue is that on ARM64 the "sleep" loop does not
wake up as often as on x86 (CC-ing Dariof who I believe observed this
with Credit2 and the wakeup.. something) - maybe he remembers the
details. Anyhow my theory is that the pages are not scrubbed at all
when they go in the idle loop as once it goes to sleep - it stays there.
Ah, see commit 05c52278a7c92bc753d9fe32017e4961012b9f23
Maybe this is related?
>
>
> -boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-09-13 0:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 23:55 CONFIG_SCRUB_DEBUG=y + arm64 + livepatch = Xen BUG at page_alloc.c:738 Konrad Rzeszutek Wilk
2017-09-12 0:45 ` Boris Ostrovsky
2017-09-13 0:01 ` Konrad Rzeszutek Wilk [this message]
2017-09-13 1:19 ` Boris Ostrovsky
2017-09-13 15:32 ` Konrad Rzeszutek Wilk
2017-09-13 18:05 ` Boris Ostrovsky
2017-09-13 18:25 ` Julien Grall
2017-09-13 18:49 ` Boris Ostrovsky
2017-09-14 21:26 ` Konrad Rzeszutek Wilk
2017-09-14 21:39 ` Boris Ostrovsky
2017-09-15 18:48 ` Konrad Rzeszutek Wilk
2017-09-15 19:20 ` Boris Ostrovsky
2017-09-15 19:50 ` Konrad Rzeszutek Wilk
2017-09-15 20:28 ` Julien Grall
2017-09-13 7:56 ` Dario Faggioli
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=20170913000147.GA6632@localhost.localdomain \
--to=konrad@kernel.org \
--cc=boris.ostrovsky@oracle.com \
--cc=dario.faggioli@citrix.com \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).