search for: xen_setup_shutdown_ev

...uspend: remove xen_hvm_suspend Stefano Stabellini (9): xen: do not try to allocate the callback vector again at restore time xen: do not set xenstored_ready before xenbus_probe on hvm xen: do not initialize PV timers on HVM if !xen_have_vector_callback xen: no need to delay xen_setup_shutdown_event for hvm guests anymore xen: do not use xen_info on HVM, set pv_info name to "Xen HVM" xen-blkfront: handle Xen major numbers other than XENVBD xen: make the ballon driver work for hvm domains xen: PV on HVM: support PV spinlocks and IPIs xen: fix compile i...

Hi all, this patch series introduces stolen ticks accounting for Xen on ARM. Stolen ticks are clocksource ticks that have been "stolen" from the cpu, typically because Linux is running in a virtual machine and the vcpu has been descheduled. To account for these ticks we introduce CONFIG_PARAVIRT and pv_time_ops so that we can make use of:

Hi, another issue I''m seeing with 3.0-rc2 and Xen is that there is an unexpectedly high amount of kernel reserved memory. I suspect that Linux allocates page table entries and corresponding data structures for the whole 6GB areas of the provided ''physical RAM map'' even though it has rather big unusable holes in it. [ 0.000000] BIOS-provided physical RAM map: [

Hi all, this patch series enables xen-swiotlb on arm and arm64. It has been heavily reworked compared to the previous versions in order to achieve better performances and to address review comments. We are not using dma_mark_clean to ensure coherency anymore. We call the platform implementation of map_page and unmap_page. We assume that dom0 has been mapped 1:1 (physical address == machine

Lots of changes since v2, too much to remember or summarize. Please ignore patch 11/11, it's just for my testing. Rich.