From: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/6] KVM userspace interface updates for 2.6.21
Date: Sun, 25 Feb 2007 03:47:37 -0800 [thread overview]
Message-ID: <20070225034737.16353a46.akpm@linux-foundation.org> (raw)
In-Reply-To: <45E15DBF.8000106-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
> On Sun, 25 Feb 2007 11:58:23 +0200 Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
> Avi Kivity wrote:
> >
> > The patchset, along with the previous fixset, is available as a git
> > tree from git://kvm.qumranet.com/home/avi/kvm/linux-2.6. You may wish
> > to plant it in your little git forest.
> >
>
> This is now git://kvm.qumranet.com/home/avi/kvm.git, as a bare 'git
> pull' will pull the current branch instead of master, giving you
> whatever I was working on at the moment. The kvm.git repo will always
> have 'master' as the current branch.
OK.
drivers/kvm/kvm.h | 13 +
drivers/kvm/kvm_main.c | 774 ++++++++++++++++++++++++++++++++-------------
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 ++++
However things might get messy later on if that tree starts introducing changes
outside drivers/kvm. There's a ton of activity in x86-world.
But if there are problems, you'll hear about it ;)
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-02-25 11:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 18:11 [PATCH 0/6] KVM userspace interface updates for 2.6.21 Avi Kivity
[not found] ` <45DC8B6E.5050205-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-21 18:13 ` [PATCH 1/6] KVM: Add internal filesystem for generating inodes Avi Kivity
2007-02-21 18:14 ` [PATCH 2/6] KVM: Create an inode per virtual machine 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:16 ` [PATCH 4/6] KVM: Move kvm_vm_ioctl_create_vcpu() around Avi Kivity
2007-02-21 18:17 ` [PATCH 5/6] KVM: Per-vcpu inodes Avi Kivity
2007-02-21 18:18 ` [PATCH 6/6] KVM: Bump API version Avi Kivity
2007-02-21 18:21 ` [PATCH 0/6] KVM userspace interface updates for 2.6.21 Avi Kivity
[not found] ` <45DC8D97.9060408-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-21 19:08 ` Rusty Russell
2007-02-25 9:58 ` Avi Kivity
[not found] ` <45E15DBF.8000106-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-25 11:47 ` Andrew Morton [this message]
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=20070225034737.16353a46.akpm@linux-foundation.org \
--to=akpm-de/tnxtf+jlsfhdxvbkv3wd2fqjk+8+b@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox