Re: [Xen-devel] [PULL 0/4] xen queue 2019-02-28

2019-03-01 Thread Peter Maydell
On Thu, 28 Feb 2019 at 17:34, Anthony PERARD wrote: > > The following changes since commit 711d13d5e2e160c1c3bcbd302af6df3980a99469: > > Merge remote-tracking branch > 'remotes/amarkovic/tags/mips-queue-feb-27-2019' into staging (2019-02-28 > 12:59:49 +) > > are available in the Git

[Xen-devel] [linux-3.18 test] 133464: regressions - FAIL

2019-03-01 Thread osstest service owner
flight 133464 linux-3.18 real [real] http://logs.test-lab.xenproject.org/osstest/logs/133464/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-debianhvm-amd64 7 xen-bootfail REGR. vs. 128858

Re: [Xen-devel] [PATCH for-next] CODING_STYLE: Document how to handle unexpected conditions

2019-03-01 Thread Jan Beulich
>>> George Dunlap 02/28/19 7:50 PM >>> >+GUIDELINES: >+ >+Passing errors up the stack should be used when the caller is already >+expecting to handle errors, and the state when the error was >+discovered isn’t broken, or too hard to fix. >+ >+BUG_ON() should be used when you can’t pass errors up

[Xen-devel] [linux-4.14 test] 133470: regressions - FAIL

2019-03-01 Thread osstest service owner
flight 133470 linux-4.14 real [real] http://logs.test-lab.xenproject.org/osstest/logs/133470/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-libvirt 18 guest-start/debian.repeat fail REGR. vs. 133261

[Xen-devel] [qemu-mainline baseline-only test] 83686: trouble: blocked/broken

2019-03-01 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 83686 qemu-mainline real [real] http://osstest.xensource.com/osstest/logs/83686/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64

[Xen-devel] [linux-linus test] 133474: regressions - FAIL

2019-03-01 Thread osstest service owner
flight 133474 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/133474/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 16 guest-localmigrate/x10 fail REGR. vs. 132911

Re: [Xen-devel] [PATCH v10 6/6] xen: use DEFINE_SYMBOL as required

2019-03-01 Thread Stefano Stabellini
On Wed, 27 Feb 2019, Jan Beulich wrote: > >>> On 26.02.19 at 22:22, wrote: > > On Tue, 26 Feb 2019, Jan Beulich wrote: > >> >>> On 25.02.19 at 21:50, wrote: > >> > @@ -210,7 +210,8 @@ static int __apply_alternatives_multi_stop(void > >> > *unused) > >> > region.begin =

Re: [Xen-devel] [PATCH for-4.12 RFC] xen/console: Handle NUL character in buffer sent via CONSOLEIO_write

2019-03-01 Thread Daniel De Graaf
On 2/27/19 1:45 PM, Julien Grall wrote: Hi Wei, On 2/27/19 12:55 PM, Wei Liu wrote: On Tue, Feb 26, 2019 at 11:03:51PM +, Julien Grall wrote: After upgrading Debian to Buster, I started noticing console mangling when using zsh. This is happenning because output sent by zsh to the console

[Xen-devel] [ovmf test] 133493: all pass - PUSHED

2019-03-01 Thread osstest service owner
flight 133493 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/133493/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf c3947b54235c93e4f41d6d56b1f5296a9f8021d5 baseline version: ovmf

[Xen-devel] [freebsd-master test] 133497: all pass - PUSHED

2019-03-01 Thread osstest service owner
flight 133497 freebsd-master real [real] http://logs.test-lab.xenproject.org/osstest/logs/133497/ Perfect :-) All tests in this flight passed as required version targeted for testing: freebsd bd8ba96fed2d3797e6f4741bff0e4ed82967e23a baseline version: freebsd

Re: [Xen-devel] [BUG linux-4.9.x] xen hotplug cpu leads to 100% steal usage

2019-03-01 Thread Thomas Gleixner
On Thu, 28 Feb 2019, Dongli Zhang wrote: > > The root cause is that the return type of jiffies_to_usecs() is 'unsigned > int', > but not 'unsigned long'. As a result, the leading 32 bits are discarded. Errm. No. The root cause is that jiffies_to_usecs() is used for that in the first place. The

[Xen-devel] [linux-4.4 test] 133468: tolerable FAIL - PUSHED

2019-03-01 Thread osstest service owner
flight 133468 linux-4.4 real [real] http://logs.test-lab.xenproject.org/osstest/logs/133468/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemuu-dmrestrict-amd64-dmrestrict 10 debian-hvm-install fail never pass

[Xen-devel] standalone PCI passthrough emulator

2019-03-01 Thread Paul Durrant
Hi, As the basis of some future development work I've put together a simple standalone emulator to pass through a single type 0 PCI function to a guest so I'm posting here in case anyone else would like a give it a try. So far I've tested with AMD FirePro S7150 and NVIDIA K1 GPUs and a

Re: [Xen-devel] standalone PCI passthrough emulator

2019-03-01 Thread Paul Durrant
> -Original Message- > From: Paul Durrant > Sent: 01 March 2019 16:41 > To: xen-devel (xen-devel@lists.xenproject.org) > > Subject: standalone PCI passthrough emulator > > Hi, > > As the basis of some future development work I've put together a simple > standalone emulator to pass >

Re: [Xen-devel] [PATCH for-next] CODING_STYLE: Document how to handle unexpected conditions

