[linux-linus test] 166146: regressions - FAIL

2021-11-14 Thread osstest service owner
flight 166146 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/166146/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-pvops 6 kernel-build fail REGR. vs. 165976 test-armhf-armhf-xl

RE: [PATCH 6/6] VT-d: avoid allocating domid_{bit,}map[] when possible

2021-11-14 Thread Tian, Kevin
> From: Jan Beulich > Sent: Friday, November 12, 2021 5:50 PM > > When an IOMMU implements the full 16 bits worth of DID in context > entries, there's no point going through a memory base translation table. > For IOMMUs not using Caching Mode we can simply use the domain IDs > verbatim, while for

RE: [PATCH 5/6] VT-d: introduce helper to convert DID to domid_t

2021-11-14 Thread Tian, Kevin
> From: Jan Beulich > Sent: Friday, November 12, 2021 5:50 PM > > This is in preparation of adding another "translation" method. Take the > combination of the extra validation both previously open-coded have been > doing: Bounds check and bitmap check. But don't propagate the previous > pointless

RE: [PATCH 4/6] VT-d: tidy domid map handling

2021-11-14 Thread Tian, Kevin
> From: Jan Beulich > Sent: Friday, November 12, 2021 5:49 PM > > - Correct struct field type. > - Use unsigned int when that suffices. > - Eliminate a (badly typed) local variable from > context_set_domain_id(). > - Don't use -EFAULT inappropriately. > - Move set_bit() such that it won't be do

RE: [PATCH 3/6] VT-d: don't leak domid mapping on error path

2021-11-14 Thread Tian, Kevin
> From: Jan Beulich > Sent: Friday, November 12, 2021 5:49 PM > > While domain_context_mapping() invokes domain_context_unmap() in a > sub- > case of handling DEV_TYPE_PCI when encountering an error, thus avoiding > a leak, individual calls to domain_context_mapping_one() aren't > similarly cover

RE: [PATCH 2/6] VT-d: split domid map cleanup check into a function

2021-11-14 Thread Tian, Kevin
> From: Jan Beulich > Sent: Friday, November 12, 2021 5:48 PM > > This logic will want invoking from elsewhere. > > Signed-off-by: Jan Beulich Reviewed-by: Kevin Tian > > --- a/xen/drivers/passthrough/vtd/iommu.c > +++ b/xen/drivers/passthrough/vtd/iommu.c > @@ -157,6 +157,51 @@ static void

RE: [PATCH 1/6] VT-d: properly reserve DID 0 for caching mode IOMMUs

2021-11-14 Thread Tian, Kevin
> From: Jan Beulich > Sent: Friday, November 12, 2021 5:48 PM > > Merely setting bit 0 in the bitmap is insufficient, as then Dom0 will > still have DID 0 allocated to it, because of the zero-filling of > domid_map[]. Set slot 0 to DOMID_INVALID to keep DID 0 from getting > used. > > Fixes: b9c2

RE: [PATCH 1/6] VT-d: properly reserve DID 0 for caching mode IOMMUs

2021-11-14 Thread Tian, Kevin
> From: Roger Pau Monné > Sent: Friday, November 12, 2021 8:19 PM > > On Fri, Nov 12, 2021 at 01:07:33PM +0100, Jan Beulich wrote: > > On 12.11.2021 12:23, Roger Pau Monné wrote: > > > On Fri, Nov 12, 2021 at 10:47:59AM +0100, Jan Beulich wrote: > > >> Merely setting bit 0 in the bitmap is insuff

[PATCH] drm/xen: fix potential memleak in error branch

2021-11-14 Thread Bernard Zhao
In function xen_drm_front_gem_import_sg_table, if in error branch, there maybe potential memleak if not call gem_free_pages_array. Signed-off-by: Bernard Zhao --- drivers/gpu/drm/xen/xen_drm_front_gem.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/x

RE: [PATCH] VT-d: prune super-page related capability macros

2021-11-14 Thread Tian, Kevin
> From: Jan Beulich > Sent: Friday, November 12, 2021 5:51 PM > > cap_super_page_val() and cap_super_offset() are unused (apart from the > latter using the former). I don't see how cap_super_offset() can be > useful in its current shape: cap_super_page_val()'s result is not an > lvalue and hence

[linux-linus test] 166144: regressions - FAIL

2021-11-14 Thread osstest service owner
flight 166144 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/166144/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-pvops 6 kernel-build fail REGR. vs. 165976 test-armhf-armhf-xl

[xen-unstable test] 166142: tolerable FAIL

2021-11-14 Thread osstest service owner
flight 166142 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/166142/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-i386-xl-qemut-debianhvm-i386-xsm 12 debian-hvm-install fail in 166135 pass in 166142 test-amd64-i38

[libvirt test] 166143: regressions - FAIL

2021-11-14 Thread osstest service owner
flight 166143 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/166143/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 151777 build-arm64-libvirt

[xen-unstable-coverity test] 166145: all pass - PUSHED

2021-11-14 Thread osstest service owner
flight 166145 xen-unstable-coverity real [real] http://logs.test-lab.xenproject.org/osstest/logs/166145/ Perfect :-) All tests in this flight passed as required version targeted for testing: xen c7a7f14b92991e7d79735bff95f04676b9af34c6 baseline version: xen 9d9c

[linux-linus test] 166141: regressions - FAIL

2021-11-14 Thread osstest service owner
flight 166141 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/166141/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-pvops 6 kernel-build fail REGR. vs. 165976 test-armhf-armhf-xl