It's a dual core 8th Gen Intel atom.
In the future I will use a quad core atom and probably I will isolate a
core.
I will investigate on ipipe traces. I will let you know, but for me it's OK
anyway.
Il mer 10 apr 2019, 21:36 Jan Kiszka ha scritto:
> On 10.04.19 21:26, cagnulein via Xeno
After 3 days of test (latency + windows 10 with cpu-z and stress test) I
reached rare peaks of 130 us.
For me it's OK but I think there is a small "regression" against the 4.9
Do you need any other test?
R.
Il lun 8 apr 2019, 12:13 Jan Kiszka ha scritto:
> On 08.04.19 11:56, cagnulein wrote:
>
Thank you, on Monday morning I will fire it up! :)
R.
Il ven 5 apr 2019, 20:29 Jan Kiszka ha scritto:
> On 05.04.19 15:27, Jan Kiszka wrote:
> > On 05.04.19 11:42, Jan Kiszka wrote:
> >> On 05.04.19 10:44, cagnulein wrote:
> >>> Hi, yes I double checked the patch and it's applied correctly.
>
I'll give it a shot, I will let you know on Monday.
Thanks and good weekend
R.
Il ven 5 apr 2019, 11:42 Jan Kiszka ha scritto:
> On 05.04.19 10:44, cagnulein wrote:
> > Hi, yes I double checked the patch and it's applied correctly.
> > Here you can find my config.
> >
> >
Hi, yes I double checked the patch and it's applied correctly.
Here you can find my config.
CONFIG_DEBUG_STACKOVERFLOW is disabled.
I can't get the uart on this system, is there any other way to catch log in
this scenario?
Why should I test the 4.4.y? 4.9.146 works fine on the same system (with
Hi Jan, thanks for your patch.
I've just tried but I have the same issue: I start a kvm guest (windows 10
iot 2019) and it works, but when I start a latency test the whole system
hangs completely.
Could i give you more info in some way?
R.
Il gio 4 apr 2019, 21:05 Jan Kiszka ha scritto:
> On
;
> > > I'm already compiling the last git. I will let you know.
> > > Thanks
> > >
> > > Il ven 1 mar 2019, 11:24 Jan Kiszka > <mailto:jan.kis...@siemens.com>
> > > <mailto:jan.kis...@siemens.com <
mailto:cagnul...@gmail.com>> ha scritto:
> >
> > Yes qemu on a xenomai kernel (host device). My guest is a windows 10
> 2019.
> >
> > I'm already compiling the last git. I will let you know.
> > Thanks
> >
> > Il ven 1 mar 2019, 11:24 Jan
>
> Il ven 1 mar 2019, 11:24 Jan Kiszka ha scritto:
>
>> On 01.03.19 10:35, cagnulein via Xenomai wrote:
>> > I’m testing the 4.14.89 ipipe (i was usually using 4.9.146) and i’ve
>> got a
>> > deterministic warning every time i start qemu. Is it alread
Yes qemu on a xenomai kernel (host device). My guest is a windows 10 2019.
I'm already compiling the last git. I will let you know.
Thanks
Il ven 1 mar 2019, 11:24 Jan Kiszka ha scritto:
> On 01.03.19 10:35, cagnulein via Xenomai wrote:
> > I’m testing the 4.14.89 ipipe (i was usua
I’m testing the 4.14.89 ipipe (i was usually using 4.9.146) and i’ve got a
deterministic warning every time i start qemu. Is it already known?
Thanks
R.
Mar 1 01:14:05 debiankvm kernel: [ 96.078798] WARNING: CPU: 0 PID: 1154
at ./arch/x86/include/asm/fpu/internal.h:617
Thank you for the proposal but I don't have more spare time right now. I
hope to help you in the future.
Roberto Viola
Il mar 26 feb 2019, 19:41 Jan Kiszka ha scritto:
> On 26.02.19 17:35, cagnulein via Xenomai wrote:
> > Hi everybody,
> >i would like to give
Hi everybody,
i would like to give my contribution to this incredible project.
In these days i'm working on a Intel Atom E3930 (2 cores 1.3GHz with Turbo
Mode to 1.8GHz) and Xenomai.
Everything working flawless, except the turbo mode.
Infact, in order to enabling the turbo mode, with the
13 matches
Mail list logo
