On 2018-04-09 18:51, Giovani Gracioli wrote:
> Hello,
> I would like to send an IPI from the root cell (Linux) to an inmate cell on 
> arm64. I know Jailhouse isolates the physical cores and would not allow to 
> send an IPI to a CPU that does not belong to the cell. However, I would like 
> to test that anyway. 
> I have a kernel module (Linux running on the root cell) that sends an IPI to 
> a core. As I do not have a deep knowledge in Jailhouse, it is not clear to me 
> how Jailhouse intercepts or/and avoids the IPI, when it is sent to a core 
> that does not belong to the root cell.
> Where in the code Jailhouse checks this? What should I change to allow the 
> IPI to be sent?
> On the inmate side, I am running the gic-demo.c and I am just printing the 
> irqn in the handle_IRQ function. Will the IPI be delivered to the handle_IRQ 
> function as well?

We do not support direct exchange of IPIs (SGIs on ARM) between cells
but rather model this case via ivshmem devices. That is the official
answer. If there should be some valid hacking reason for actually
messing with the core: gic_handle_sgir_write does the filtering,
specifically the code blow "/* Route to target CPUs in cell */".


Siemens AG, Corporate Technology, CT RDA IOT SES-DE
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 jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to