From: Andi Kleen <ak@muc.de>
To: Zachary Amsden <zach@vmware.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 2/11] Sched clock paravirt op
Date: 6 Feb 2007 13:32:56 +0100
Date: Tue, 6 Feb 2007 13:32:56 +0100 [thread overview]
Message-ID: <20070206123256.GF47229@muc.de> (raw)
In-Reply-To: <200702060352.l163qeAf000727@zach-dev.vmware.com>
> .write_msr = native_write_msr,
> .read_tsc = native_read_tsc,
> .read_pmc = native_read_pmc,
> + .get_scheduled_cycles = native_read_tsc,
> + .get_cpu_khz = native_calculate_cpu_khz,
> .load_tr_desc = native_load_tr_desc,
Description missing?
Please write at least two paragraphs or more on each new hook
you want to add.
My feeling is that rdtsc should work fine here. If not please explain.
-Andi
next prev parent reply other threads:[~2007-02-06 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 3:52 [PATCH 2/11] Sched clock paravirt op Zachary Amsden
2007-02-06 4:00 ` Zachary Amsden
2007-02-06 12:32 ` Andi Kleen [this message]
2007-02-06 22:47 ` Zachary Amsden
2007-02-06 23:23 ` Jeremy Fitzhardinge
2007-02-06 23:42 ` Zachary Amsden
2007-02-06 23:48 ` Jeremy Fitzhardinge
2007-02-06 23:50 ` 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=20070206123256.GF47229@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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