Hi,
> It might be possible to rework Dom0 memory allocation to limit the
> damage or even re-order the binary in memory. Amit, could you post the
> full Xen log with earlyprintk enabled?
Please find XEN logs :
[ 229.769854] Starting kernel ...
[ 229.773120]
- UART enabled -
- CPU boot
Hi,
On 3/8/19 10:10 AM, Amit Tomer wrote:
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:
We did try new b
Hi,
> 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:
We did try new branch with new fixes but we see s
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 poin
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
n
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
me
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, somethin
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) ?
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) ?
--- a/arch/arm64/boot/dts/renesas/r8a7795-h3ulcb
Hi
> Thanks for testing! You might have found a real bug in the series. Could
> you please also attach the full device tree?
Please find the attached DTS and DTB file used for testing.
Thanks
-Amit
r8a7795-h3ulcb.dts
Description: audio/vnd.dts
r8a7795-h3ulcb.dtb
Description: Binary data
_
Sorry for the formatting.
On Tue, 5 Mar 2019, 21:24 Stefano Stabellini,
wrote:
> On Sun, 3 Mar 2019, Amit Tomer wrote:
> > Hi,
> >
> > > This series introduces a cacheability parameter for the iomem option,
> so
> > > that we can map an iomem region into a guest as cacheable memory.
> > >
> > >
On Sun, 3 Mar 2019, Amit Tomer wrote:
> Hi,
>
> > This series introduces a cacheability parameter for the iomem option, so
> > that we can map an iomem region into a guest as cacheable memory.
> >
> > Then, this series fixes the way Xen handles reserved memory regions on
> > ARM: they should be ma
Hi,
> This series introduces a cacheability parameter for the iomem option, so
> that we can map an iomem region into a guest as cacheable memory.
>
> Then, this series fixes the way Xen handles reserved memory regions on
> ARM: they should be mapped as normal memory, instead today they are
> trea
Hi all,
This series introduces a cacheability parameter for the iomem option, so
that we can map an iomem region into a guest as cacheable memory.
Then, this series fixes the way Xen handles reserved memory regions on
ARM: they should be mapped as normal memory, instead today they are
treated as
14 matches
Mail list logo
