On Mon, Jan 15, 2018 at 12:22:48PM +0100, Marc-Andre Lureau wrote:
> Hi
>
> On Mon, Jan 15, 2018 at 9:55 AM, Peter Xu wrote:
> > fw_cfg device does not need IOMMU protection, so use physical addresses
> > always. That's how QEMU implements fw_cfg. Otherwise we'll see call
> > traces during boot
Hi
On Mon, Jan 15, 2018 at 9:55 AM, Peter Xu wrote:
> fw_cfg device does not need IOMMU protection, so use physical addresses
> always. That's how QEMU implements fw_cfg. Otherwise we'll see call
> traces during boot when vIOMMU is enabled in guest:
>
> [1.018306] [ cut here ]--
fw_cfg device does not need IOMMU protection, so use physical addresses
always. That's how QEMU implements fw_cfg. Otherwise we'll see call
traces during boot when vIOMMU is enabled in guest:
[1.018306] [ cut here ]
[1.018314] WARNING: CPU: 1 PID: 1 at drivers/fir