public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Gabriel L. Somlo" <gsomlo@gmail.com>, kvm@vger.kernel.org
Subject: Re: kvm-kmod and kernels 3.11.*
Date: Fri, 13 Dec 2013 16:36:07 +0100	[thread overview]
Message-ID: <52AB2967.8000207@siemens.com> (raw)
In-Reply-To: <52AB23DF.2000509@redhat.com>

On 2013-12-13 16:12, Paolo Bonzini wrote:
> Il 13/12/2013 16:04, Jan Kiszka ha scritto:
>> 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.
> 
> I think the relevance of releases is ~zero.  kvm-kmod still remains
> extremely useful IMHO as a hacking tool.

Exactly.

> 
>> 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.
> 
> Yes, git can be good enough for distribution.
> 
>> 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.
> 
> Agreed on this as well.  Personally I would be fine even with only 3-4
> releases backwards compatibility (e.g. 3.8) right now.
> 
>>>> 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!
> 
> Your next branch works for me.  The only difference between my patch and
> your origin/next is that I'm copying
> 
> 	%(linux)s/arch/%(arch)s/include/uapi/asm/msr-index.h'
> 
> and you have
> 
> +
> +#ifndef MSR_IA32_VMX_MISC_PREEMPTION_TIMER_SCALE
> +#define MSR_IA32_VMX_MISC_PREEMPTION_TIMER_SCALE   0x1F
> +#endif

Indeed, will change this.

Thanks!
Jan

> 
> Everything else is roughly the same.  Thanks for maintaining kvm-kmod!
> 
> Paolo
> 


-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2013-12-13 15:36 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
2013-12-13 15:12     ` Paolo Bonzini
2013-12-13 15:36       ` Jan Kiszka [this message]
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=52AB2967.8000207@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