From: Jan Kiszka <jan.kiszka@siemens.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
"Gabriel L. Somlo" <gsomlo@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: kvm-kmod and kernels 3.11.*
Date: Fri, 13 Dec 2013 16:04:18 +0100 [thread overview]
Message-ID: <52AB21F2.1030005@siemens.com> (raw)
In-Reply-To: <52AA31A8.4010806@redhat.com>
On 2013-12-12 22:59, Paolo Bonzini wrote:
> Il 12/12/2013 22:27, Gabriel L. Somlo ha scritto:
>> I tried copying and/or cut'n'pasting from additional source files in
>> the current kvm git tree, but haven't totally figured out how the magic
>> of "make sync" works yet :) Do you have any notes or any other
>> documentation one could use to be able to usefully hack on kvm-kmod
>> when it starts lagging behind the latest kvm master branch ?
>
> You need to "hack" the ./sync script to generate the appropriate
> #ifdefs.
>
> It looks like the code to support newer releases is currently in the
> next branch of kvm-kmod.git.
Yes, kvm-kmod is starting to bitrot. I just noticed I messed up the last
stable release back in August, and no one seems to have noticed it.
There were no complains about the missing releases for 3.11 and 3.12, so
it the relevance must have dropped significantly.
kvm-kmod is still useful for hacking, so I'm considering to stop
providing releases (except for a final 3.10.21), just updates in git to
allow wrapping of latest kvm head on recent kernels. There are breakages
with kernels < 3.0 now, about which I personally do not care anymore, so
lifting the entrance level to 3.0 seems reasonable.
>
> For completeness, here is the patch I am using right now.
Is there anything in your patch that is still required with current
kvm-kmod next? Then I would be happy about a patch!
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-12-13 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 21:27 kvm-kmod and kernels 3.11.* Gabriel L. Somlo
2013-12-12 21:59 ` Paolo Bonzini
2013-12-13 15:04 ` Jan Kiszka [this message]
2013-12-13 15:12 ` Paolo Bonzini
2013-12-13 15:36 ` Jan Kiszka
2013-12-13 16:19 ` Gabriel L. Somlo
2013-12-13 16:24 ` Paolo Bonzini
2013-12-13 16:26 ` Jan Kiszka
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=52AB21F2.1030005@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gsomlo@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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