Hi Jan,
On 21/11/2019 10:41, Jan Beulich wrote:
On 21.11.2019 11:07, Julien Grall wrote:
On 21/11/2019 09:04, Jan Beulich wrote:
On 20.11.2019 21:22, Julien Grall wrote:
On 14/11/2019 16:43, Jan Beulich wrote:
TBD: Does Arm actually have anything to check against in its
On 21.11.2019 11:07, Julien Grall wrote:
>
>
> On 21/11/2019 09:04, Jan Beulich wrote:
>> On 20.11.2019 21:22, Julien Grall wrote:
>>> On 14/11/2019 16:43, Jan Beulich wrote:
TBD: Does Arm actually have anything to check against in its
arch_notify_gfn()?
>>>
>>> I understand
On 21/11/2019 09:04, Jan Beulich wrote:
On 20.11.2019 21:22, Julien Grall wrote:
On 14/11/2019 16:43, Jan Beulich wrote:
In order for individual IOMMU drivers (and from an abstract pov also
architectures) to be able to adjust, ahead of actual mapping requests,
their data structures when they
On 20.11.2019 21:22, Julien Grall wrote:
> On 14/11/2019 16:43, Jan Beulich wrote:
>> In order for individual IOMMU drivers (and from an abstract pov also
>> architectures) to be able to adjust, ahead of actual mapping requests,
>> their data structures when they might cover only a sub-range of
Hi Jan,
On 14/11/2019 16:43, Jan Beulich wrote:
In order for individual IOMMU drivers (and from an abstract pov also
architectures) to be able to adjust, ahead of actual mapping requests,
their data structures when they might cover only a sub-range of all
possible GFNs, introduce a notification
In order for individual IOMMU drivers (and from an abstract pov also
architectures) to be able to adjust, ahead of actual mapping requests,
their data structures when they might cover only a sub-range of all
possible GFNs, introduce a notification call used by various code paths
potentially
