Re: [PATCH 0/5] paravirt clock source patches, #4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Avi Kivity wrote:     
>>> This all looks pretty good.  How do you want this to get into the 
>>> kernel?
>>>     
>>
>> [ note: fixed up kvm list address: s/-owner// ]
>>
>> Good question.  The kvm patches have dependencies on not-yet merged
>> bits, so they have to go through the kvm queue.  The first two can also
>> go through Ingos x86 tree I guess.
>>
>>   
>
> Alternativey, if Ingo acks, I'll send all five through kvm.git.
>
> Note the kvm specific patches need to be backported as we want them 
> for 2.6.26.  I can do that.
>
> (Ingo: said patches are in 
> http://thread.gmane.org/gmane.comp.emulators.kvm.devel/18149)
>

What's happening with this?  Is it going through x86.git or what?

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/virtualization

[Index of Archives]     [KVM Development]     [Libvirt Development]     [Libvirt Users]     [CentOS Virtualization]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux