summaryrefslogtreecommitdiffstats
path: root/classes/meta-virt-k8s-cfg.bbclass
diff options
context:
space:
mode:
authorMichal Orzel <michal.orzel@arm.com>2022-06-09 11:57:47 +0200
committerBruce Ashfield <bruce.ashfield@gmail.com>2022-06-20 12:07:45 -0400
commit17f3d28228341b5fc80ffcfa8847f4cfb74991bf (patch)
tree78d92b20a61a10b99b8ea4fd0cbf045ecd2bc90c /classes/meta-virt-k8s-cfg.bbclass
parentec96eab80c3caa59fa7d086398d5a5a2895b8b68 (diff)
downloadmeta-virtualization-17f3d28228341b5fc80ffcfa8847f4cfb74991bf.tar.gz
Revert "xen: Disable PCI on qemuarm with Xen"
This reverts commit fb0a7b97db4f419b82309f98a4944ae3330d1e2e. Justification: Commit fb0a7b97db4f removed the PCI node from the qemu device tree due to the issue when trying to access PCI configuration space that was causing Linux running on top of Xen to end up in an infinite loop. The investigation showed that the problem occurs due to qemu placing ECAM space at 256GiB mark. Even though Xen officially supports on arm32 up to 12GiB of physical address space, it is able to map it correctly for dom0. However, when Linux tries to access the ECAM space and the stage2 translation fault occurs, HPFAR register contains incorrect IPA. We can say it is incorrect because using hardware AT instruction or software lookup, we can obtain the correct IPA from the same VA. This can suggest that the problem is related to QEMU fault handling. Instead of removing the PCI node the follow-up commit will disable highmem option in qemu which will cause placing ECAM space in the 32-bit space. Signed-off-by: Michal Orzel <michal.orzel@arm.com> Reviewed-by: Bertrand Marquis <bertrand.marquis@arm.com> Reviewed-by: Christopher Clark <christopher.w.clark@gmail.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
Diffstat (limited to 'classes/meta-virt-k8s-cfg.bbclass')
0 files changed, 0 insertions, 0 deletions