From: Zachary Amsden <zach@vmware.com>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
ak@suse.de, chrisw@sous-sol.org, jeremy@xensource.com,
rusty@rustcorp.com.au
Subject: Re: + paravirt-vmi-timer-patches.patch added to -mm tree
Date: Sat, 06 Jan 2007 12:52:27 -0800 [thread overview]
Message-ID: <45A00C0B.90901@vmware.com> (raw)
In-Reply-To: <1168102492.26086.215.camel@imap.mvista.com>
Daniel Walker wrote:
> On Fri, 2006-12-15 at 14:27 -0800, akpm@osdl.org wrote:
>
>> +
>> +unsigned long long vmi_sched_clock(void)
>> +{
>> + return read_available_cycles();
>> +}
>> +
>>
>
>
> This sched_clock is likely broken if it's returning something other than
> nanoseconds. It looks like cycles, but it's also getting piped through
> an ops pointer so I'm not sure what's getting returned here.
>
Thanks, I'll fix that.
Zach
next prev parent reply other threads:[~2007-01-06 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200612152227.kBFMRNuQ002977@shell0.pdx.osdl.net>
2007-01-06 16:54 ` + paravirt-vmi-timer-patches.patch added to -mm tree Daniel Walker
2007-01-06 20:52 ` Zachary Amsden [this message]
2007-01-06 18:06 ` Daniel Walker
2007-01-06 20:37 ` Zachary Amsden
2007-01-06 20:40 ` Daniel Walker
2007-01-06 20:51 ` 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=45A00C0B.90901@vmware.com \
--to=zach@vmware.com \
--cc=ak@suse.de \
--cc=chrisw@sous-sol.org \
--cc=dwalker@mvista.com \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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