Re: [PATCH 33/36] doc, xen-command-line: introduce coloring options

On 04.03.2022 18:46, Marco Solieri wrote: > From: Luca Miccio > > Four additional parameters in the Xen command line are used to define > the underlying coloring policy, which is not directly configurable > otherwise. > > Signed-off-by: Luca Miccio > Signed-off-by: Marco Solieri > --- > docs/

Re: [PATCH 28/36] xen/arm: introduce xen_map_text_rw

On 04.03.2022 18:46, Marco Solieri wrote: > From: Luca Miccio > > Introduce two new arm specific functions to temporarily map/unmap the > Xen text read-write (the Xen text is mapped read-only by default by > setup_pagetables): xen_map_text_rw and xen_unmap_text_rw. > > There is only one caller i

Re: [PATCH 18/36] Alloc: introduce page_list_for_each_reverse

On 04.03.2022 18:46, Marco Solieri wrote: > --- a/xen/include/xen/mm.h > +++ b/xen/include/xen/mm.h > @@ -488,6 +488,8 @@ page_list_splice(struct page_list_head *list, struct > page_list_head *head) > list_for_each_entry_safe(pos, tmp, head, list) > # define page_list_for_each_safe_reverse(p

Re: [PATCH 11/36] xen/include: define hypercall parameter for coloring

On 04.03.2022 18:46, Marco Solieri wrote: > --- a/xen/include/public/arch-arm.h > +++ b/xen/include/public/arch-arm.h > @@ -303,6 +303,12 @@ struct vcpu_guest_context { > typedef struct vcpu_guest_context vcpu_guest_context_t; > DEFINE_XEN_GUEST_HANDLE(vcpu_guest_context_t); > > +#define MAX_CO

Re: [PATCH 09/36] xen/arch: add default colors selection function

On 04.03.2022 18:46, Marco Solieri wrote: > From: Luca Miccio > > When cache coloring support is enabled, a color assignment is needed for > every domain. Introduce a function computing a default configuration > with a safe and common value -- the dom0 color selection. > > Do not access directly

Re: [PATCH 07/36] xen/arm: add coloring data to domains

On 04.03.2022 18:46, Marco Solieri wrote: > From: Luca Miccio > > We want to be able to associate an assignment of cache colors to each > domain. Add a configurable-length array containing a set of color > indices in the domain data. > > Signed-off-by: Luca Miccio > Signed-off-by: Marco Solier

[PATCH] x86/xen: Fix kerneldoc warning

Fix the following W=1 kernel warnings: arch/x86/xen/setup.c:725: warning: expecting prototype for machine_specific_memory_setup(). Prototype was for xen_memory_setup() instead. Reported-by: Abaci Robot Signed-off-by: Jiapeng Chong --- arch/x86/xen/setup.c | 2 +- 1 file changed, 1 insertion(+)

[ovmf test] 168451: regressions - FAIL

flight 168451 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/168451/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 168254 build-amd64-xsm

[ovmf test] 168449: regressions - FAIL

flight 168449 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/168449/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 168254 build-amd64-xsm

[linux-linus test] 168442: tolerable FAIL - PUSHED

flight 168442 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/168442/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 168435 test-amd64-amd64-xl-qemuu-ws16-amd64

[ovmf test] 168447: regressions - FAIL

flight 168447 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/168447/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 168254 build-amd64-xsm

RE: Proposal for Porting Xen to Armv8-R64 - DraftA

Hi Stefano, > -Original Message- > From: Xen-devel On Behalf Of Wei > Chen > Sent: 2022年3月3日 10:07 > To: Julien Grall ; [email protected]; Stefano > Stabellini > Cc: Bertrand Marquis ; Penny Zheng > ; Henry Wang ; nd > Subject: RE: Proposal for Porting Xen to Armv8-R64 - Dr

[ovmf test] 168446: regressions - FAIL

flight 168446 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/168446/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 168254 build-amd64-xsm

Re: How to create and start Xen guest VM by qemu-system-x86_64 command line

Hi Alex, Thanks for the response. Actually my target is trying to enable virglrenderer on Xen based Qemu. Before, I have successfully enabled it on KVM based Qemu by the Qemu command line. Such as 'qemu-system-x86_64 *-device virtio-vga-gl* xxx' If change to use xl, I don't know how to set t

[ovmf test] 168445: regressions - FAIL

flight 168445 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/168445/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 168254 build-amd64-xsm

[ovmf test] 168444: regressions - FAIL

flight 168444 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/168444/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 168254 build-amd64-xsm

[ovmf test] 168443: regressions - FAIL

flight 168443 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/168443/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 168254 build-amd64-xsm

[ovmf test] 168441: regressions - FAIL

flight 168441 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/168441/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 168254 build-amd64-xsm

[qemu-mainline test] 168437: tolerable FAIL - PUSHED

flight 168437 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/168437/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemuu-win7-amd64 19 guest-stopfail like 168429 test-armhf-armhf-libvirt 16 sav

[ovmf test] 168440: regressions - FAIL

flight 168440 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/168440/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 168254 build-amd64-xsm

[ovmf test] 168439: regressions - FAIL

flight 168439 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/168439/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 168254 build-amd64-xsm

RE: [PATCH 10/12] swiotlb: add a SWIOTLB_ANY flag to lift the low memory restriction

From: Dongli Zhang Sent: Friday, March 4, 2022 10:28 AM > > Hi Michael, > > On 3/4/22 10:12 AM, Michael Kelley (LINUX) wrote: > > From: Christoph Hellwig Sent: Tuesday, March 1, 2022 2:53 AM > >> > >> Power SVM wants to allocate a swiotlb buffer that is not restricted to low > >> memory for >

[ovmf test] 168438: regressions - FAIL

flight 168438 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/168438/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 168254 build-amd64-xsm

[linux-linus test] 168435: tolerable FAIL - PUSHED

flight 168435 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/168435/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 168423 test-amd64-amd64-xl-qemuu-ws16-amd64

[ovmf test] 168436: regressions - FAIL

flight 168436 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/168436/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 168254 build-amd64-xsm

[qemu-mainline test] 168429: tolerable FAIL - PUSHED

flight 168429 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/168429/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-armhf-armhf-xl-rtds18 guest-start/debian.repeat fail REGR. vs. 168420 Tests which did not succee

[ovmf test] 168433: regressions - FAIL

flight 168433 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/168433/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 168254 build-amd64-xsm

[xen-unstable test] 168428: tolerable FAIL

flight 168428 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/168428/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-amd64-xl-rtds 20 guest-localmigrate/x10 fail pass in 168417 Tests which did not succeed, but

[libvirt test] 168432: regressions - FAIL

flight 168432 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/168432/ 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-armhf-libvirt

[linux-linus test] 168423: tolerable FAIL - PUSHED

flight 168423 linux-linus real [real] flight 168434 linux-linus real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/168423/ http://logs.test-lab.xenproject.org/osstest/logs/168434/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-armhf-