> Subject: Re: ARM64 MSIX enabling error
>
> On 08.12.20 06:28, Peng Fan wrote:
> >> Subject: RE: ARM64 MSIX enabling error
> >>
> >>> Subject: Re: ARM64 MSIX enabling error
> >>>
> >>> On 07.12.20 08:46, Peng Fan wrote:
> >>>> Hi,
> >>>>
> >>>> I use MSIX, not INTX in root cell file, but always met the following
> >>>> error.
> >>>> uio_ivshmem: probe of 0001:00:00.0 failed with error -28
> >>>>
> >>>>
> >>>> I am trying virtio ivshmem on my board, but seems virtio ivshmem
> >>>> vi_find_vqs not work with INTX, so I change to MSIX to see how.
> >>>> But met upper error, any suggestions?
> >>>
> >>> MSI-X for virtual devices only works when injecting them into a
> >>> physical PCI bus which is using MSI-X already. Is that the case here?
> >>> If not, you need to debug the INTx case.
> >>
> >> ok. Thanks.
> >>
> >> I could see virtio-ivshmem-console /dev/uio1 shows a few lines log,
> >>
> >> But it responds to input very slow, when I press enter key, it takes
> >> long time to respond.
> >
> > After correct the interrupt number, it responds to enter key fast.
> > But if I not press enter key, the virtio-ivshmem-console /dev/uio1
> > will show nothing. If I press enter key, it will show one line boot log.
> > Press one more time, it will show the other boot log.
> > I need press enter always, then could see the boot log printed out.
> >
>
> Still interrupts issues, I would say. The GIC MMIO resources are not
> accidentally passed through? Does /proc/interrupts report events for the
> virtual device?
ivshm_irq_handler is triggered in the beginning, for several times, but after
that, there is no interrupt triggered from inmate Linux to root Linux.
The inmate Linux is dead loop in
__send_to_port
->
644 while (!virtqueue_get_buf(out_vq, &len)
645 && !virtqueue_is_broken(out_vq))
646 cpu_relax();
If I press enter key in virtio-ivshmem-console /dev/uio1, it could pass the
loop.
But it will run into it again later and not break out.
Regards,
Peng.
>
> Jan
>
> --
> Siemens AG, T RDA IOT
> Corporate Competence Center Embedded Linux
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jailhouse" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups
> .google.com%2Fd%2Fmsgid%2Fjailhouse-dev%2F543a61e2-e521-5c89-0d96-
> 9f06946f0aae%2540siemens.com&data=04%7C01%7Cpeng.fan%40nxp.
> com%7Ceacc771a8b7b4d510a8b08d89b4a2ca4%7C686ea1d3bc2b4c6fa92cd
> 99c5c301635%7C0%7C1%7C637430090157688268%7CUnknown%7CTWFpb
> GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI
> 6Mn0%3D%7C3000&sdata=G%2FBsXHpiIJyCP5xLNegvC%2FF3Sapl27EH
> wCG%2FPNpwaY8%3D&reserved=0.
--
You received this message because you are subscribed to the Google Groups
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jailhouse-dev/DB6PR0402MB27605393AB95974CE4D8944E88CD0%40DB6PR0402MB2760.eurprd04.prod.outlook.com.
