Re: [Xen-devel] [PATCH 0/6] iomem cacheability

[Stefano Stabellini <sstabellini@xxxxxxxxxx>]

On Thu, 7 Mar 2019, Julien Grall wrote:
> On 07/03/2019 08:42, Amit Tomer wrote:
> > Hi,
> > 
> > > 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.
> > > 
> > Thanks for pointing that out.
> > 
> > Is it like we need to create "separate" reserve-memory
> > node(make_reserved-memory_node) when
> > memory node is encountered?
> 
> Sorry I don't understand what you mean.
> 
> What I meant is reserved-regions is some memory that have been carved out from
> the RAM. So the reserved-regions needs to be described in the memory node
> (memory@<addr>). We can either append them to the memory node created by
> make_memory_node. Or introduce new ones.
> 
> I haven't yet thought which one is more suitable.

Yes, you are right. I made a couple of quick fixes for this issue and
another issue raised by Julien during review (the usage of p2m_ram_t).
Amit, if you would like to give it a try I have a work-in-progress
branch with the fixes here:

http://xenbits.xenproject.org/git-http/people/sstabellini/xen-unstable.git 
iomem_cache-wip

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel