From: Avi Kivity <avi@qumranet.com>
To: David Brown <dmlb2000@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] [GIT PULL] KVM fix for 2.6.22
Date: Sat, 16 Jun 2007 10:47:26 +0300 [thread overview]
Message-ID: <4673958E.7090707@qumranet.com> (raw)
In-Reply-To: <9c21eeae0706150736o6c581222oca883161e8062ed2@mail.gmail.com>
David Brown wrote:
>
> Yes thank you for the fix Avi. btw what version of kvm is in 2.6.22?
> the kvm wiki doesn't say.
>
It's somewhere between kvm-21 and kvm-22. Any recent version of the
userspace can be used to drive it (i.e. starting with 2.6.22, there is
no need to match kernel and userspace versions).
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2007-06-16 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 9:43 [GIT PULL] KVM fix for 2.6.22 Avi Kivity
2007-06-15 14:36 ` [kvm-devel] " David Brown
2007-06-16 7:47 ` Avi Kivity [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=4673958E.7090707@qumranet.com \
--to=avi@qumranet.com \
--cc=dmlb2000@gmail.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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