public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	kvm@vger.kernel.org, virtualization@lists.osdl.org,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 0/5] paravirt clock source patches, #4
Date: Wed, 04 Jun 2008 17:01:23 +0300	[thread overview]
Message-ID: <4846A033.7030007@qumranet.com> (raw)
In-Reply-To: <48454BE5.1010007@redhat.com>

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.


  reply	other threads:[~2008-06-04 14:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
2008-06-16 13:53       ` Avi Kivity

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=4846A033.7030007@qumranet.com \
    --to=avi@qumranet.com \
    --cc=jeremy@goop.org \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=virtualization@lists.osdl.org \
    /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