From: Jan Kiszka <jan.kiszka@siemens.com>
To: ya su <suya94335@gmail.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Has any work 3.3 kvm-kmod for rhel 6.2 kernel successfully?
Date: Mon, 16 Apr 2012 15:10:45 +0200 [thread overview]
Message-ID: <4F8C1A55.8000107@siemens.com> (raw)
In-Reply-To: <CA+tHM2GQEgUgUEJZn7QPjua9ph3KDg3czgwMQCkZXwD39t6-8Q@mail.gmail.com>
On 2012-04-16 14:23, ya su wrote:
> kvm-kmod 3.3 patch attached.
>
> I also change kernel to export __get_user_pages_fast.
Ugh, that's huge. How did you select which feature to enable? Based on
compile tests? The risk would then be to miss some bits that are
additionally required. Or did you step through the git commits to
identify corresponding parts?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-04-16 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 10:12 Has any work 3.3 kvm-kmod for rhel 6.2 kernel successfully? ya su
2012-04-16 10:27 ` Nadav Har'El
2012-04-16 11:08 ` Jan Kiszka
2012-04-16 12:23 ` ya su
2012-04-16 13:10 ` Jan Kiszka [this message]
2012-04-16 14:34 ` ya su
2012-04-16 14:46 ` Jan Kiszka
2012-06-05 4:22 ` ya su
2012-06-05 8:40 ` Jan Kiszka
2012-06-05 15:59 ` Takuya Yoshikawa
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=4F8C1A55.8000107@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=suya94335@gmail.com \
/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