Re: [PATCH] irqchip/gic-v3-its: Flush GICR caching for a cross node collection move of an irq

On Wed, Dec 20, 2017 at 6:42 PM, Marc Zyngier wrote: > On 20/12/17 09:34, Ganapatrao Kulkarni wrote: >> Hi Marc, >> >> On Wed, Dec 20, 2017 at 2:56 PM, Marc Zyngier wrote: >>> On 20/12/17 09:15, Ganapatrao Kulkarni wrote: When an interrupt is

Re: [PATCH] irqchip/gic-v3-its: Flush GICR caching for a cross node collection move of an irq

On Wed, Dec 20, 2017 at 6:42 PM, Marc Zyngier wrote: > On 20/12/17 09:34, Ganapatrao Kulkarni wrote: >> Hi Marc, >> >> On Wed, Dec 20, 2017 at 2:56 PM, Marc Zyngier wrote: >>> On 20/12/17 09:15, Ganapatrao Kulkarni wrote: When an interrupt is moved, it is possible that an implementation

Re: [PATCH] irqchip/gic-v3-its: Flush GICR caching for a cross node collection move of an irq

On 20/12/17 09:34, Ganapatrao Kulkarni wrote: > Hi Marc, > > On Wed, Dec 20, 2017 at 2:56 PM, Marc Zyngier wrote: >> On 20/12/17 09:15, Ganapatrao Kulkarni wrote: >>> When an interrupt is moved, it is possible that an implementation that >>> supports caching might still

Re: [PATCH] irqchip/gic-v3-its: Flush GICR caching for a cross node collection move of an irq

On 20/12/17 09:34, Ganapatrao Kulkarni wrote: > Hi Marc, > > On Wed, Dec 20, 2017 at 2:56 PM, Marc Zyngier wrote: >> On 20/12/17 09:15, Ganapatrao Kulkarni wrote: >>> When an interrupt is moved, it is possible that an implementation that >>> supports caching might still have cached data for a

Re: [PATCH] irqchip/gic-v3-its: Flush GICR caching for a cross node collection move of an irq

On 20/12/17 09:34, Ganapatrao Kulkarni wrote: > Hi Marc, > > On Wed, Dec 20, 2017 at 2:56 PM, Marc Zyngier wrote: >> On 20/12/17 09:15, Ganapatrao Kulkarni wrote: >>> When an interrupt is moved, it is possible that an implementation that >>> supports caching might still

Re: [PATCH] irqchip/gic-v3-its: Flush GICR caching for a cross node collection move of an irq

On 20/12/17 09:34, Ganapatrao Kulkarni wrote: > Hi Marc, > > On Wed, Dec 20, 2017 at 2:56 PM, Marc Zyngier wrote: >> On 20/12/17 09:15, Ganapatrao Kulkarni wrote: >>> When an interrupt is moved, it is possible that an implementation that >>> supports caching might still have cached data for a

Re: [PATCH] irqchip/gic-v3-its: Flush GICR caching for a cross node collection move of an irq

Hi Marc, On Wed, Dec 20, 2017 at 2:56 PM, Marc Zyngier wrote: > On 20/12/17 09:15, Ganapatrao Kulkarni wrote: >> When an interrupt is moved, it is possible that an implementation that >> supports caching might still have cached data for a previous >> (no longer valid)

Re: [PATCH] irqchip/gic-v3-its: Flush GICR caching for a cross node collection move of an irq

Hi Marc, On Wed, Dec 20, 2017 at 2:56 PM, Marc Zyngier wrote: > On 20/12/17 09:15, Ganapatrao Kulkarni wrote: >> When an interrupt is moved, it is possible that an implementation that >> supports caching might still have cached data for a previous >> (no longer valid) mapping of the interrupt.

Re: [PATCH] irqchip/gic-v3-its: Flush GICR caching for a cross node collection move of an irq

On 20/12/17 09:15, Ganapatrao Kulkarni wrote: > When an interrupt is moved, it is possible that an implementation that > supports caching might still have cached data for a previous > (no longer valid) mapping of the interrupt. In particular, in a distributed > GIC implementation like multi-socket

Re: [PATCH] irqchip/gic-v3-its: Flush GICR caching for a cross node collection move of an irq

On 20/12/17 09:15, Ganapatrao Kulkarni wrote: > When an interrupt is moved, it is possible that an implementation that > supports caching might still have cached data for a previous > (no longer valid) mapping of the interrupt. In particular, in a distributed > GIC implementation like multi-socket

[PATCH] irqchip/gic-v3-its: Flush GICR caching for a cross node collection move of an irq

When an interrupt is moved, it is possible that an implementation that supports caching might still have cached data for a previous (no longer valid) mapping of the interrupt. In particular, in a distributed GIC implementation like multi-socket SoC platfroms. Hence it is necessary to flush cached

[PATCH] irqchip/gic-v3-its: Flush GICR caching for a cross node collection move of an irq

When an interrupt is moved, it is possible that an implementation that supports caching might still have cached data for a previous (no longer valid) mapping of the interrupt. In particular, in a distributed GIC implementation like multi-socket SoC platfroms. Hence it is necessary to flush cached