From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] [PATCH] x86/ipipe: get FPU backup area allocated for all threads
Date: Fri, 04 Oct 2013 11:01:08 +0200 [thread overview]
Message-ID: <524E83D4.8070007@siemens.com> (raw)
In-Reply-To: <fb449ebaab2d4e71a032af35d5a881b6.squirrel@127.0.0.1>
On 2013-10-04 10:53, Gilles Chanteperdrix wrote:
>
> Jan Kiszka wrote:
>>> diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c
>>> index a00bed1..4716eb2 100644
>>> --- a/arch/x86/kernel/process.c
>>> +++ b/arch/x86/kernel/process.c
>>> @@ -73,14 +73,6 @@ int arch_dup_task_struct(struct task_struct *dst,
>>> struct task_struct *src)
>>> if (ret)
>>> return ret;
>>> fpu_copy(dst, src);
>>> - } else {
>>> -#ifdef CONFIG_IPIPE
>>> - /* unconditionally allocate, RT domain may need it */
>>> - memset(&dst->thread.fpu, 0, sizeof(dst->thread.fpu));
>>> - ret = fpu_alloc(&dst->thread.fpu);
>>> - if (ret)
>>> - return ret;
>>> -#endif
>>
>> Why removing the systematic allocation? This is not explained above and
>> seems counterproductive.
>
> Because when we stop deleting the fpu backup area upon exec, no fork ever
> takes place for source thread without an fpu backup area. So, the "else"
> clause never happens, and we can remove it entirely.
OK, please add this to the commit log.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2013-10-04 9:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 19:21 [Xenomai] [PATCH] x86/ipipe: get FPU backup area allocated for all threads Gilles Chanteperdrix
2013-10-04 8:33 ` Jan Kiszka
2013-10-04 8:50 ` Gilles Chanteperdrix
2013-10-04 8:53 ` Jan Kiszka
2013-10-04 8:57 ` Gilles Chanteperdrix
2013-10-04 8:53 ` Gilles Chanteperdrix
2013-10-04 9:01 ` Jan Kiszka [this message]
2013-10-04 20:18 ` Gilles Chanteperdrix
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=524E83D4.8070007@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@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.