* Re: [PATCH 0/5] paravirt clock source patches, #4 [not found] ` <48454A38.4090907@goop.org> @ 2008-06-03 13:49 ` Gerd Hoffmann 2008-06-04 14:01 ` Avi Kivity 0 siblings, 1 reply; 3+ messages in thread From: Gerd Hoffmann @ 2008-06-03 13:49 UTC (permalink / raw) To: Jeremy Fitzhardinge; +Cc: kvm, virtualization 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 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. cheers, Gerd -- http://kraxel.fedorapeople.org/xenner/ ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 0/5] paravirt clock source patches, #4 2008-06-03 13:49 ` [PATCH 0/5] paravirt clock source patches, #4 Gerd Hoffmann @ 2008-06-04 14:01 ` Avi Kivity 2008-06-16 13:53 ` Avi Kivity 0 siblings, 1 reply; 3+ messages in thread From: Avi Kivity @ 2008-06-04 14:01 UTC (permalink / raw) To: Gerd Hoffmann; +Cc: Jeremy Fitzhardinge, kvm, virtualization, Ingo Molnar 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. >>> >> 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) -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH 0/5] paravirt clock source patches, #4 2008-06-04 14:01 ` Avi Kivity @ 2008-06-16 13:53 ` Avi Kivity 0 siblings, 0 replies; 3+ messages in thread From: Avi Kivity @ 2008-06-16 13:53 UTC (permalink / raw) To: Gerd Hoffmann; +Cc: Jeremy Fitzhardinge, kvm, virtualization, Ingo Molnar 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. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-06-16 13:53 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1212498439-1283-1-git-send-email-kraxel@redhat.com>
[not found] ` <48454A38.4090907@goop.org>
2008-06-03 13:49 ` [PATCH 0/5] paravirt clock source patches, #4 Gerd Hoffmann
2008-06-04 14:01 ` Avi Kivity
2008-06-16 13:53 ` Avi Kivity
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox