All of lore.kernel.org
 help / color / mirror / Atom feed
* [Xenomai] Boot failed on arm64 - xenomai_init --> ipipe_send_ipi
@ 2018-05-16 18:13 Auel, Kendall
  2018-05-16 19:05 ` Greg Gallagher
  2018-05-17  2:13 ` Dmitriy Cherkasov
  0 siblings, 2 replies; 8+ messages in thread
From: Auel, Kendall @ 2018-05-16 18:13 UTC (permalink / raw)
  To: xenomai

I'm trying to build a xenomai-enabled kernel for an arm64 (quad A53 cores). Something is not configured correctly, but I haven't been able to get past a stall during xenomai_init. Any ideas on what I'm doing wrong? Thanks.

[    0.729547] kvm [1]: 8-bit VMID
[    0.732121] kvm [1]: IDMAP page: 40c5e000
[    0.736134] kvm [1]: HYP VA range: 800000000000:ffffffffffff
[    0.742609] kvm [1]: Hyp mode initialized successfully
[    0.747003] kvm [1]: GICv3: no GICV resource entry
[    0.751740] kvm [1]: disabling GICv2 emulation
[    0.756357] kvm [1]: GIC system register CPU interface enabled
[    0.762428] kvm [1]: vgic interrupt IRQ1
[    0.766021] kvm [1]: virtual timer IRQ4
[    0.775341] audit: initializing netlink subsys (disabled)
[    0.777914] audit: type=2000 audit(0.675:1): initialized
[    0.783729] [Xenomai] scheduling class idle registered.
[    0.788506] [Xenomai] scheduling class rt registered.
[   21.795205] INFO: rcu_preempt detected stalls on CPUs/tasks:
[   21.798018]  2-...: (0 ticks this GP) idle=4c9/140000000000000/0 softirq=129/129 fqs=2428
[   21.806295]  (detected by 1, t=5255 jiffies, g=-252, c=-253, q=106)
[   21.812575] Task dump for CPU 2:
[   21.815801] swapper/0       R  running task        0     1      0 0x00000002
[   21.822864] Call trace:
[   21.825315] [<ffff0000080859f4>] __switch_to+0x8c/0xa0
[   21.830456] [<ffff0000084384a8>] gic_raise_softirq+0x58/0x170
[   21.836208] [<ffff00000808dd64>] ipipe_send_ipi+0x24/0x30
[   21.841615] [<ffff000008154f60>] ipipe_critical_enter+0x108/0x1a8
[   21.847719] [<ffff000008156d60>] ipipe_select_timers+0x2d8/0x320
[   21.853736] [<ffff0000091a2440>] xenomai_init+0x158/0x4c4
[   21.859141] [<ffff000008083308>] do_one_initcall+0x38/0x128
[   21.864724] [<ffff000009190d00>] kernel_init_freeable+0x1ac/0x24c
[   21.870828] [<ffff000008c57e40>] kernel_init+0x10/0x100
[   21.876056] [<ffff000008082fe4>] ret_from_fork+0x14/0x30

Thanks,
Kendall Auel, Senior Embedded Software Engineer
3D Systems, 26600 SW Parkway Ave., Suite 300, Dock 61, Wilsonville OR 97070, USA
Tel: +1 503 482 1970   Mobile: +1 503 939 6862   3dsystems.com<http://3dsystems.com/>

[3D-Systems-logo_primary_3-color_light-bkgrd_no-tm]

This e-mail is intended for the exclusive use of the recipients named above and may constitute privileged or confidential information or otherwise be protected from disclosure. Dissemination, distribution, forwarding or copying of this e-mail by anyone other than the intended recipients is prohibited. If you have received this e-mail in error, please notify me immediately by reply e-mail or telephone and completely delete or destroy any and all electronic or other copies of the original message and any attachments to it. Thank you.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 10651 bytes
Desc: image001.png
URL: <http://xenomai.org/pipermail/xenomai/attachments/20180516/92c0d749/attachment.png>

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] Boot failed on arm64 - xenomai_init --> ipipe_send_ipi
  2018-05-16 18:13 [Xenomai] Boot failed on arm64 - xenomai_init --> ipipe_send_ipi Auel, Kendall
@ 2018-05-16 19:05 ` Greg Gallagher
  2018-05-16 20:00   ` Auel, Kendall
  2018-05-17  2:13 ` Dmitriy Cherkasov
  1 sibling, 1 reply; 8+ messages in thread
From: Greg Gallagher @ 2018-05-16 19:05 UTC (permalink / raw)
  To: Auel, Kendall; +Cc: xenomai

HI,
  What ipipe and kernel version are you using and what Xenomai branch
are you using?

-Greg

On Wed, May 16, 2018 at 2:13 PM, Auel, Kendall
<Kendall.Auel@3dsystems.com> wrote:
> I'm trying to build a xenomai-enabled kernel for an arm64 (quad A53 cores). Something is not configured correctly, but I haven't been able to get past a stall during xenomai_init. Any ideas on what I'm doing wrong? Thanks.
>
> [    0.729547] kvm [1]: 8-bit VMID
> [    0.732121] kvm [1]: IDMAP page: 40c5e000
> [    0.736134] kvm [1]: HYP VA range: 800000000000:ffffffffffff
> [    0.742609] kvm [1]: Hyp mode initialized successfully
> [    0.747003] kvm [1]: GICv3: no GICV resource entry
> [    0.751740] kvm [1]: disabling GICv2 emulation
> [    0.756357] kvm [1]: GIC system register CPU interface enabled
> [    0.762428] kvm [1]: vgic interrupt IRQ1
> [    0.766021] kvm [1]: virtual timer IRQ4
> [    0.775341] audit: initializing netlink subsys (disabled)
> [    0.777914] audit: type=2000 audit(0.675:1): initialized
> [    0.783729] [Xenomai] scheduling class idle registered.
> [    0.788506] [Xenomai] scheduling class rt registered.
> [   21.795205] INFO: rcu_preempt detected stalls on CPUs/tasks:
> [   21.798018]  2-...: (0 ticks this GP) idle=4c9/140000000000000/0 softirq=129/129 fqs=2428
> [   21.806295]  (detected by 1, t=5255 jiffies, g=-252, c=-253, q=106)
> [   21.812575] Task dump for CPU 2:
> [   21.815801] swapper/0       R  running task        0     1      0 0x00000002
> [   21.822864] Call trace:
> [   21.825315] [<ffff0000080859f4>] __switch_to+0x8c/0xa0
> [   21.830456] [<ffff0000084384a8>] gic_raise_softirq+0x58/0x170
> [   21.836208] [<ffff00000808dd64>] ipipe_send_ipi+0x24/0x30
> [   21.841615] [<ffff000008154f60>] ipipe_critical_enter+0x108/0x1a8
> [   21.847719] [<ffff000008156d60>] ipipe_select_timers+0x2d8/0x320
> [   21.853736] [<ffff0000091a2440>] xenomai_init+0x158/0x4c4
> [   21.859141] [<ffff000008083308>] do_one_initcall+0x38/0x128
> [   21.864724] [<ffff000009190d00>] kernel_init_freeable+0x1ac/0x24c
> [   21.870828] [<ffff000008c57e40>] kernel_init+0x10/0x100
> [   21.876056] [<ffff000008082fe4>] ret_from_fork+0x14/0x30
>
> Thanks,
> Kendall Auel, Senior Embedded Software Engineer
> 3D Systems, 26600 SW Parkway Ave., Suite 300, Dock 61, Wilsonville OR 97070, USA
> Tel: +1 503 482 1970   Mobile: +1 503 939 6862   3dsystems.com<http://3dsystems.com/>
>
> [3D-Systems-logo_primary_3-color_light-bkgrd_no-tm]
>
> This e-mail is intended for the exclusive use of the recipients named above and may constitute privileged or confidential information or otherwise be protected from disclosure. Dissemination, distribution, forwarding or copying of this e-mail by anyone other than the intended recipients is prohibited. If you have received this e-mail in error, please notify me immediately by reply e-mail or telephone and completely delete or destroy any and all electronic or other copies of the original message and any attachments to it. Thank you.
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: image001.png
> Type: image/png
> Size: 10651 bytes
> Desc: image001.png
> URL: <http://xenomai.org/pipermail/xenomai/attachments/20180516/92c0d749/attachment.png>
> _______________________________________________
> Xenomai mailing list
> Xenomai@xenomai.org
> https://xenomai.org/mailman/listinfo/xenomai


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] Boot failed on arm64 - xenomai_init --> ipipe_send_ipi
  2018-05-16 19:05 ` Greg Gallagher
@ 2018-05-16 20:00   ` Auel, Kendall
  2018-05-16 20:39     ` Greg Gallagher
  0 siblings, 1 reply; 8+ messages in thread
