From: Chris Wright <chrisw@sous-sol.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: paravirt repo rebased to 2.6.21-rc6-mm1
Date: Tue, 10 Apr 2007 17:10:18 -0700 [thread overview]
Message-ID: <20070411001018.GV10574@sequoia.sous-sol.org> (raw)
In-Reply-To: <461C1DDB.4090307@vmware.com>
* Zachary Amsden (zach@vmware.com) wrote:
> Jeremy Fitzhardinge wrote:
> >Seems to work OK for native and Xen. I had to play a bit with the
> >paravirt-sched-clock patch to deal with the VMI changes. Zach, can you
> >check that it still works?
>
> I'm on it.
Not sure about cycles_2_ns...
arch/i386/kernel/built-in.o: In function `activate_vmi':
/home/chrisw/hg/xen/linux-2.6-pv/arch/i386/kernel/vmi.c:894: undefined reference to `vmi_sched_clock'
diff -r a5e50a2e914a arch/i386/kernel/vmiclock.c
--- a/arch/i386/kernel/vmiclock.c Tue Apr 10 16:20:13 2007 -0700
+++ b/arch/i386/kernel/vmiclock.c Tue Apr 10 17:07:47 2007 -0700
@@ -64,10 +64,10 @@ int vmi_set_wallclock(unsigned long now)
return 0;
}
-/* paravirt_ops.get_scheduled_cycles = vmi_get_sched_cycles */
-unsigned long long vmi_get_sched_cycles(void)
-{
- return vmi_timer_ops.get_cycle_counter(VMI_CYCLES_AVAILABLE);
+unsigned long long vmi_sched_clock(void)
+{
+ cycle_t cycles = vmi_timer_ops.get_cycle_counter(VMI_CYCLES_AVAILABLE);
+ return cycles_2_ns(cycles);
}
/* paravirt_ops.get_cpu_khz = vmi_cpu_khz */
next prev parent reply other threads:[~2007-04-11 0:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 23:23 paravirt repo rebased to 2.6.21-rc6-mm1 Jeremy Fitzhardinge
2007-04-10 23:29 ` Zachary Amsden
2007-04-11 0:10 ` Chris Wright [this message]
2007-04-10 23:29 ` Zachary Amsden
2007-04-10 23:48 ` Chris Wright
2007-04-12 8:54 ` Chris Wright
2007-04-12 15:40 ` Zachary Amsden
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=20070411001018.GV10574@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.com \
/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;
as well as URLs for NNTP newsgroup(s).