Re: [Xen-devel] [XEN/ARM PATCH v2 1/1] Add support for Exynos secure firmware

[Julien Grall <julien.grall@xxxxxxxxxx>]

Hi Suriyan,

On 17/09/14 15:17, Suriyan Ramasami wrote:
> > The code path is the same for the XU and the Arndale for the reset.
> > Let me check into this.
>
> This also has been confirmed to happen on the Odroid XU.
> I found that when __initconst is used for exynos_dt_pmu_matches[],
> when the reset code is executed, the memory address for
> exynos_dt_pmu_matches  when accessed generates a DATA abort. I wonder
> if the area where ever the init variables are, are invalidated when
> the dom0 is exiting? I am not sure.
>
> If I remove __initconst from exynos_dt_pmu_mathces[] then there is no
> such issue.
>
> I am wondering if someone has some expert comments on the use of
> __initconst and how that would effect the reset code?
All __initconst variable will live to a separate section. once Xen has 
finished to boot, the section will be freed and Xen may use the memory 
for itself or the guest.
If you plan to use the variables during the reset, then you should drop 
the __initconst.
Regards,

--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel