This is the only new patch, the rest was still sitting in the
send-email directory ... sorry for the spam.
Henning
Am Fri, 14 Sep 2018 18:14:38 +0200
schrieb Henning Schild :
> This adds all build output to .gitignore. Not everybody works out of
> tree, or knows that this option exists. So let
Upstream 4.14 switched to purely eager fpu switching. That was
backported to 4.4 and 4.9. This commit makes cobalt able to deal whith
the changed kernel behaviour.
This commit takes care of 4.9 to begin with.
Introduce IPIPE_X86_FPU_EAGER to switch between the new and the old
implementations. The
Linux 4.14 dropped support for lazy fpu switching and in the 4.4 and 4.9
series similar changes where backported.
So fpu is eager for those versions. That simplifies things a lot and we can
drop several changes from the IPIPE patch.
On the Xenomai side the only thing we still have to care about is
4.14 is always eager, unfortunately we will need a few ifdefs inside the
eager fpu support as well.
Signed-off-by: Henning Schild
---
.../arch/x86/include/asm/xenomai/wrappers.h | 4
kernel/cobalt/arch/x86/thread.c | 21 ++-
2 files changed, 24
This adds all build output to .gitignore. Not everybody works out of
tree, or knows that this option exists. So let us add all build output
to .gitignore. While this names all our binaries and has the risk of
getting out of sync, it at least makes "git status" human readable again.
Signed-off-by:
Linux 4.4.138 switched to eager fpu, set IPIPE_X86_FPU_EAGER
accordingly.
Signed-off-by: Henning Schild
---
kernel/cobalt/arch/x86/include/asm/xenomai/wrappers.h | 4
1 file changed, 4 insertions(+)
diff --git a/kernel/cobalt/arch/x86/include/asm/xenomai/wrappers.h
>>> Norbert, I have followed your emails and your project. You did a good job,
>>> but I don't agree with your approach. My points are:
>>>
>>> - You are trying to convert Xenomai a CMake project and this probably will
>>> not happen because Upstream is very happy with the autotools. I don't
All three kernels are tested now. I addressed comments from the first
review. Unfortunately i did not find a nice split to reduce the ifdef
hell we are in here.
I guess once we drop lazy fpu, most of it will go away.
Henning
Am Fri, 14 Sep 2018 17:10:18 +0200
schrieb Henning Schild :
> 4.14 is
Change to v1:
removed whitespace changes and changed commit message
Am Fri, 14 Sep 2018 17:10:15 +0200
schrieb Henning Schild :
> Linux 4.14 dropped support for lazy fpu switching and in the 4.4 and
> 4.9 series similar changes where backported.
> So fpu is eager for those versions. That
Linux 4.4.138 switched to eager fpu, set IPIPE_X86_FPU_EAGER
accordingly.
Signed-off-by: Henning Schild
---
kernel/cobalt/arch/x86/include/asm/xenomai/wrappers.h | 4
1 file changed, 4 insertions(+)
diff --git a/kernel/cobalt/arch/x86/include/asm/xenomai/wrappers.h
Signed-off-by: Henning Schild
---
kernel/cobalt/include/asm-generic/xenomai/syscall.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/kernel/cobalt/include/asm-generic/xenomai/syscall.h
b/kernel/cobalt/include/asm-generic/xenomai/syscall.h
index f11ade8e7..3873fa634 100644
---
4.14 is always eager, unfortunately we will need a few ifdefs inside the
eager fpu support as well.
Signed-off-by: Henning Schild
---
.../arch/x86/include/asm/xenomai/wrappers.h | 4
kernel/cobalt/arch/x86/thread.c | 21 ++-
2 files changed, 24
Linux 4.14 dropped support for lazy fpu switching and in the 4.4 and 4.9
series similar changes where backported.
So fpu is eager for those versions. That simplifies things a lot and we can
drop several changes from the IPIPE patch.
On the Xenomai side the only thing we still have to care about is
Upstream 4.14 switched to purely eager fpu switching. That was
backported to 4.4 and 4.9. This commit makes cobalt able to deal whith
the changed kernel behaviour.
This commit takes care of 4.9 to begin with.
Introduce IPIPE_X86_FPU_EAGER to switch between the new and the old
implementations. The
Am Mon, 27 Aug 2018 18:36:49 +0200
schrieb Jan Kiszka :
> On 2018-08-27 15:33, Henning Schild wrote:
> > Linux 4.14 dropped support for lazy fpu switching and in the 4.4
> > and 4.9 series similar changes where backported.
> > So we can assume that fpu switching is purely eager for those
> >
t; Yes I get that, and I tried the same with FindXenomai. I consider the CMake
> Config approach
> a lot better.
:-)
Cheers,
Leopold
--
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-
A: Because it messes up the order in which people
On 14/09/18 09:45, Per Oberg wrote:
[...]
>
> Being able to use the same code, without patches or a lot of defines
> including other files is a very clean way of debugging your software. I often
> set up Simulations where I use my laptop running or our controller, possibly
> connected to
> So, from my point of view it confirm my suspicious that the wrapper
> mechanism is fragile. I really didn't understand why Xenomai core team
> changed the native API for the POSIX. Although I saw the Jan Kiska
> conference video explaining it, tell me primitive or dump, but I prefer to
> have
>
> So, from my point of view it confirm my suspicious that the wrapper
> mechanism is fragile. I really didn't understand why Xenomai core team
> changed the native API for the POSIX. Although I saw the Jan Kiska
> conference video explaining it, tell me primitive or dump, but I prefer to
> have
>
Le vendredi 14 septembre 2018 à 02:45 -0500, Per Oberg a écrit :
>
> This!
>
> Being able to use the same code, without patches or a lot of defines
> including other files is a very clean way of debugging your software.
> I often set up Simulations where I use my laptop running or our
>
- Den 13 sep 2018, på kl 23:36, Leopold Palomo-Avellaneda l...@alaxarxa.net
skrev:
> Hi,
> El 13/09/18 a les 14:42, Lange Norbert ha escrit:
>> link order is important and goes left-to-right, this seems to include
> > "wrappers",
>> which only wrap symbols that where already encountered
21 matches
Mail list logo
