From: Julien Grall <Julien.Grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
Amit Tomer <amittomer25@gmail.com>
Cc: "wei.liu2@citrix.com" <wei.liu2@citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Julien Grall <julien.grall@gmail.com>,
Jan Beulich <JBeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
"ian.jackson@citrix.com" <ian.jackson@citrix.com>,
nd <nd@arm.com>
Subject: Re: [PATCH 0/6] iomem cacheability
Date: Wed, 6 Mar 2019 22:59:06 +0000 [thread overview]
Message-ID: <7b7c45ee-745f-1ede-1063-7fd66449194b@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1903061429230.17248@sstabellini-ThinkPad-X260>
Hi,
On 06/03/2019 22:42, Stefano Stabellini wrote:
> On Wed, 6 Mar 2019, Amit Tomer wrote:
>> Hi,
>>> Looking at the stack trace, this is very likely due to the issue I pointed out earlier on. I.e reserved-memory region should be described in the memory nodes.
>>
>> Do you mean, something like this(reserved-memory node is under memory node) ?
>
> No, I think Julien meant that all the reserved-memory regions ranges
> should be "covered" by the ranges of the memory node.
>
> If a reserved-memory node range is 0x54000000 - 0x57000000, then we need
> to make sure that the memory node includes that range. In your case, the
> first memory bank is 0x48000000 - 0x80000000 so it would clearly include
> the range 0x54000000 - 0x57000000. So, it looks like it is correct from
> that point of view.
Not really, the DT provided by Amit is for the host. The memory node
will be rewritten by Xen for Dom0 and does not include the
reserved-memory regions so far.
>
> I am suspecting there is a bug in the patch "xen/arm: map
> reserved-memory regions as normal memory in dom0", specifically in the
> implementation of check_reserved_memory.
I don't think the issue is in that code (see above).
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-03-06 22:59 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 23:06 [PATCH 0/6] iomem cacheability Stefano Stabellini
2019-02-26 23:07 ` [PATCH 1/6] xen: extend XEN_DOMCTL_memory_mapping to handle cacheability Stefano Stabellini
2019-02-26 23:18 ` Julien Grall
2019-04-20 0:02 ` Stefano Stabellini
2019-04-20 0:02 ` [Xen-devel] " Stefano Stabellini
2019-04-21 17:32 ` Julien Grall
2019-04-21 17:32 ` [Xen-devel] " Julien Grall
2019-04-22 21:59 ` Stefano Stabellini
2019-04-22 21:59 ` [Xen-devel] " Stefano Stabellini
2019-04-24 10:42 ` Julien Grall
2019-04-24 10:42 ` [Xen-devel] " Julien Grall
2019-02-27 10:34 ` Jan Beulich
2019-04-17 21:12 ` Stefano Stabellini
2019-04-17 21:12 ` [Xen-devel] " Stefano Stabellini
2019-04-17 21:25 ` Julien Grall
2019-04-17 21:25 ` [Xen-devel] " Julien Grall
2019-04-17 21:55 ` Stefano Stabellini
2019-04-17 21:55 ` [Xen-devel] " Stefano Stabellini
2019-04-25 10:41 ` Jan Beulich
2019-04-25 10:41 ` [Xen-devel] " Jan Beulich
2019-04-25 22:31 ` Stefano Stabellini
2019-04-25 22:31 ` [Xen-devel] " Stefano Stabellini
2019-04-26 7:12 ` Jan Beulich
2019-04-26 7:12 ` [Xen-devel] " Jan Beulich
2019-02-27 19:28 ` Julien Grall
2019-04-19 23:20 ` Stefano Stabellini
2019-04-19 23:20 ` [Xen-devel] " Stefano Stabellini
2019-04-21 17:14 ` Julien Grall
2019-04-21 17:14 ` [Xen-devel] " Julien Grall
2019-04-22 17:33 ` Stefano Stabellini
2019-04-22 17:33 ` [Xen-devel] " Stefano Stabellini
2019-04-22 17:42 ` Julien Grall
2019-04-22 17:42 ` [Xen-devel] " Julien Grall
2019-02-27 21:02 ` Julien Grall
2019-02-26 23:07 ` [PATCH 2/6] libxc: xc_domain_memory_mapping, " Stefano Stabellini
2019-02-26 23:07 ` [PATCH 3/6] libxl/xl: add cacheability option to iomem Stefano Stabellini
2019-02-27 20:02 ` Julien Grall
2019-04-19 23:13 ` Stefano Stabellini
2019-04-19 23:13 ` [Xen-devel] " Stefano Stabellini
2019-02-26 23:07 ` [PATCH 4/6] xen/arm: keep track of reserved-memory regions Stefano Stabellini
2019-02-28 14:38 ` Julien Grall
2019-02-26 23:07 ` [PATCH 5/6] xen/arm: map reserved-memory regions as normal memory in dom0 Stefano Stabellini
2019-02-26 23:45 ` Julien Grall
2019-04-22 22:42 ` Stefano Stabellini
2019-04-22 22:42 ` [Xen-devel] " Stefano Stabellini
2019-04-23 8:09 ` Julien Grall
2019-04-23 8:09 ` [Xen-devel] " Julien Grall
2019-04-23 17:32 ` Stefano Stabellini
2019-04-23 17:32 ` [Xen-devel] " Stefano Stabellini
2019-04-23 18:37 ` Julien Grall
2019-04-23 18:37 ` [Xen-devel] " Julien Grall
2019-04-23 21:34 ` Stefano Stabellini
2019-04-23 21:34 ` [Xen-devel] " Stefano Stabellini
2019-02-26 23:07 ` [PATCH 6/6] xen/docs: how to map a page between dom0 and domU using iomem Stefano Stabellini
2019-03-03 17:20 ` [PATCH 0/6] iomem cacheability Amit Tomer
2019-03-05 21:22 ` Stefano Stabellini
2019-03-05 22:45 ` Julien Grall
2019-03-06 11:46 ` Amit Tomer
2019-03-06 22:42 ` Stefano Stabellini
2019-03-06 22:59 ` Julien Grall [this message]
2019-03-07 8:42 ` Amit Tomer
2019-03-07 10:04 ` Julien Grall
2019-03-07 21:24 ` Stefano Stabellini
2019-03-08 10:10 ` Amit Tomer
2019-03-08 16:37 ` Julien Grall
2019-03-08 17:44 ` Amit Tomer
2019-03-06 11:30 ` Amit Tomer
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=7b7c45ee-745f-1ede-1063-7fd66449194b@arm.com \
--to=julien.grall@arm.com \
--cc=JBeulich@suse.com \
--cc=amittomer25@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=julien.grall@gmail.com \
--cc=nd@arm.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.