From: Auel, Kendall @ 2018-05-16 20:00 UTC (permalink / raw)
  To: xenomai

Greg,

The kernel is 4.9.51, modified by NXP for the i.MX8, the Xenomai branch is "next", and the ipipe patch is ipipe-core-4.9.51-arm64-4.patch.

Also, I modified the defconfig to turn off CONFIG_CPU_FREQ and CONFIG_ACPI_PROCESSOR. I've also tried a version with PAGE_MIGRATION disabled and got the same result.

- Kendall

> 
> HI,
>   What ipipe and kernel version are you using and what Xenomai branch are
> you using?
> 
> -Greg
> 
> On Wed, May 16, 2018 at 2:13 PM, Auel, Kendall
> <Kendall.Auel@3dsystems.com> wrote:
> > I'm trying to build a xenomai-enabled kernel for an arm64 (quad A53 cores).
> Something is not configured correctly, but I haven't been able to get past a
> stall during xenomai_init. Any ideas on what I'm doing wrong? Thanks.
> >
> > [    0.729547] kvm [1]: 8-bit VMID
> > [    0.732121] kvm [1]: IDMAP page: 40c5e000
> > [    0.736134] kvm [1]: HYP VA range: 800000000000:ffffffffffff
> > [    0.742609] kvm [1]: Hyp mode initialized successfully
> > [    0.747003] kvm [1]: GICv3: no GICV resource entry
> > [    0.751740] kvm [1]: disabling GICv2 emulation
> > [    0.756357] kvm [1]: GIC system register CPU interface enabled
> > [    0.762428] kvm [1]: vgic interrupt IRQ1
> > [    0.766021] kvm [1]: virtual timer IRQ4
> > [    0.775341] audit: initializing netlink subsys (disabled)
> > [    0.777914] audit: type=2000 audit(0.675:1): initialized
> > [    0.783729] [Xenomai] scheduling class idle registered.
> > [    0.788506] [Xenomai] scheduling class rt registered.
> > [   21.795205] INFO: rcu_preempt detected stalls on CPUs/tasks:
> > [   21.798018]  2-...: (0 ticks this GP) idle=4c9/140000000000000/0
> softirq=129/129 fqs=2428
> > [   21.806295]  (detected by 1, t=5255 jiffies, g=-252, c=-253, q=106)
> > [   21.812575] Task dump for CPU 2:
> > [   21.815801] swapper/0       R  running task        0     1      0 0x00000002
> > [   21.822864] Call trace:
> > [   21.825315] [<ffff0000080859f4>] __switch_to+0x8c/0xa0
> > [   21.830456] [<ffff0000084384a8>] gic_raise_softirq+0x58/0x170
> > [   21.836208] [<ffff00000808dd64>] ipipe_send_ipi+0x24/0x30
> > [   21.841615] [<ffff000008154f60>] ipipe_critical_enter+0x108/0x1a8
> > [   21.847719] [<ffff000008156d60>] ipipe_select_timers+0x2d8/0x320
> > [   21.853736] [<ffff0000091a2440>] xenomai_init+0x158/0x4c4
> > [   21.859141] [<ffff000008083308>] do_one_initcall+0x38/0x128
> > [   21.864724] [<ffff000009190d00>] kernel_init_freeable+0x1ac/0x24c
> > [   21.870828] [<ffff000008c57e40>] kernel_init+0x10/0x100
> > [   21.876056] [<ffff000008082fe4>] ret_from_fork+0x14/0x30
> >
> > Thanks,
> > Kendall Auel, Senior Embedded Software Engineer 3D Systems, 26600 SW
> > Parkway Ave., Suite 300, Dock 61, Wilsonville OR 97070, USA
> > Tel: +1 503 482 1970   Mobile: +1 503 939 6862
> 3dsystems.com<http://3dsystems.com/>
> >
> > [3D-Systems-logo_primary_3-color_light-bkgrd_no-tm]
> >
> > This e-mail is intended for the exclusive use of the recipients named above
> and may constitute privileged or confidential information or otherwise be
> protected from disclosure. Dissemination, distribution, forwarding or copying
> of this e-mail by anyone other than the intended recipients is prohibited. If
> you have received this e-mail in error, please notify me immediately by reply
> e-mail or telephone and completely delete or destroy any and all electronic
> or other copies of the original message and any attachments to it. Thank you.
> >
> > -------------- next part -------------- A non-text attachment was
> > scrubbed...
> > Name: image001.png
> > Type: image/png
> > Size: 10651 bytes
> > Desc: image001.png
> > URL:
> >
> <http://xenomai.org/pipermail/xenomai/attachments/20180516/92c0d749/a
> t
> > tachment.png>
> _______________________________________________
> > Xenomai mailing list
> > Xenomai@xenomai.org
> > https://xenomai.org/mailman/listinfo/xenomai

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] Boot failed on arm64 - xenomai_init --> ipipe_send_ipi
  2018-05-16 20:00   ` Auel, Kendall
@ 2018-05-16 20:39     ` Greg Gallagher
  0 siblings, 0 replies; 8+ messages in thread
From: Greg Gallagher @ 2018-05-16 20:39 UTC (permalink / raw)
  To: Auel, Kendall; +Cc: xenomai

I know Philippe put a change into the arm 32-bit ipipe for the new gic
in the imx7d which was causing a lock up.  I'm not sure if this is a
similar thing.

-Greg

On Wed, May 16, 2018 at 4:00 PM, Auel, Kendall
<Kendall.Auel@3dsystems.com> wrote:
> Greg,
>
> The kernel is 4.9.51, modified by NXP for the i.MX8, the Xenomai branch is "next", and the ipipe patch is ipipe-core-4.9.51-arm64-4.patch.
>
> Also, I modified the defconfig to turn off CONFIG_CPU_FREQ and CONFIG_ACPI_PROCESSOR. I've also tried a version with PAGE_MIGRATION disabled and got the same result.
>
> - Kendall
>
>>
>> HI,
>>   What ipipe and kernel version are you using and what Xenomai branch are
>> you using?
>>
>> -Greg
>>
>> On Wed, May 16, 2018 at 2:13 PM, Auel, Kendall
>> <Kendall.Auel@3dsystems.com> wrote:
>> > I'm trying to build a xenomai-enabled kernel for an arm64 (quad A53 cores).
>> Something is not configured correctly, but I haven't been able to get past a
>> stall during xenomai_init. Any ideas on what I'm doing wrong? Thanks.
>> >
>> > [    0.729547] kvm [1]: 8-bit VMID
>> > [    0.732121] kvm [1]: IDMAP page: 40c5e000
>> > [    0.736134] kvm [1]: HYP VA range: 800000000000:ffffffffffff
>> > [    0.742609] kvm [1]: Hyp mode initialized successfully
>> > [    0.747003] kvm [1]: GICv3: no GICV resource entry
>> > [    0.751740] kvm [1]: disabling GICv2 emulation
>> > [    0.756357] kvm [1]: GIC system register CPU interface enabled
>> > [    0.762428] kvm [1]: vgic interrupt IRQ1
>> > [    0.766021] kvm [1]: virtual timer IRQ4
>> > [    0.775341] audit: initializing netlink subsys (disabled)
>> > [    0.777914] audit: type=2000 audit(0.675:1): initialized
>> > [    0.783729] [Xenomai] scheduling class idle registered.
>> > [    0.788506] [Xenomai] scheduling class rt registered.
>> > [   21.795205] INFO: rcu_preempt detected stalls on CPUs/tasks:
>> > [   21.798018]  2-...: (0 ticks this GP) idle=4c9/140000000000000/0
>> softirq=129/129 fqs=2428
>> > [   21.806295]  (detected by 1, t=5255 jiffies, g=-252, c=-253, q=106)
>> > [   21.812575] Task dump for CPU 2:
>> > [   21.815801] swapper/0       R  running task        0     1      0 0x00000002
>> > [   21.822864] Call trace:
>> > [   21.825315] [<ffff0000080859f4>] __switch_to+0x8c/0xa0
>> > [   21.830456] [<ffff0000084384a8>] gic_raise_softirq+0x58/0x170
>> > [   21.836208] [<ffff00000808dd64>] ipipe_send_ipi+0x24/0x30
>> > [   21.841615] [<ffff000008154f60>] ipipe_critical_enter+0x108/0x1a8
>> > [   21.847719] [<ffff000008156d60>] ipipe_select_timers+0x2d8/0x320
>> > [   21.853736] [<ffff0000091a2440>] xenomai_init+0x158/0x4c4
>> > [   21.859141] [<ffff000008083308>] do_one_initcall+0x38/0x128
>> > [   21.864724] [<ffff000009190d00>] kernel_init_freeable+0x1ac/0x24c
>> > [   21.870828] [<ffff000008c57e40>] kernel_init+0x10/0x100
>> > [   21.876056] [<ffff000008082fe4>] ret_from_fork+0x14/0x30
>> >
>> > Thanks,
>> > Kendall Auel, Senior Embedded Software Engineer 3D Systems, 26600 SW
>> > Parkway Ave., Suite 300, Dock 61, Wilsonville OR 97070, USA
>> > Tel: +1 503 482 1970   Mobile: +1 503 939 6862
>> 3dsystems.com<http://3dsystems.com/>
>> >
>> > [3D-Systems-logo_primary_3-color_light-bkgrd_no-tm]
>> >
>> > This e-mail is intended for the exclusive use of the recipients named above
>> and may constitute privileged or confidential information or otherwise be
>> protected from disclosure. Dissemination, distribution, forwarding or copying
>> of this e-mail by anyone other than the intended recipients is prohibited. If
>> you have received this e-mail in error, please notify me immediately by reply
>> e-mail or telephone and completely delete or destroy any and all electronic
>> or other copies of the original message and any attachments to it. Thank you.
>> >
>> > -------------- next part -------------- A non-text attachment was
>> > scrubbed...
>> > Name: image001.png
>> > Type: image/png
>> > Size: 10651 bytes
>> > Desc: image001.png
>> > URL:
>> >
>> <http://xenomai.org/pipermail/xenomai/attachments/20180516/92c0d749/a
>> t
>> > tachment.png>
>> _______________________________________________
>> > Xenomai mailing list
>> > Xenomai@xenomai.org
>> > https://xenomai.org/mailman/listinfo/xenomai
> _______________________________________________
> Xenomai mailing list
> Xenomai@xenomai.org
> https://xenomai.org/mailman/listinfo/xenomai


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] Boot failed on arm64 - xenomai_init --> ipipe_send_ipi
  2018-05-16 18:13 [Xenomai] Boot failed on arm64 - xenomai_init --> ipipe_send_ipi Auel, Kendall
  2018-05-16 19:05 ` Greg Gallagher
@ 2018-05-17  2:13 ` Dmitriy Cherkasov
  2018-05-17 14:31   ` Lennart Sorensen
  2018-05-18  7:00   ` Jan Kiszka
  1 sibling, 2 replies; 8+ messages in thread
From: Dmitriy Cherkasov @ 2018-05-17  2:13 UTC (permalink / raw)
  To: xenomai

On Wed, May 16, 2018, at 11:13 AM, Auel, Kendall wrote:
> I'm trying to build a xenomai-enabled kernel for an arm64 (quad A53 
> cores). Something is not configured correctly, but I haven't been able 
> to get past a stall during xenomai_init. Any ideas on what I'm doing 
> wrong? Thanks.
> 
> [    0.729547] kvm [1]: 8-bit VMID
> [    0.732121] kvm [1]: IDMAP page: 40c5e000
> [    0.736134] kvm [1]: HYP VA range: 800000000000:ffffffffffff
> [    0.742609] kvm [1]: Hyp mode initialized successfully

I don't think this patch has ever been tested with KVM/HYP mode. I
would try and see if it works in SVC mode on the same hardware.


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] Boot failed on arm64 - xenomai_init --> ipipe_send_ipi
  2018-05-17  2:13 ` Dmitriy Cherkasov
@ 2018-05-17 14:31   ` Lennart Sorensen
  2018-05-18  7:00   ` Jan Kiszka
  1 sibling, 0 replies; 8+ messages in thread
From: Lennart Sorensen @ 2018-05-17 14:31 UTC (permalink / raw)
  To: Dmitriy Cherkasov; +Cc: xenomai

On Wed, May 16, 2018 at 07:13:01PM -0700, Dmitriy Cherkasov wrote:
> On Wed, May 16, 2018, at 11:13 AM, Auel, Kendall wrote:
> > I'm trying to build a xenomai-enabled kernel for an arm64 (quad A53 
> > cores). Something is not configured correctly, but I haven't been able 
> > to get past a stall during xenomai_init. Any ideas on what I'm doing 
> > wrong? Thanks.
> > 
> > [    0.729547] kvm [1]: 8-bit VMID
> > [    0.732121] kvm [1]: IDMAP page: 40c5e000
> > [    0.736134] kvm [1]: HYP VA range: 800000000000:ffffffffffff
> > [    0.742609] kvm [1]: Hyp mode initialized successfully
> 
> I don't think this patch has ever been tested with KVM/HYP mode. I
> would try and see if it works in SVC mode on the same hardware.

32 bit armhf does work with xenomai and HYP.  Never tried 64 bit arm
though.

-- 
Len Sorensen


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] Boot failed on arm64 - xenomai_init --> ipipe_send_ipi
  2018-05-17  2:13 ` Dmitriy Cherkasov
  2018-05-17 14:31   ` Lennart Sorensen
@ 2018-05-18  7:00   ` Jan Kiszka
  2018-05-22  6:26     ` Dmitriy Cherkasov
  1 sibling, 1 reply; 8+ messages in thread
From: Jan Kiszka @ 2018-05-18  7:00 UTC (permalink / raw)
  To: Dmitriy Cherkasov, xenomai

On 2018-05-17 04:13, Dmitriy Cherkasov wrote:
> On Wed, May 16, 2018, at 11:13 AM, Auel, Kendall wrote:
>> I'm trying to build a xenomai-enabled kernel for an arm64 (quad A53 
>> cores). Something is not configured correctly, but I haven't been able 
>> to get past a stall during xenomai_init. Any ideas on what I'm doing 
>> wrong? Thanks.
>>
>> [    0.729547] kvm [1]: 8-bit VMID
>> [    0.732121] kvm [1]: IDMAP page: 40c5e000
>> [    0.736134] kvm [1]: HYP VA range: 800000000000:ffffffffffff
>> [    0.742609] kvm [1]: Hyp mode initialized successfully
> 
> I don't think this patch has ever been tested with KVM/HYP mode. I
> would try and see if it works in SVC mode on the same hardware.
> 

It's unlikely that the presence of KVM is causing issues: Linux just
installs the needed hypervisor stub in EL2 but will continue in EL1 from
then on. Only when actually spawning a VM, that code will come into play
again.

I'm rather concerned to see gic_raise_softirq causing a Linux context
switch. I suppose there is some Linux synchronization mechanism in play,
and the patch lacks related adaptions of that.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [Xenomai] Boot failed on arm64 - xenomai_init --> ipipe_send_ipi
  2018-05-18  7:00   ` Jan Kiszka
@ 2018-05-22  6:26     ` Dmitriy Cherkasov
  0 siblings, 0 replies; 8+ messages in thread
From: Dmitriy Cherkasov @ 2018-05-22  6:26 UTC (permalink / raw)
  To: Jan Kiszka, xenomai, Auel, Kendall

On 05/18/2018 12:00 AM, Jan Kiszka wrote:
> On 2018-05-17 04:13, Dmitriy Cherkasov wrote:
>> On Wed, May 16, 2018, at 11:13 AM, Auel, Kendall wrote:
>>> I'm trying to build a xenomai-enabled kernel for an arm64 (quad A53 
>>> cores). Something is not configured correctly, but I haven't been able 
>>> to get past a stall during xenomai_init. Any ideas on what I'm doing 
>>> wrong? Thanks.
>>>
>>> [    0.729547] kvm [1]: 8-bit VMID
>>> [    0.732121] kvm [1]: IDMAP page: 40c5e000
>>> [    0.736134] kvm [1]: HYP VA range: 800000000000:ffffffffffff
>>> [    0.742609] kvm [1]: Hyp mode initialized successfully
>>
>> I don't think this patch has ever been tested with KVM/HYP mode. I
>> would try and see if it works in SVC mode on the same hardware.
>>
> 
> It's unlikely that the presence of KVM is causing issues: Linux just
> installs the needed hypervisor stub in EL2 but will continue in EL1 from
> then on. Only when actually spawning a VM, that code will come into play
> again.
> 
> I'm rather concerned to see gic_raise_softirq causing a Linux context
> switch. I suppose there is some Linux synchronization mechanism in play,
> and the patch lacks related adaptions of that.
> 
> Jan
> 

Good point. Kendall, did the patch apply cleanly?


^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2018-05-22  6:26 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-05-16 18:13 [Xenomai] Boot failed on arm64 - xenomai_init --> ipipe_send_ipi Auel, Kendall
2018-05-16 19:05 ` Greg Gallagher
2018-05-16 20:00   ` Auel, Kendall
2018-05-16 20:39     ` Greg Gallagher
2018-05-17  2:13 ` Dmitriy Cherkasov
2018-05-17 14:31   ` Lennart Sorensen
2018-05-18  7:00   ` Jan Kiszka
2018-05-22  6:26     ` Dmitriy Cherkasov

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.