Re: [PATCH v3] kvm tools, vesa: Use guest-mapped memory for framebuffer

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

 



On Mon, Jun 6, 2011 at 7:06 PM, Sasha Levin <levinsasha928@xxxxxxxxx> wrote:
> Currently VESA was mapping itself into 0xd0000000 which means that we'll
> have an overlap when we're using more than 4GB.
>
> Maybe we should increase our PCI gap size (which starts at 0xf0000000
> currently) to include that memory? This way we could prevent an overlap
> if we use large amount of RAM and that extra gap won't really hurt
> anything if we don't use VESA.

Yup. I sent a v4 that does that. I guess that we need to do this
properly as soon as the next driver that needs more hacks comes along
;-).

                         Pekka
--
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