On 2020.06.03 14:33:21 +0200, Julian Stecklina wrote: > When a user tries to allocate too many or too big vGPUs and runs out > of graphics memory, the resulting error message is not actionable and > looks like an internal error. > > Change the error message to clearly point out what actions a user can > take to resolve this situation. > > Cc: Thomas Prescher <thomas.prescher@xxxxxxxxxxxxxxxxxxxxx> > Cc: Zhenyu Wang <zhenyuw@xxxxxxxxxxxxxxx> > Signed-off-by: Julian Stecklina <julian.stecklina@xxxxxxxxxxxxxxxxxxxxx> > --- > drivers/gpu/drm/i915/gvt/aperture_gm.c | 9 ++++++--- > 1 file changed, 6 insertions(+), 3 deletions(-) > > diff --git a/drivers/gpu/drm/i915/gvt/aperture_gm.c b/drivers/gpu/drm/i915/gvt/aperture_gm.c > index 0d6d598713082..5c5c8e871dae2 100644 > --- a/drivers/gpu/drm/i915/gvt/aperture_gm.c > +++ b/drivers/gpu/drm/i915/gvt/aperture_gm.c > @@ -69,9 +69,12 @@ static int alloc_gm(struct intel_vgpu *vgpu, bool high_gm) > start, end, flags); > mmio_hw_access_post(gt); > mutex_unlock(>->ggtt->vm.mutex); > - if (ret) > - gvt_err("fail to alloc %s gm space from host\n", > - high_gm ? "high" : "low"); > + if (ret) { > + gvt_err("vgpu%d: failed to allocate %s gm space from host\n", > + vgpu->id, high_gm ? "high" : "low"); > + gvt_err("vgpu%d: destroying vGPUs, decreasing vGPU memory size or increasing GPU aperture size may resolve this\n", > + vgpu->id); Currently we can't decrease vGPU mem size as defined by mdev type, so actually you may try different vGPU type. And aperture size is also handled for supported vGPU mdev types, so assume user should already be awared of that too. I just don't want us to be too chatty. :) > + } > > return ret; > } > -- > 2.26.2 > > _______________________________________________ > intel-gvt-dev mailing list > intel-gvt-dev@xxxxxxxxxxxxxxxxxxxxx > https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev -- Open Source Technology Center, Intel ltd. $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel