[Xen-devel] [RFC 08/16] gic: separate ppi processing

2018-11-28 Thread Andrii Anisov
From: Andrii Anisov PPI are pcpu private, so their processing is not concurrent and do not need pcpu shared flags and correspondent lockings. So avoid odd bits sets, checks and locks. Signed-off-by: Andrii Anisov --- xen/arch/arm/gic.c| 8 ++-- xen/arch/arm/irq.c| 32 +

Re: [Xen-devel] [RFC 08/16] gic: separate ppi processing

2018-12-12 Thread Andrii Anisov
Julien, Sorry for bothering you too much. What about this patch? -- Sincerely, Andrii Anisov. ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel

Re: [Xen-devel] [RFC 08/16] gic: separate ppi processing

2018-12-12 Thread Julien Grall
Hi, On 12/12/2018 12:37, Andrii Anisov wrote: Julien, Sorry for bothering you too much. What about this patch? I haven't answered because I am waiting the numbers. Cheers, -- Julien Grall ___ Xen-devel mailing list Xen-devel@lists.xenproject.org

Re: [Xen-devel] [RFC 08/16] gic: separate ppi processing

2018-12-12 Thread Andrii Anisov
On 12.12.18 14:46, Julien Grall wrote: I haven't answered because I am waiting the numbers. I got it. But TBM will not show effect of this patch. Even the patch breaks TBM's functionality because TBM relies on a phys timer interrupt to be assigned to the domain (go through the spi path). --

Re: [Xen-devel] [RFC 08/16] gic: separate ppi processing

2018-12-12 Thread Julien Grall
Hi, On 12/12/2018 12:52, Andrii Anisov wrote: On 12.12.18 14:46, Julien Grall wrote: I haven't answered because I am waiting the numbers. I got it. But TBM will not show effect of this patch. If TBM does not show effect, then you need a different benchmark. Probably by looking at how the