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

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

 



On Mon, 2011-06-06 at 15:56 +0200, Alexander Graf wrote:
> > @@ -216,7 +216,7 @@ void kvm__init_ram(struct kvm *kvm)
> > 		phys_size  = kvm->ram_size - phys_size;
> > 		host_mem   = kvm->ram_start + phys_start;
> > 
> > -		kvm_register_mem_slot(kvm, 1, phys_start, phys_size, host_mem);
> > +		kvm__register_mem_slot(kvm, 1, phys_start, phys_size, host_mem);
> 
> ... and also slot 1. Is this on purpose or could there be potential overwriting?

No, I just made a mess out of it and realized it too late. See v2 of the
patch I sent just now.

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