On 08/25/2015 05:27 PM, Andre Przywara wrote:
> Hi Eric,
>
> On 14/08/15 12:58, Eric Auger wrote:
>> On 07/10/2015 04:21 PM, Andre Przywara wrote:
>>> The LPI configuration and pending tables of the GICv3 LPIs are held
>>> in tables in (guest) memory. To achieve reasonable performance, we
>>>
On 08/25/2015 05:47 PM, Andre Przywara wrote:
> Hi Eric,
>
> On 14/08/15 13:35, Eric Auger wrote:
>> On 08/14/2015 01:58 PM, Eric Auger wrote:
>>> On 07/10/2015 04:21 PM, Andre Przywara wrote:
The LPI configuration and pending tables of the GICv3 LPIs are held
in tables in (guest)
Hi Eric,
On 14/08/15 12:58, Eric Auger wrote:
On 07/10/2015 04:21 PM, Andre Przywara wrote:
The LPI configuration and pending tables of the GICv3 LPIs are held
in tables in (guest) memory. To achieve reasonable performance, we
cache this data in our own data structures, so we need to sync
Hi Eric,
On 14/08/15 13:35, Eric Auger wrote:
On 08/14/2015 01:58 PM, Eric Auger wrote:
On 07/10/2015 04:21 PM, Andre Przywara wrote:
The LPI configuration and pending tables of the GICv3 LPIs are held
in tables in (guest) memory. To achieve reasonable performance, we
cache this data in our
On 07/10/2015 04:21 PM, Andre Przywara wrote:
The LPI configuration and pending tables of the GICv3 LPIs are held
in tables in (guest) memory. To achieve reasonable performance, we
cache this data in our own data structures, so we need to sync those
two views from time to time. This behaviour
On 08/14/2015 01:58 PM, Eric Auger wrote:
On 07/10/2015 04:21 PM, Andre Przywara wrote:
The LPI configuration and pending tables of the GICv3 LPIs are held
in tables in (guest) memory. To achieve reasonable performance, we
cache this data in our own data structures, so we need to sync those
The LPI configuration and pending tables of the GICv3 LPIs are held
in tables in (guest) memory. To achieve reasonable performance, we
cache this data in our own data structures, so we need to sync those
two views from time to time. This behaviour is well described in the
GICv3 spec and is also
