On 17 February 2018 at 18:46, Eric Auger <eric.au...@redhat.com> wrote:
> At the moment, the SMMUv3 does not support notification on
> TLB invalidation. So let's abort as soon as such notifier gets
> enabled.
>
> Signed-off-by: Eric Auger <eric.au...@redhat.com>
> ---
> hw/arm/smmuv3.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/hw/arm/smmuv3.c b/hw/arm/smmuv3.c
> index 384393f..5efe933 100644
> --- a/hw/arm/smmuv3.c
> +++ b/hw/arm/smmuv3.c
> @@ -1074,12 +1074,23 @@ static void smmuv3_class_init(ObjectClass *klass,
> void *data)
> dc->realize = smmu_realize;
> }
>
> +static void smmuv3_notify_flag_changed(IOMMUMemoryRegion *iommu,
> + IOMMUNotifierFlag old,
> + IOMMUNotifierFlag new)
> +{
> + if (old == IOMMU_NOTIFIER_NONE) {
> + error_setg(&error_fatal,
> + "SMMUV3: vhost and vfio notifiers not yet supported");
> + }
> +}
Is this triggerable by the guest, or by the user on the command
line, or only by a bug in the board or other QEMU code?
thanks
-- PMM
