Re: BAR Conflict

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> >>>> and kvm does not want to go further. dmesg, /proc/iomem and lspci are at
> >>>> the end of this email.
> >>>> The memory reserved by BIOS-e820
> >>>> [    0.000000]  BIOS-e820: 00000000fa000000 - 00000000fc000000
> >>>> (reserved)
> >>>> Quadro 2000 is 05:00.0 and its conflicting BAR is
> >>>>        Region 3: Memory at f8000000 (64-bit, prefetchable) [disabled]
> >>>> [size=64M]
> >>>> and its upstream bridge 00:1c.00
> OK, if it's safe to ignore for PCI allocations, then ignore the
> reservation. But I think that should be done automatically if somehow
> possible, not by the user via a kernel parameter.
> 
> Is there a simple way to test such a policy without significant
> refactoring of the e820 code?

Why not just make the kvm PCI passthrough code check the MMIO
of the card and make an "gap" in the E820 for that region. In essence
creating a PCI I/O region?

Why does QEMU setup up that reserved region? Can it move it?
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux