public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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 16:46:21 +0200	[thread overview]
Message-ID: <4F8C30BD.2050002@siemens.com> (raw)
In-Reply-To: <CA+tHM2H_gs1ns3Ff2GW3d7FGaqFCCh61PCfqxYi2T+1qucpKyw@mail.gmail.com>

On 2012-04-16 16:34, ya su wrote:
> I first notice 3.3 release notes, it says it can compile against
> 2.6.32-40, so I think it can work with 2.6.32,  then I change it with
> rhel 2.6.32 kernel.

The problem is that the RHEL 2.6.32 kernel has nothing to do with a
standard 2.6.32 as too many features were ported back. So the version
number based feature checks fail as you noticed.

We could adapt kvm-kmod to detect that it is a RHEL kernel (there is
surely some define), but it requires going through all the relevant
features carefully.

> 
> I just re-change orginal kvm-kmod 3.3 with rhel 2.6.32, only to change
> compile redefination errors, but the problem remains the same. the
> patch attached.
> 
> I don't go through git commits, as so many changes from 2.6.32 to 3.3 in kernel.
> 
> I think the problem may come from  memory change notification.

The approach to resolve this could be to identify backported features
based on the build breakage or runtime anomalies, then analyze the
kvm-kmod history for changes that wrapped those features, and finally
adjust all affected code blocks. I'm open for patches and willing to
support you on questions, but I can't work on this myself.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2012-04-16 14:46 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
2012-04-16 14:34       ` ya su
2012-04-16 14:46         ` Jan Kiszka [this message]
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=4F8C30BD.2050002@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