#
4f045c57 |
| 11-Aug-2011 |
Sasha Levin <levinsasha928@gmail.com> |
kvm tools: Use correct size for VESA memory bar
This patch makes BAR 1 16k, instead of BAR0 - which is the PIO bar.
This fixes wrong output on lspci command and ioremap warnings during boot.
Signe
kvm tools: Use correct size for VESA memory bar
This patch makes BAR 1 16k, instead of BAR0 - which is the PIO bar.
This fixes wrong output on lspci command and ioremap warnings during boot.
Signed-off-by: Sasha Levin <levinsasha928@gmail.com> Signed-off-by: Pekka Enberg <penberg@kernel.org>
show more ...
|
#
c64f7ff0 |
| 06-Aug-2011 |
Sasha Levin <levinsasha928@gmail.com> |
kvm tools: Fix PCI masking on probes
This patch adds a missing check of mask during probing of PCI BARs.
The missing check manifested in wrong address values for the BARs after the initial probe.
kvm tools: Fix PCI masking on probes
This patch adds a missing check of mask during probing of PCI BARs.
The missing check manifested in wrong address values for the BARs after the initial probe.
Reported-by: David Evensky <evensky@dancer.ca.sandia.gov> Signed-off-by: Sasha Levin <levinsasha928@gmail.com> Signed-off-by: Pekka Enberg <penberg@kernel.org>
show more ...
|
#
7fca1897 |
| 17-Jun-2011 |
Sasha Levin <levinsasha928@gmail.com> |
kvm tools: Fix attempt to free mmaped memory
Framebuffer memory which was mmap() is being free() at the shutdown of the guest, leading to glibc errors.
Signed-off-by: Sasha Levin <levinsasha928@gma
kvm tools: Fix attempt to free mmaped memory
Framebuffer memory which was mmap() is being free() at the shutdown of the guest, leading to glibc errors.
Signed-off-by: Sasha Levin <levinsasha928@gmail.com> Signed-off-by: Pekka Enberg <penberg@kernel.org>
show more ...
|
#
96feb589 |
| 06-Jun-2011 |
Pekka Enberg <penberg@kernel.org> |
kvm tools, vesa: Use guest-mapped memory for framebuffer
This patch converts hw/vesa.c to use guest-mapped memory for framebuffer and drops the slow MMIO emulation. This speeds up framebuffer access
kvm tools, vesa: Use guest-mapped memory for framebuffer
This patch converts hw/vesa.c to use guest-mapped memory for framebuffer and drops the slow MMIO emulation. This speeds up framebuffer accesses considerably. Please note that this can be optimized even more with the KVM_GET_DIRTY_LOG ioctl() as explained by Alexander Graf.
Cc: Alexander Graf <agraf@suse.de> Cc: Cyrill Gorcunov <gorcunov@gmail.com> Cc: Ingo Molnar <mingo@elte.hu> Cc: John Floren <john@jfloren.net> Cc: Sasha Levin <levinsasha928@gmail.com> Signed-off-by: Pekka Enberg <penberg@kernel.org>
show more ...
|
#
73f7e5b3 |
| 03-Jun-2011 |
Sasha Levin <levinsasha928@gmail.com> |
kvm tools: Add MMIO coalescing support
Coalescing MMIO allows us to avoid an exit every time we have a MMIO write, instead - MMIO writes are coalesced in a ring which can be flushed once an exit for
kvm tools: Add MMIO coalescing support
Coalescing MMIO allows us to avoid an exit every time we have a MMIO write, instead - MMIO writes are coalesced in a ring which can be flushed once an exit for a different reason is needed. A MMIO exit is also trigged once the ring is full.
Coalesce all MMIO regions registered in the MMIO mapper. Add a coalescing handler under kvm_cpu.
Signed-off-by: Sasha Levin <levinsasha928@gmail.com> Signed-off-by: Pekka Enberg <penberg@kernel.org>
show more ...
|
#
aba1efa5 |
| 03-Jun-2011 |
Pekka Enberg <penberg@kernel.org> |
kvm tools, ui: Move VNC specific framebuffer code to ui/vnc.c
This patch makes use of 'struct framebuffer' and moves the VNC code to ui/vnc.c in preparation for other framebuffer output targets.
Ac
kvm tools, ui: Move VNC specific framebuffer code to ui/vnc.c
This patch makes use of 'struct framebuffer' and moves the VNC code to ui/vnc.c in preparation for other framebuffer output targets.
Acked-by: Ingo Molnar <mingo@elte.hu> Cc: Cyrill Gorcunov <gorcunov@gmail.com> Cc: John Floren <john@jfloren.net> Cc: Sasha Levin <levinsasha928@gmail.com> Signed-off-by: Pekka Enberg <penberg@kernel.org>
show more ...
|
#
e342083c |
| 01-Jun-2011 |
John Floren <john@jfloren.net> |
kvm tools: Add support for PS/2 keyboard system
Add support for PS/2 keyboard system with AUX device (aka mouse). The device works with vnc, the guest must be started with the '--vnc' parameter for
kvm tools: Add support for PS/2 keyboard system
Add support for PS/2 keyboard system with AUX device (aka mouse). The device works with vnc, the guest must be started with the '--vnc' parameter for the device to be initialized.
Signed-off-by: John Floren <john@jfloren.net> [ turn into patch and clean up code ] Signed-off-by: Sasha Levin <levinsasha928@gmail.com> Signed-off-by: Pekka Enberg <penberg@kernel.org>
show more ...
|
#
947392bc |
| 26-May-2011 |
Sasha Levin <levinsasha928@gmail.com> |
kvm tools: Use dynamic IO port allocation in vesa driver
Signed-off-by: Sasha Levin <levinsasha928@gmail.com> Signed-off-by: Pekka Enberg <penberg@kernel.org>
|
#
3d62dea6 |
| 26-May-2011 |
Sasha Levin <levinsasha928@gmail.com> |
kvm tools: Add optional parameter used in ioport callbacks
Allow specifying an optional parameter when registering an ioport range. The callback functions provided by the registering module will be
kvm tools: Add optional parameter used in ioport callbacks
Allow specifying an optional parameter when registering an ioport range. The callback functions provided by the registering module will be called with the same parameter.
This may be used to keep context during callbacks on IO operations.
Signed-off-by: Sasha Levin <levinsasha928@gmail.com> Signed-off-by: Pekka Enberg <penberg@kernel.org>
show more ...
|
#
de960f08 |
| 23-May-2011 |
Pekka Enberg <penberg@kernel.org> |
kvm tools: Code cleanups to hw/vesa.c
Tidy up the code in hw/vesa.c:
- Make videomem local to hw/vesa.c
- Remove debugging printf() calls
- Fix up coding style issues
Cc: John Floren <john
kvm tools: Code cleanups to hw/vesa.c
Tidy up the code in hw/vesa.c:
- Make videomem local to hw/vesa.c
- Remove debugging printf() calls
- Fix up coding style issues
Cc: John Floren <john@jfloren.net> Cc: Sasha Levin <levinsasha928@gmail.com> Signed-off-by: Pekka Enberg <penberg@kernel.org>
show more ...
|
#
b025083d |
| 23-May-2011 |
John Floren <john@jfloren.net> |
kvm tools: Add VESA device
Add a simple VESA device which simply moves a framebuffer from guest kernel to a VNC server.
VESA device PCI code is very similar to virtio-* PCI code.
Signed-off-by: Jo
kvm tools: Add VESA device
Add a simple VESA device which simply moves a framebuffer from guest kernel to a VNC server.
VESA device PCI code is very similar to virtio-* PCI code.
Signed-off-by: John Floren <john@jfloren.net> [ turning code into patches and cleanup ] Signed-off-by: Sasha Levin <levinsasha928@gmail.com> Signed-off-by: Pekka Enberg <penberg@kernel.org>
show more ...
|