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

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

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

Gerd Hoffmann wrote: > Jeremy Fitzhardinge wrote: > >> Gerd Hoffmann wrote: >> >>> paravirt clock source patches, next round. >>> >>> There is now a pvclock-abi.h file with the structs and some longish >>> comments in it and everybody is switched over to use the stuff in >>> there. >>>

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

Jeremy Fitzhardinge wrote: > Gerd Hoffmann wrote: >> paravirt clock source patches, next round. >> >> There is now a pvclock-abi.h file with the structs and some longish >> comments in it and everybody is switched over to use the stuff in >> there. > > This all looks pretty good. How do you want

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

Jeremy Fitzhardinge wrote: > Gerd Hoffmann wrote: >> paravirt clock source patches, next round. >> >> There is now a pvclock-abi.h file with the structs and some longish >> comments in it and everybody is switched over to use the stuff in >> there. > > This all looks pretty good. How do you want

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

Gerd Hoffmann wrote: > paravirt clock source patches, next round. > > There is now a pvclock-abi.h file with the structs and some longish > comments in it and everybody is switched over to use the stuff in > there. This all looks pretty good. How do you want this to get into the kernel? J __

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

paravirt clock source patches, next round. There is now a pvclock-abi.h file with the structs and some longish comments in it and everybody is switched over to use the stuff in there. cheers, Gerd ___ Virtualization mailing list Virtualization@lists.