From: Avi Kivity <avi@qumranet.com> To: kvm-devel <kvm-devel@lists.sourceforge.net> Cc: linux-kernel <linux-kernel@vger.kernel.org>, Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@elte.hu> Subject: [PATCH 0/6] KVM userspace interface updates for 2.6.21 Date: Wed, 21 Feb 2007 20:11:58 +0200 [thread overview] Message-ID: <45DC8B6E.5050205@qumranet.com> (raw) The following patchset moves the kvm userspace interface from having a single fd, to having three types of file descriptors: - one fd returned by open("/dev/kvm") is used for generic access to the kvm driver, for example to get the API version and to create virtual machines - when you create a virtual machine, you get back an fd that can be used to control vm-wide aspects, like guest memory configuratio - when you create a virtual cpu, you get an fd that can be used to control the vcpu, for example getting and setting registers, and if you're really serious, running the guest The motivation for this change is twofold: - prevent having a 'struct inode' and 'struct file' with different file operation callbacks - prevent cacheline bouncing of the 'struct file' when we support guest smp (by giving each vcpu its own file structure) A side effect is that the code becomes somewhat cleaner, due to the vcpu number not being passed around and validated. The change was discussed on kvm-devel some time ago. Thanks to Arnd Bergmann for useful suggestions and to the epoll code for inspiration. -- error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org> Cc: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>, linux-kernel <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org> Subject: [PATCH 0/6] KVM userspace interface updates for 2.6.21 Date: Wed, 21 Feb 2007 20:11:58 +0200 [thread overview] Message-ID: <45DC8B6E.5050205@qumranet.com> (raw) The following patchset moves the kvm userspace interface from having a single fd, to having three types of file descriptors: - one fd returned by open("/dev/kvm") is used for generic access to the kvm driver, for example to get the API version and to create virtual machines - when you create a virtual machine, you get back an fd that can be used to control vm-wide aspects, like guest memory configuratio - when you create a virtual cpu, you get an fd that can be used to control the vcpu, for example getting and setting registers, and if you're really serious, running the guest The motivation for this change is twofold: - prevent having a 'struct inode' and 'struct file' with different file operation callbacks - prevent cacheline bouncing of the 'struct file' when we support guest smp (by giving each vcpu its own file structure) A side effect is that the code becomes somewhat cleaner, due to the vcpu number not being passed around and validated. The change was discussed on kvm-devel some time ago. Thanks to Arnd Bergmann for useful suggestions and to the epoll code for inspiration. -- 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
next reply other threads:[~2007-02-21 18:12 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-21 18:11 Avi Kivity [this message] 2007-02-21 18:11 ` [PATCH 0/6] KVM userspace interface updates for 2.6.21 Avi Kivity 2007-02-21 18:13 ` [PATCH 1/6] KVM: Add internal filesystem for generating inodes Avi Kivity 2007-02-21 18:13 ` Avi Kivity 2007-02-21 18:14 ` [PATCH 2/6] KVM: Create an inode per virtual machine Avi Kivity 2007-02-21 18:14 ` Avi Kivity 2007-02-21 18:15 ` [PATCH 3/6] KVM: Rename some kvm_dev_ioctl_*() functions to kvm_vm_ioctl_*() Avi Kivity 2007-02-21 18:15 ` Avi Kivity 2007-02-21 18:16 ` [PATCH 4/6] KVM: Move kvm_vm_ioctl_create_vcpu() around Avi Kivity 2007-02-21 18:16 ` Avi Kivity 2007-02-21 18:17 ` [PATCH 5/6] KVM: Per-vcpu inodes Avi Kivity 2007-02-21 18:17 ` Avi Kivity 2007-02-21 18:18 ` [PATCH 6/6] KVM: Bump API version Avi Kivity 2007-02-21 18:18 ` Avi Kivity 2007-02-21 18:21 ` [PATCH 0/6] KVM userspace interface updates for 2.6.21 Avi Kivity 2007-02-21 18:21 ` Avi Kivity 2007-02-21 19:08 ` [kvm-devel] " Rusty Russell 2007-02-21 19:08 ` Rusty Russell 2007-02-25 9:58 ` Avi Kivity 2007-02-25 9:58 ` Avi Kivity 2007-02-25 11:47 ` Andrew Morton 2007-02-25 11:47 ` Andrew Morton
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=45DC8B6E.5050205@qumranet.com \ --to=avi@qumranet.com \ --cc=akpm@osdl.org \ --cc=kvm-devel@lists.sourceforge.net \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@elte.hu \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.