From: Ingo Molnar <mingo@elte.hu>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"hpa@zytor.com" <hpa@zytor.com>,
"markus.t.metzger@gmail.com" <markus.t.metzger@gmail.com>,
"roland@redhat.com" <roland@redhat.com>,
"eranian@googlemail.com" <eranian@googlemail.com>,
"Villacis, Juan" <juan.villacis@intel.com>,
"ak@linux.jf.intel.com" <ak@linux.jf.intel.com>
Subject: Re: [patch 3/21] x86, bts: wait until traced task has been scheduled out
Date: Wed, 1 Apr 2009 14:53:14 +0200 [thread overview]
Message-ID: <20090401125314.GM12966@elte.hu> (raw)
In-Reply-To: <928CFBE8E7CB0040959E56B4EA41A77E926D537D@irsmsx504.ger.corp.intel.com>
* Metzger, Markus T <markus.t.metzger@intel.com> wrote:
> >-----Original Message-----
> >From: Ingo Molnar [mailto:mingo@elte.hu]
> >Sent: Wednesday, April 01, 2009 1:42 PM
> >To: Oleg Nesterov; Peter Zijlstra
>
>
> >* Oleg Nesterov <oleg@redhat.com> wrote:
> >
> >> On 03/31, Markus Metzger wrote:
> >> >
> >> > +static void wait_to_unschedule(struct task_struct *task)
> >> > +{
> >> > + unsigned long nvcsw;
> >> > + unsigned long nivcsw;
> >> > +
> >> > + if (!task)
> >> > + return;
> >> > +
> >> > + if (task == current)
> >> > + return;
> >> > +
> >> > + nvcsw = task->nvcsw;
> >> > + nivcsw = task->nivcsw;
> >> > + for (;;) {
> >> > + if (!task_is_running(task))
> >> > + break;
> >> > + /*
> >> > + * The switch count is incremented before the actual
> >> > + * context switch. We thus wait for two switches to be
> >> > + * sure at least one completed.
> >> > + */
> >> > + if ((task->nvcsw - nvcsw) > 1)
> >> > + break;
> >> > + if ((task->nivcsw - nivcsw) > 1)
> >> > + break;
> >> > +
> >> > + schedule();
> >>
> >> schedule() is a nop here. We can wait unpredictably long...
> >>
> >> Ingo, do have have any ideas to improve this helper?
> >
> >hm, there's a similar looking existing facility:
> >wait_task_inactive(). Have i missed some subtle detail that makes it
> >inappropriate for use here?
>
> wait_task_inactive() waits until the task is no longer
> TASK_RUNNING.
No, that's wrong, wait_task_inactive() waits until the task
deschedules.
Ingo
next prev parent reply other threads:[~2009-04-01 12:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 12:59 Markus Metzger
2009-04-01 0:17 ` Oleg Nesterov
2009-04-01 8:09 ` Metzger, Markus T
2009-04-01 19:04 ` Oleg Nesterov
2009-04-01 19:52 ` Markus Metzger
2009-04-01 11:41 ` Ingo Molnar
2009-04-01 12:43 ` Metzger, Markus T
2009-04-01 12:53 ` Ingo Molnar [this message]
2009-04-01 19:45 ` Oleg Nesterov
2009-04-01 0:26 ` Oleg Nesterov
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=20090401125314.GM12966@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@linux.jf.intel.com \
--cc=eranian@googlemail.com \
--cc=hpa@zytor.com \
--cc=juan.villacis@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@gmail.com \
--cc=markus.t.metzger@intel.com \
--cc=oleg@redhat.com \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome