From: Randy Dunlap <randy.dunlap@oracle.com>
To: Laurent Vivier <Laurent.Vivier@bull.net>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND 2][PATCH 3/4] modify account_system_time() to update guest time in cpustat and task_struct
Date: Mon, 10 Sep 2007 09:13:21 -0700 [thread overview]
Message-ID: <20070910091321.f0c63c34.randy.dunlap@oracle.com> (raw)
In-Reply-To: <46E56A5E.20209@bull.net>
On Mon, 10 Sep 2007 18:01:34 +0200 Laurent Vivier wrote:
> Randy Dunlap wrote:
> > On Mon, 10 Sep 2007 16:12:58 +0200 Laurent Vivier wrote:
> >
> >> [PATCH 3/4] modify account_system_time() to add cputime to cpustat->guest if we
> >> are running a VCPU. We add this cputime to cpustat->user instead of
> >> cpustat->system because this part of KVM code is in fact user code although it
> >> is executed in the kernel. We duplicate VCPU time between guest and user to
> >> allow an unmodified "top(1)" to display correct value. A modified "top(1)" is
> >> able to display good cpu user time and cpu guest time by subtracting cpu guest
> >> time from cpu user time. Update "gtime" in task_struct accordingly.
> >>
> >> Signed-off-by: Laurent Vivier <Laurent.Vivier@bull.net>
> >
> >
> > Hi,
> > Please use kernel-doc notation here:
> > (see Documentation/kernel-doc-nano-HOWTO.txt or source file examples
> > or ask)
> >
> > easy fix:
> >
> > /*
> > + * Account guest cpu time to a process.
> >
> > /**
> > * account_guest_time - Account guest cpu time to a process.
> >
> > + * @p: the process that the cpu time gets accounted to
> > + * @cputime: the cpu time spent in virtual machine since the last update
> > + */
> > +void account_guest_time(struct task_struct *p, cputime_t cputime)
> > +{
>
> thank you for the comment.
>
> But I just made a cut&past of the comment of the function above.
>
> Should I be consistent with the doc or with the source ?
I see. That entire file could use some kernel-doc-ization.
I suppose that lessens the need for you to make such a change.
I'll probably do it some slow night then.
Thanks,
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2007-09-10 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 14:12 Laurent Vivier
2007-09-10 15:53 ` Randy Dunlap
2007-09-10 16:01 ` Laurent Vivier
2007-09-10 16:13 ` Randy Dunlap [this message]
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=20070910091321.f0c63c34.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=Laurent.Vivier@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®