2019-03-01 Thread Wei Liu
On Thu, Feb 28, 2019 at 06:49:05PM +, George Dunlap wrote: > It's not always clear what the best way is to handle unexpected > conditions: whether with ASSERT(), BUG_ON(), or some other method. > All methods have a risk of introducing security vulnerabilities and > unnecessary instabilities to

Re: [Xen-devel] [PATCH for-next] CODING_STYLE: Document how to handle unexpected conditions

2019-03-01 Thread George Dunlap
On 3/1/19 5:14 PM, Wei Liu wrote: > On Thu, Feb 28, 2019 at 06:49:05PM +, George Dunlap wrote: >> It's not always clear what the best way is to handle unexpected >> conditions: whether with ASSERT(), BUG_ON(), or some other method. >> All methods have a risk of introducing security

Re: [Xen-devel] [PATCH for-next] CODING_STYLE: Document how to handle unexpected conditions

2019-03-01 Thread George Dunlap
On 3/1/19 5:12 PM, Jan Beulich wrote: George Dunlap 02/28/19 7:50 PM >>> >> +GUIDELINES: >> + >> +Passing errors up the stack should be used when the caller is already >> +expecting to handle errors, and the state when the error was >> +discovered isn’t broken, or too hard to fix. >> + >>

[Xen-devel] [xen-unstable test] 133489: regressions - FAIL

2019-03-01 Thread osstest service owner
flight 133489 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/133489/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 7 xen-boot fail REGR. vs. 133300 Tests

[Xen-devel] [ovmf baseline-only test] 83688: trouble: blocked/broken

2019-03-01 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 83688 ovmf real [real] http://osstest.xensource.com/osstest/logs/83688/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm

[Xen-devel] [libvirt test] 133488: regressions - FAIL

2019-03-01 Thread osstest service owner
flight 133488 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/133488/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-libvirt6 libvirt-buildfail REGR. vs. 133460 Tests which did not

[Xen-devel] [xen-4.10-testing test] 133487: tolerable FAIL - PUSHED

2019-03-01 Thread osstest service owner
flight 133487 xen-4.10-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/133487/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-i386-xl-qemut-ws16-amd64 17 guest-stop fail like 132966

Re: [Xen-devel] [PATCH for-4.12] tools/tests: Drop obsolete test infrastructure

2019-03-01 Thread Juergen Gross
On 25/02/2019 14:16, Andrew Cooper wrote: > The regression/ directory was identified as already broken in 2012 (c/s > 953953cc5). The logic is intended to test *.py files in the Xen tree against > different versions of python, but every identified version is now obsolete. > > Signed-off-by:

[Xen-devel] [ovmf baseline-only test] 83684: trouble: blocked/broken

2019-03-01 Thread Platform Team regression test user
This run is configured for baseline tests only. flight 83684 ovmf real [real] http://osstest.xensource.com/osstest/logs/83684/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm

[Xen-devel] [xen-unstable-smoke test] 133498: tolerable all pass - PUSHED

2019-03-01 Thread osstest service owner
flight 133498 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/133498/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass test-arm64-arm64-xl-xsm

[Xen-devel] [PATCH] tools/xenstore: Do not abort xenstore-ls if a node disappears while iterating

2019-03-01 Thread David Woodhouse
From: David Woodhouse When recursing, a node sometimes disappears. Deal with it and move on instead of aborting and failing to print the rest of what was requested. Signed-off-by: David Woodhouse --- And thus did an extremely sporadic "not going to delete that device because it already

[Xen-devel] [xen-4.9-testing test] 133466: regressions - FAIL

2019-03-01 Thread osstest service owner
flight 133466 xen-4.9-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/133466/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvopsbroken in 133314

[Xen-devel] [PATCH] Minor security policy text changes to avoid ambiguity

2019-03-01 Thread Lars Kurth
See http://xenbits.xen.org/gitweb/?p=people/larsk/governance.git;a=summary for the repository. Signed-off-by: Lars Kurth CC: committ...@xenproject.org --- security-policy.pandoc | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/security-policy.pandoc

Re: [Xen-devel] [PATCH] Minor security policy text changes to avoid ambiguity

2019-03-01 Thread Andrew Cooper
On 01/03/2019 13:55, Lars Kurth wrote: > See http://xenbits.xen.org/gitweb/?p=people/larsk/governance.git;a=summary > for the repository. > > Signed-off-by: Lars Kurth Reviewed-by: Andrew Cooper ___ Xen-devel mailing list

Re: [Xen-devel] [PATCH] Minor security policy text changes to avoid ambiguity

2019-03-01 Thread Ian Jackson
Lars Kurth writes ("[PATCH] Minor security policy text changes to avoid ambiguity"): > See http://xenbits.xen.org/gitweb/?p=people/larsk/governance.git;a=summary > for the repository. I don't think in fact that there was previously any ambiguity. The text in the policy two paragraphs earlier

Re: [Xen-devel] [PATCH] Minor security policy text changes to avoid ambiguity

2019-03-01 Thread George Dunlap
On 3/1/19 1:55 PM, Lars Kurth wrote: > See http://xenbits.xen.org/gitweb/?p=people/larsk/governance.git;a=summary > for the repository. > > Signed-off-by: Lars Kurth > CC: committ...@xenproject.org Acked-by: George Dunlap ___ Xen-devel mailing list

[Xen-devel] [qemu-mainline test] 133467: tolerable FAIL - PUSHED

2019-03-01 Thread osstest service owner
flight 133467 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/133467/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stopfail like 133284 test-armhf-armhf-libvirt 14