Skip to contentSkip to conversation

KVM updates for Linux 2.6.21-rc2

GIT PULL Avi Kivity 2 participants 2 messages Mar 4, 2007 KVM

lore
Share & tools
lore

Avi Kivity

author
#0 lore raw

Linus,

The following changes since commit b648a0d22908116b4ef168935a160d7f17c4e6d:
Linus Torvalds (1):
Merge branch 'upstream-linus' of
master.kernel.org:/.../jgarzik/libata-dev

are found in the 'linus' branch of the git repository at:

git://kvm.qumranet.com/home/avi/kvm.git

The changes fall into three broad categories:
- initial kvm paravirtulization support
- the first batch of the stable userspace interface changes
- fixes, fixes, fixes

The userspace interface changes, while nontrivial, are crucially important as I'd like to freeze the non-paravirt userspace interface for 2.6.21. Unfortunately there are a few more changes of that nature pending.

The patches have been sitting in -mm collecting bit dust for a while, as well as in the regular kvm releases.

Please exercise more than the usual care when pulling as I am very much a git newbie.

Ahmed S. Darwish (1):
KVM: Use ARRAY_SIZE macro instead of manual calculation.

Andrew Morton (1):
KVM: Move kvmfs magic number to <linux/magic.h>

Avi Kivity (13):
KVM: mmu: add missing dirty page tracking cases
KVM: Cosmetics
KVM: Add hypercall host support for svm
KVM: Wire up hypercall handlers to a central arch-independent location
KVM: svm: init cr0 with the wp bit set
KVM: More 0 -> NULL conversions
KVM: Add internal filesystem for generating inodes
KVM: Create an inode per virtual machine
KVM: Rename some kvm_dev_ioctl_*() functions to kvm_vm_ioctl_*()
KVM: Move kvm_vm_ioctl_create_vcpu() around
KVM: Per-vcpu inodes
KVM: Bump API version
KVM: Fix bogus failure in kvm.ko module initialization

Ingo Molnar (2):
KVM: add MSR based hypercall API
KVM: Add host hypercall support for vmx

Jeremy Katz (1):
KVM: Move virtualization deactivation from CPU_DEAD state to
CPU_DOWN_PREPARE

Joerg Roedel (2):
KVM: vmx: hack set_cr0_no_modeswitch() to actually do modeswitch
KVM: SVM: intercept SMI to handle it at host level

Markus Rechberger (1):
KVM: Use page_private()/set_page_private() apis

Uri Lublin (4):
KVM: Add missing calls to mark_page_dirty()
KVM: Fix dirty page log bitmap size/access calculation
kvm: move do_remove_write_access() up
KVM: Remove write access permissions when dirty-page-logging is
enabled

drivers/kvm/kvm.h | 13 +-
drivers/kvm/kvm_main.c | 776
+++++++++++++++++++++++++++++++--------------

drivers/kvm/kvm_svm.h     |    3 +-
drivers/kvm/mmu.c         |   36 +-
drivers/kvm/paging_tmpl.h |   18 +-
drivers/kvm/svm.c         |   42 ++-
drivers/kvm/vmx.c         |   33 ++-
include/linux/kvm.h       |   50 ++--
include/linux/kvm_para.h  |   73 +++++
include/linux/magic.h     |    1 +
10 files changed, 748 insertions(+), 297 deletions(-)

create mode 100644 include/linux/kvm_para.h

Signature · 8 lines
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
#1 lore raw
Quoted 5 lines · Avi Kivity

The changes fall into three broad categories:
- initial kvm paravirtulization support
- the first batch of the stable userspace interface changes
- fixes, fixes, fixes

This is the absolute last time I say this.

WAY too late. You'd better get this in before -rc1 next time around. I want *FIXES*ONLY* by now, and next time I see crap like this I'm going to ignore it until you fix me a pull that contains fixes only, and I'm not even going to pull during the next merge window because I'm not interested in merging something that isn't maintained and doesn't get those "fixes only" trees.

So I pulled this now, but the fact is, I already ignored this once exactly because it wasn't appropriate to pull at this point. Yes, I soemtimes miss emails, but dammit, quite often it's also because I just judge the email to be *CRAP* and simply not worth bothering with.

750 new lines of code, with much of it apparently being new features, and stupid cleanups and cosmetics that don't actually fix anything simply isn't "post-rc2 material". I really *really* don't want to see this again!

I'm really fed up with having to pull big changes after the merge window, because it just doesn't seem to let up. I'm going to go postal on the next maintainer who doesn't understand what "merge window" and "fixes only" means.

Linus

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV