From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: adeos-main <adeos-main@gna.org>, Philippe Gerum <rpm@xenomai.org>
Subject: Re: [Adeos-main] [PULL] 2.6.38-noarch: Re-add root preemption notifier
Date: Fri, 14 Oct 2011 14:39:21 +0200 [thread overview]
Message-ID: <4E982D79.7040308@domain.hid> (raw)
In-Reply-To: <4E982C40.4040704@domain.hid>
On 2011-10-14 14:34, Gilles Chanteperdrix wrote:
> On 10/14/2011 01:12 PM, Jan Kiszka wrote:
>> The following changes since commit 641d8e87531c6367a6357335378194ea06a23701:
>>
>> ipipe: Prevent unwritable pages after mprotect (2011-07-21 09:51:56 +0200)
>>
>> are available in the git repository at:
>> git://git.kiszka.org/ipipe queues/2.6.38-noarch
>>
>> Jan Kiszka (1):
>> ipipe: Re-add root preemption notifier
>>
>> include/linux/ipipe.h | 35 +++++++++++++++++++++++++++++++++++
>> include/linux/ipipe_base.h | 2 +-
>> kernel/ipipe/core.c | 6 ++++++
>> 3 files changed, 42 insertions(+), 1 deletions(-)
>>
>> ---
>>
>> ipipe: Re-add root preemption notifier
>>
>> Restore the original root preemption notifiers, once added for 2.6.35
>> but then lost again on 2.6.36 merge. Unfortunately, the feature flag was
>> not lost. So it became meaningless and we have to rename it to
>> __IPIPE_FEATURE_ROOTPREEMPT_NOTIFIER.
>
> The I-pipe defines a generic infrastructure for events, why bypassing it?
>
Because
- this is no kernel-to-ipipe event, but an ipipe-to-kernel (kvm) one
- there is no relation to domains here
- there is no relation to a shadow task here (the event is fired over
a pure Linux task)
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-10-14 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 11:12 [Adeos-main] [PULL] 2.6.38-noarch: Re-add root preemption notifier Jan Kiszka
2011-10-14 12:34 ` Gilles Chanteperdrix
2011-10-14 12:39 ` Jan Kiszka [this message]
2011-12-29 23:10 ` Philippe Gerum
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=4E982D79.7040308@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=adeos-main@gna.org \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=rpm@xenomai.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.