From: Vijay Kilari <vijay.kilari@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Andre Przywara <andre.przywara@arm.com>
Subject: Re: arm: alloc_heap_pages allocates already allocated page
Date: Tue, 7 Feb 2017 16:40:58 +0530 [thread overview]
Message-ID: <CALicx6v533d6yOs=RRsu5d7FJ9srv09W4PmkqDv0yinsnqYstw@mail.gmail.com> (raw)
In-Reply-To: <1545956c-a602-835a-aac0-8845a56e7b9e@arm.com>
On Tue, Feb 7, 2017 at 3:37 PM, Julien Grall <julien.grall@arm.com> wrote:
> On 07/02/2017 08:18, Vijay Kilari wrote:
>>
>> Hi,
>
>
> Hello,
>
>> I am seeing below panic with NUMA during DT mappings in
>> alloc_heap_pages()
>> BUG_ON(pg[i].count_info != PGC_state_free);
>> However, this issue is not there with 4.7 version. The same NUMA board
>> boots fine.
>
>
> I am a bit confused by what you are saying. Xen on ARM does not yet support
> NUMA. I also know you are working on NUMA support. So does the BUG happen on
> upstream xen or upstream xen + your patches?
I was testing with Andre ITS patches (RFC version 1) + my NUMA patches
+ upstream xen.
However now I tested with upstream xen + Andre ITS patches (staging
branch) on NUMA board.
I see panic (similar to what I see with my patches). Log are here.
http://pastebin.com/QJqUBvD9
The same plain upstream xen + Andre ITS patches boots fine with non-NUMA board.
>
> If the latter please provide more details on your modifications.
>
>> With 4.8 or staging I see below panic.
>
>
> I would recommend you to try bisecting to see if you can pin point a
> specific commit.
>
>>
>> I have add print in alloc_heap_pages to print page_to_mfn(pg) and
>> before and after calling
>> map_range_to_domain() DT mapping.
>> It shows that 0x83e22a is returned for multiple alloc_heap_page requests.
>
>
> This is fine as long as there is a free_heap_pages between the 2 calls of
> alloc_heap_pages. I would recommend you to look if free_heap_pages has been
> called.
>
> [....]
>
>
>> (XEN) Xen BUG at page_alloc.c:870
>
>
> I was not able to spot a BUG at line 870 but 827. I think, the
> BUG_ON(PGC_state_free) is here to catch potential bug in the allocator, all
> the pages allocated should always be free.
>
> Furthermore, we haven't made much changes in page_alloc.c recently. So this
> 43 lines differences made me wonder if you did other changes than adding
> debug?
Yes, I added debug prints.
>
> Regards,
>
> --
> Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-02-07 11:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 8:18 arm: alloc_heap_pages allocates already allocated page Vijay Kilari
2017-02-07 10:07 ` Julien Grall
2017-02-07 11:10 ` Vijay Kilari [this message]
2017-02-07 11:28 ` Julien Grall
2017-02-07 12:41 ` Vijay Kilari
2017-02-07 12:47 ` Julien Grall
2017-02-07 13:00 ` Julien Grall
2017-02-07 13:25 ` Vijay Kilari
2017-02-07 13:27 ` Julien Grall
2017-02-07 15:59 ` Vijay Kilari
2017-02-08 14:18 ` Julien Grall
2017-02-08 15:42 ` Julien Grall
2017-02-09 6:36 ` Vijay Kilari
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='CALicx6v533d6yOs=RRsu5d7FJ9srv09W4PmkqDv0yinsnqYstw@mail.gmail.com' \
--to=vijay.kilari@gmail.com \
--cc=andre.przywara@arm.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).