From: Ingo Molnar <mingo@elte.hu>
To: Gregory Haskins <ghaskins@novell.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [PATCH 1/2] RT: Preemptible Function-Call-IPI Support
Date: Tue, 31 Jul 2007 11:19:03 +0200 [thread overview]
Message-ID: <20070731091903.GA15822@elte.hu> (raw)
In-Reply-To: <20070730211539.5162.87483.stgit@novell1.haskins.net>
* Gregory Haskins <ghaskins@novell.com> wrote:
> This code allows FUNCTION_CALL IPIs to become preemptible by executing
> them in kthread context instead of interrupt context. They are
> referred to as "Virtual Function Call IPIs" (VFCIPI) because we no
> longer rely on the actual FCIPI facility. Instead we schedule a
> thread to run. This essentially replaces the synchronous FCIPI with
> an async RESCHEDULE IPI.
why do we need this? It's quite complex and brings little extra AFAICS.
See the "schedule_on_each_cpu-enhance.patch" from Peter Ziljstra that
lets a function to be executed on all CPUs. That should be extended
(trivially) to execute a function on another CPU. That's all we need.
Ingo
next prev parent reply other threads:[~2007-07-31 9:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 21:15 [PATCH 0/2] VFCIPI support v2 Gregory Haskins
2007-07-30 21:15 ` [PATCH 1/2] RT: Preemptible Function-Call-IPI Support Gregory Haskins
2007-07-31 9:19 ` Ingo Molnar [this message]
2007-07-31 9:21 ` Ingo Molnar
2007-07-31 9:25 ` Ingo Molnar
2007-07-31 14:26 ` Gregory Haskins
2007-07-31 14:26 ` Gregory Haskins
2007-07-31 20:14 ` Gregory Haskins
2007-07-30 21:15 ` [PATCH 2/2] RT: Add priority inheritance to the VFCIPI facility Gregory Haskins
2007-07-30 21:34 ` [PATCH 0/2] VFCIPI support v2 Daniel Walker
-- strict thread matches above, loose matches on Subject: below --
2007-07-31 11:44 [PATCH 1/2] RT: Preemptible Function-Call-IPI Support Gregory Haskins
2007-07-31 12:11 Gregory Haskins
2007-07-31 14:22 ` Ingo Molnar
2007-07-31 13:24 [PATCH 0/2][RFC] VFCIPI v3 Gregory Haskins
2007-07-31 13:24 ` [PATCH 1/2] RT: Preemptible Function-Call-IPI Support Gregory Haskins
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=20070731091903.GA15822@elte.hu \
--to=mingo@elte.hu \
--cc=ghaskins@novell.com \
--cc=linux-rt-users@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.