On 24/05/20 16:27, Philippe Mathieu-Daudé wrote:
>> In an ideal world all our DMA devices would use some kind of common
>> framework or design pattern so they didn't hog all the CPU
>> and/or spend minutes with the BQL held if the guest requests
>> an enormous-sized DMA. In practice many of them ju
On 24/05/2020 14:40, Peter Maydell wrote:
> On Sun, 24 May 2020 at 11:30, Philippe Mathieu-Daudé
> wrote:
>> It looks to me a normal behavior for a DMA device. DMA devices have a
>> different address space view than the CPUs.
>> Also note the fw_cfg is a generic device, not restricted to the x86
On 5/24/20 3:40 PM, Peter Maydell wrote:
> On Sun, 24 May 2020 at 11:30, Philippe Mathieu-Daudé
> wrote:
>> It looks to me a normal behavior for a DMA device. DMA devices have a
>> different address space view than the CPUs.
>> Also note the fw_cfg is a generic device, not restricted to the x86 a
On Sun, 24 May 2020 at 11:30, Philippe Mathieu-Daudé wrote:
> It looks to me a normal behavior for a DMA device. DMA devices have a
> different address space view than the CPUs.
> Also note the fw_cfg is a generic device, not restricted to the x86 arch.
In an ideal world all our DMA devices would
On 5/24/20 6:12 AM, Alexander Bulekov wrote:
> Public bug reported:
>
> For me, this takes close to 3 minutes at 100% CPU:
> echo "outl 0x518 0x9596" | ./i386-softmmu/qemu-system-i386 -M q35 -m 32
> -nographic -accel qtest -monitor none -serial none -qtest stdio
>
> #0 phys_page_find (d=0x6
Public bug reported:
For me, this takes close to 3 minutes at 100% CPU:
echo "outl 0x518 0x9596" | ./i386-softmmu/qemu-system-i386 -M q35 -m 32
-nographic -accel qtest -monitor none -serial none -qtest stdio
#0 phys_page_find (d=0x60635d80, addr=136728041144404) at /exec.c:338
#1 addre
