Re: [PATCH] kvm tools: adds a PCI device that exports a host shared segment as a PCI BAR in the guest

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

 



On Sun, Aug 28, 2011 at 10:34:45AM +0300, Avi Kivity wrote:
> On 08/26/2011 01:03 AM, David Evensky wrote:
> >I need to specify the physical address because I need to ioremap the
> >memory during boot.
> 
> Did you consider pci_ioremap_bar()?

No, the code needs a physical memory address, not a PCI device. I
suppose we could do something special for PCI devices, but that wasn't
our intent. That said, this was also one of those things you learn every
day. :-)

> >The production issue I think is a memory limitation. We certainly do
> >use QEMU a lot; but for this the kvm tool is a better fit.
> >
> 
> What is this memory limitation?

It isn't a hard and fast number; just trying to maximize the number of
guests we can have.

> -- 
> I have a truly marvellous patch that fixes the bug which this
> signature is too narrow to contain.
> 
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux