linux-kernel - Re: [GIT PULL] KVM updates for the 2.6.37 merge window

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 26 Oct 2010 08:55:34 -0700
From:	Alexander Graf <agraf@...e.de>
To:	Avi Kivity <avi@...hat.com>
Cc:	Scott Wood <scottwood@...escale.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	KVM list <kvm@...r.kernel.org>,
	Marcelo Tosatti <mtosatti@...hat.com>
Subject: Re: [GIT PULL] KVM updates for the 2.6.37 merge window


On 25.10.2010, at 09:59, Avi Kivity wrote:

> On 10/25/2010 06:49 PM, Scott Wood wrote:
>> On Sun, 24 Oct 2010 15:29:12 +0200
>> Avi Kivity<avi@...hat.com>  wrote:
>> 
>> >    Linus, the repository and branch
>> >
>> >     git://git.kernel.org/pub/scm/virt/kvm/kvm.git kvm-updates/2.6.37
>> >
>> >  contains the kvm updates for the 2.6.37 merge window.  Major changes
>> >  this time around include powerpc paravirtualization, a virtual tsc
>> >  rework, and exposing npt to the guest for fast nested virtualization.
>> >  Please pull.
>> 
>> How about these patches which are in kvm.git/next but not
>> kvm-updates/2.6.37?
>> 
>> PPC: KVM: Book E doesn't have __end_interrupts.
>> KVM: PPC: e500: Call kvm_vcpu_uninit() before kvmppc_e500_tlb_uninit()
>> KVM: PPC: BookE: fix sleep with interrupts disabled
>> KVM: PPC: BookE: Load the lower half of MSR
>> 
> 
> Alex, if you want them in, please prepare backports for 2.6.36.1.

Why backports for 2.6.36.1 when we're talking about 2.6.27? Most of them fix bugs introduced by the PV framework.


Alex

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/