Hello!
> Limiting high MMIO to 2GB is also relatively little.
Ok, then what about 512GB window @ 512GB address? Would this satisfy everybody
?
[VIRT_PCIE_MMIO_HIGH] = {0x80, 0x80 }
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
Hello!
> > --- a/hw/arm/virt.c
> > +++ b/hw/arm/virt.c
> > @@ -125,6 +125,7 @@ static const MemMapEntry a15memmap[] = {
> > [VIRT_PCIE_PIO] = { 0x3eff, 0x0001 },
> > [VIRT_PCIE_ECAM] = { 0x3f00, 0x0100 },
> > [VIRT_MEM] ={ 0x40
On 23/07/2015 13:57, Alexander Graf wrote:
>> > @@ -125,6 +125,7 @@ static const MemMapEntry a15memmap[] = {
>> > [VIRT_PCIE_PIO] = { 0x3eff, 0x0001 },
>> > [VIRT_PCIE_ECAM] = { 0x3f00, 0x0100 },
>> > [VIRT_MEM] ={ 0x4000, 30UL
On 23.07.15 13:42, Pavel Fedin wrote:
> This large region is necessary for some devices like ivshmem and video cards
>
> Signed-off-by: Pavel Fedin
> ---
> A small merge conflict in virt.h is possible when applying the patch to
> current master. It is
> caused by change made by my vGICv3 seri
This large region is necessary for some devices like ivshmem and video cards
Signed-off-by: Pavel Fedin
---
A small merge conflict in virt.h is possible when applying the patch to
current master. It is
caused by change made by my vGICv3 series (VIRT_GIC_V2M changed).
---
hw/arm/virt.c
