[Xen-devel] [linux-4.1 baseline-only test] 68446: trouble: blocked/broken/fail/pass

This run is configured for baseline tests only. flight 68446 linux-4.1 real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68446/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-armhf-armhf-xl-midway1

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

flight 104633 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/104633/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-armhf-armhf-libvirt-xsm 13 saverestore-support-checkfail like 104611

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

flight 104635 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/104635/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 9d77acf1566fae033ae2dad0ddc8d8565f1c6f4a baseline version: ovmf

[Xen-devel] [xen-unstable test] 104632: regressions - trouble: blocked/broken/fail/pass

flight 104632 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/104632/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-rumprun-amd64 3 host-install(3) broken REGR. vs. 104614

[Xen-devel] [qemu-upstream-4.5-testing baseline-only test] 68445: trouble: broken/fail/pass

This run is configured for baseline tests only. flight 68445 qemu-upstream-4.5-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68445/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-amd64-i386-libvirt-pair

Re: [Xen-devel] [early RFC] ARM PCI Passthrough design document

On 01/24/2017 11:13 PM, Julien Grall wrote: > > > On 19/01/17 05:09, Manish Jaggi wrote: >> Hi Julien, > > Hello Manish, [snip] >> I think, PCI passthrough and DOM0 w/ACPI enumerating devices on PCI are >> separate features. >> Without Xen mapping PCI config space region in stage2 of dom0,

Re: [Xen-devel] [early RFC] ARM PCI Passthrough design document

Hi Julien/Stefano, On 01/24/2017 07:58 PM, Julien Grall wrote: > Hi Stefano, > > On 04/01/17 00:24, Stefano Stabellini wrote: >> On Thu, 29 Dec 2016, Julien Grall wrote: > > [...] > >>> # Introduction >>> >>> PCI passthrough allows to give control of physical PCI devices to guest. >>> This

[Xen-devel] [linux-arm-xen baseline-only test] 68453: tolerable trouble: blocked/broken/pass

This run is configured for baseline tests only. flight 68453 linux-arm-xen real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68453/ Failures :-/ but no regressions. Tests which did not succeed, including tests which could not be run: test-arm64-arm64-libvirt-xsm 1

[Xen-devel] [xen-4.6-testing baseline-only test] 68438: trouble: broken/pass

This run is configured for baseline tests only. flight 68438 xen-4.6-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68438/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-amd64-amd64-libvirt-vhd 2

[Xen-devel] [linux-3.18 baseline-only test] 68448: trouble: blocked/broken/pass

This run is configured for baseline tests only. flight 68448 linux-3.18 real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68448/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-armhf-armhf-xl-midway1

[Xen-devel] [xen-4.0-testing baseline-only test] 68455: tolerable trouble: blocked/broken/pass

This run is configured for baseline tests only. flight 68455 xen-4.0-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68455/ Failures :-/ but no regressions. Tests which did not succeed, including tests which could not be run: test-i386-i386-xl 1

[Xen-devel] [xen-4.4-testing baseline-only test] 68436: trouble: blocked/broken/fail/pass

This run is configured for baseline tests only. flight 68436 xen-4.4-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68436/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-amd64-amd64-rumprun-amd64 1

[Xen-devel] [qemu-upstream-4.6-testing baseline-only test] 68447: trouble: blocked/broken/pass

This run is configured for baseline tests only. flight 68447 qemu-upstream-4.6-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68447/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-armhf-armhf-xl-multivcpu

[Xen-devel] [xen-4.2-testing baseline-only test] 68434: trouble: blocked/broken/fail/pass

This run is configured for baseline tests only. flight 68434 xen-4.2-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68434/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-amd64-amd64-rumprun-amd64 1

[Xen-devel] [xen-unstable baseline-only test] 68439: trouble: blocked/broken/pass

This run is configured for baseline tests only. flight 68439 xen-unstable real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68439/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: build-arm64-libvirt 1

[Xen-devel] [qemu-upstream-unstable baseline-only test] 68441: trouble: blocked/broken/pass

This run is configured for baseline tests only. flight 68441 qemu-upstream-unstable real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68441/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: build-arm64-libvirt 1

[Xen-devel] [linux-3.14 baseline-only test] 68450: trouble: broken/pass

This run is configured for baseline tests only. flight 68450 linux-3.14 real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68450/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-amd64-amd64-libvirt-vhd 2

[Xen-devel] [xen-4.5-testing baseline-only test] 68437: trouble: broken/pass

This run is configured for baseline tests only. flight 68437 xen-4.5-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68437/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-amd64-amd64-rumprun-amd64 2

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

This run is configured for baseline tests only. flight 68440 qemu-mainline real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68440/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: build-arm64-libvirt 1

[Xen-devel] [xen-4.3-testing baseline-only test] 68435: trouble: blocked/broken/fail/pass

This run is configured for baseline tests only. flight 68435 xen-4.3-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68435/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-amd64-amd64-rumprun-amd64 1

[Xen-devel] [linux-3.4 baseline-only test] 68452: trouble: broken/pass

This run is configured for baseline tests only. flight 68452 linux-3.4 real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68452/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-amd64-amd64-xl-qemut-debianhvm-amd64-xsm

[Xen-devel] [xen-4.1-testing baseline-only test] 68433: tolerable trouble: blocked/broken/fail/pass

This run is configured for baseline tests only. flight 68433 xen-4.1-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68433/ Failures :-/ but no regressions. Tests which did not succeed, including tests which could not be run: test-amd64-amd64-rumprun-amd64 1

[Xen-devel] [qemu-upstream-4.4-testing baseline-only test] 68444: trouble: broken/pass

This run is configured for baseline tests only. flight 68444 qemu-upstream-4.4-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68444/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-amd64-amd64-libvirt-pair

[Xen-devel] [qemu-upstream-4.3-testing baseline-only test] 68443: trouble: broken/pass

This run is configured for baseline tests only. flight 68443 qemu-upstream-4.3-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68443/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-amd64-i386-libvirt

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

This run is configured for baseline tests only. flight 68456 ovmf real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68456/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run: test-amd64-amd64-xl-qemuu-ovmf-amd64 1

[Xen-devel] [qemu-upstream-4.2-testing baseline-only test] 68442: trouble: broken/pass

This run is configured for baseline tests only. flight 68442 qemu-upstream-4.2-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68442/ Failures and problems with tests :-( Tests which did not succeed, including tests which could not be run:

Re: [Xen-devel] [PATCH v14 3/3] iommu: add rmrr Xen command line option for extra rmrrs

> From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Tuesday, January 24, 2017 4:47 PM > > >>> On 23.01.17 at 19:20, wrote: > > +overlap = false; > > +list_for_each_entry(rmrru, _rmrr_units, list) > > +{ > > +if (

Re: [Xen-devel] [PATCH v14 1/3] iommu VT-d: separate rmrr addition function.

> From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Tuesday, January 24, 2017 4:34 PM > > >>> On 23.01.17 at 19:20, wrote: > > In preparation for auxiliary RMRR data provided on Xen command line, > > make RMRR adding a separate function. > > Also free memery for

[Xen-devel] [PATCH v2] arm/p2m: Fix regression during domain shutdown with active mem_access

The change in commit 438c5fe4f0c introduced a regression for domains where mem_acces is or was active. When relinquish_p2m_mapping attempts to clear a page where the order is not 0 the following ASSERT is triggered: ASSERT(!p2m->mem_access_enabled || page_order == 0); This regression was

[Xen-devel] [DOC v8] PV Calls protocol design

Changes in v8: - introduce the concept of indexes page - many clarifications - add a diagram - introduce support for multiple versions of the protocol Changes in v7: - add a glossary of Xen terms - add a paragraph on why Xen was chosen - wording improvements - add links to xenstore documents

Re: [Xen-devel] [PATCH] arm/p2m: Fix regression during domain shutdown with active mem_access

On 24/01/2017 23:38, Tamas K Lengyel wrote: > On Tue, Jan 24, 2017 at 4:19 PM, Julien Grall wrote: >> >> On 24/01/2017 22:45, Tamas K Lengyel wrote: >>> On Tue, Jan 24, 2017 at 3:32 PM, Julien Grall >>> wrote: On 24/01/2017 22:19, Tamas

Re: [Xen-devel] [PATCH v2 3/3] xen-platform: add missing disk unplug option

On Tue, 24 Jan 2017, Paul Durrant wrote: > The Xen HVM unplug protocol [1] specifies a mechanism to allow guests to > request unplug of 'aux' disks (which is stated to mean all IDE disks, > except the primary master). This patch adds support for that unplug request. > > NOTE: The semantics of

Re: [Xen-devel] [PATCH v2 1/3] xen-platform: re-structure unplug_disks

On Tue, 24 Jan 2017, Paul Durrant wrote: > The current code is poorly structured and potentially leads to multiple > config space reads when one is sufficient. Also the UNPLUG_ALL_IDE_DISKS > flag is mis-named since it also results in SCSI disks being unplugged. > > This patch renames the flag

Re: [Xen-devel] [PATCH v2 2/3] xen-platform: add support for unplugging NVMe disks...

On Tue, 24 Jan 2017, Paul Durrant wrote: > ...not just IDE and SCSI. > > This patch allows the Xen tool-stack to fully support of NVMe as an > emulated disk type. > > Signed-off-by: Paul Durrant Please update docs/misc/hvm-emulated-unplug.markdown in the Xen repository

Re: [Xen-devel] [PATCH] arm/p2m: Fix regression during domain shutdown with active mem_access

On Tue, Jan 24, 2017 at 4:19 PM, Julien Grall wrote: > > > On 24/01/2017 22:45, Tamas K Lengyel wrote: >> >> On Tue, Jan 24, 2017 at 3:32 PM, Julien Grall >> wrote: >>> >>> >>> >>> On 24/01/2017 22:19, Tamas K Lengyel wrote: On Tue, Jan

[Xen-devel] [qemu-mainline test] 104629: regressions - trouble: blocked/broken/fail/pass

flight 104629 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/104629/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 3 host-install(3) broken REGR. vs. 104611

Re: [Xen-devel] [PATCH v2] docs: clarify xl mem-max semantics

On 24/01/2017 21:47, Jim Fehlig wrote: > On 01/23/2017 02:49 AM, Juergen Gross wrote: >> The information given in the xl man page for the mem-max command is >> rather brief. Expand it in order to let the reader understand what it >> is really doing. >> >> As the related libxl function

Re: [Xen-devel] [PATCH] arm/p2m: Fix regression during domain shutdown with active mem_access

On 24/01/2017 22:45, Tamas K Lengyel wrote: On Tue, Jan 24, 2017 at 3:32 PM, Julien Grall wrote: On 24/01/2017 22:19, Tamas K Lengyel wrote: On Tue, Jan 24, 2017 at 3:13 PM, Julien Grall wrote: Hi Tamas, On 24/01/2017 22:10, Tamas K Lengyel

Re: [Xen-devel] [PATCH v1 2/2] xen/kbdif: add multi-touch support

On Tue, 24 Jan 2017, Oleksandr Andrushchenko wrote: > On 01/23/2017 09:49 PM, Stefano Stabellini wrote: > > On Sat, 21 Jan 2017, Oleksandr Andrushchenko wrote: > > > In the mail-thread you mentioned above there is a picture of > > > the xenstore entries and conclusion: > > > > > > 1. No change to

Re: [Xen-devel] memory hotplug for domUs

On 01/20/2017 09:06 AM, Juergen Gross wrote: On 20/01/17 16:54, Ian Jackson wrote: Juergen Gross writes ("memory hotplug for domUs"): We first thought to enhance "xl mem-set", but after some more thinking about it I'd rather add a new xl command, e.g. "mem-add" (we could later even add

Re: [Xen-devel] [PATCH v3] kexec: implemented XEN KEXEC STATUS to determine if an image is loaded

On 01/24/2017 01:16 PM, Daniel Kiper wrote: On Tue, Jan 24, 2017 at 12:55:35PM -0600, Eric DeVolder wrote: Instead of the scripts having to poke at various fields we can provide that functionality via the -S parameter. kexec_loaded/kexec_crash_loaded exposes Linux kernel kexec/crash state. It

Re: [Xen-devel] [PATCH v3] kexec: implemented XEN KEXEC STATUS to determine if an image is loaded

On 01/24/2017 01:16 PM, Daniel Kiper wrote: On Tue, Jan 24, 2017 at 12:55:35PM -0600, Eric DeVolder wrote: Instead of the scripts having to poke at various fields we can provide that functionality via the -S parameter. kexec_loaded/kexec_crash_loaded exposes Linux kernel kexec/crash state. It

Re: [Xen-devel] [PATCH] arm/p2m: Fix regression during domain shutdown with active mem_access

On Tue, Jan 24, 2017 at 3:32 PM, Julien Grall wrote: > > > On 24/01/2017 22:19, Tamas K Lengyel wrote: >> >> On Tue, Jan 24, 2017 at 3:13 PM, Julien Grall >> wrote: >>> >>> Hi Tamas, >>> >>> On 24/01/2017 22:10, Tamas K Lengyel wrote:

Re: [Xen-devel] [PATCH] arm/p2m: Fix regression during domain shutdown with active mem_access

On 24/01/2017 22:19, Tamas K Lengyel wrote: On Tue, Jan 24, 2017 at 3:13 PM, Julien Grall wrote: Hi Tamas, On 24/01/2017 22:10, Tamas K Lengyel wrote: The change in commit 438c5fe4f0c introduced a regression for domains where mem_acces is or was active. When

Re: [Xen-devel] [PATCH] arm/p2m: Fix regression during domain shutdown with active mem_access

On Tue, Jan 24, 2017 at 3:13 PM, Julien Grall wrote: > Hi Tamas, > > On 24/01/2017 22:10, Tamas K Lengyel wrote: >> >> The change in commit 438c5fe4f0c introduced a regression for domains where >> mem_acces is or was active. When relinquish_p2m_mapping attempts to clear >> a

Re: [Xen-devel] [PATCH 0/2] ocaml: Start on fixing brokenness when no ocamlopt

> On 24 Jan 2017, at 11:35, Ian Jackson wrote: > > Ian Jackson writes ("[PATCH 0/2] ocaml: Start on fixing brokenness when no > ocamlopt"): >> Debian jessie arm64 has Ocaml (in the package `ocaml-nox') but the >> package lacks ocamlopt. > ... >> This does not

Re: [Xen-devel] [PATCH] arm/p2m: Fix regression during domain shutdown with active mem_access

Hi Tamas, On 24/01/2017 22:10, Tamas K Lengyel wrote: The change in commit 438c5fe4f0c introduced a regression for domains where mem_acces is or was active. When relinquish_p2m_mapping attempts to clear a page where the order is not 0 the following ASSERT is triggered:

[Xen-devel] [PATCH] arm/p2m: Fix regression during domain shutdown with active mem_access

The change in commit 438c5fe4f0c introduced a regression for domains where mem_acces is or was active. When relinquish_p2m_mapping attempts to clear a page where the order is not 0 the following ASSERT is triggered: ASSERT(!p2m->mem_access_enabled || page_order == 0); This regression was

[Xen-devel] [xen-unstable test] 104625: trouble: blocked/broken/fail/pass

flight 104625 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/104625/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-freebsd10-amd64 3 host-install(3) broken REGR. vs.

Re: [Xen-devel] [PATCH v2] docs: clarify xl mem-max semantics

On 01/23/2017 02:49 AM, Juergen Gross wrote: The information given in the xl man page for the mem-max command is rather brief. Expand it in order to let the reader understand what it is really doing. As the related libxl function libxl_domain_setmaxmem() isn't much clearer add a comment to it

Re: [Xen-devel] Is: EPT violations. Was:Re: Problems with pci/vga passthrough

On 01/24/2017 01:51 PM, Boris Ostrovsky wrote: > On 01/24/2017 01:44 PM, Diederik de Haas wrote: >> On dinsdag 24 januari 2017 13:28:28 CET Boris Ostrovsky wrote: > Reported it at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852324 > but given Ben Hutchings' reaction it seems to be a

Re: [Xen-devel] Commit 3a6c9 breaks QEMU on FreeBSD/Xen

On Tue, 24 Jan 2017, Stefano Stabellini wrote: > On Tue, 24 Jan 2017, Roger Pau Monné wrote: > > Hello, > > > > The following commit: > > > > commit 3a6c9172ac5951e6dac2b3f6cbce3cfccdec5894 > > Author: Juergen Gross > > Date: Tue Nov 22 07:10:58 2016 +0100 > > > > xen:

Re: [Xen-devel] [PATCH] xen, input: try to read screen resolution for xen-kbdfront

Hi Juergen, [auto build test ERROR on xen-tip/linux-next] [also build test ERROR on v4.10-rc5] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [Xen-devel] Commit 3a6c9 breaks QEMU on FreeBSD/Xen

On Tue, 24 Jan 2017, Roger Pau Monné wrote: > Hello, > > The following commit: > > commit 3a6c9172ac5951e6dac2b3f6cbce3cfccdec5894 > Author: Juergen Gross > Date: Tue Nov 22 07:10:58 2016 +0100 > > xen: create qdev for each backend device > > Prevents me from running QEMU

[Xen-devel] [xen-unstable-smoke test] 104630: tolerable trouble: broken/fail/pass - PUSHED

flight 104630 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/104630/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a build-arm64-pvops 5

Re: [Xen-devel] [PATCH v14 3/3] iommu: add rmrr Xen command line option for extra rmrrs

> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Tuesday, January 24, 2017 10:08 AM > To: Venu Busireddy > Cc: Feng Wu; Kevin Tian; xen-devel@lists.xen.org; Elena Ufimtseva; Konrad > Rzeszutek Wilk > Subject: Re: [PATCH v14 3/3] iommu: add rmrr Xen command line

Re: [Xen-devel] [early RFC] ARM PCI Passthrough design document

On Tue, 24 Jan 2017, Julien Grall wrote: > > > ## Discovering and register hostbridge > > > > > > Both ACPI and Device Tree do not provide enough information to fully > > > instantiate an host bridge driver. In the case of ACPI, some data may come > > > from ASL, > > > > The data available from

Re: [Xen-devel] [PATCH 4/4] tools/fuzz: add README.afl

On 20/01/17 12:11, Wei Liu wrote: > And rename README to README.oss-fuzz. > > Signed-off-by: Wei Liu > --- > Cc: Andrew Cooper > Cc: George Dunlap > Cc: Ian Jackson > Cc: Jan Beulich

Re: [Xen-devel] [PATCH v3] kexec: implemented XEN KEXEC STATUS to determine if an image is loaded

On Tue, Jan 24, 2017 at 12:55:35PM -0600, Eric DeVolder wrote: > Instead of the scripts having to poke at various fields we can > provide that functionality via the -S parameter. > > kexec_loaded/kexec_crash_loaded exposes Linux kernel kexec/crash > state. It does not say anything about Xen

Re: [Xen-devel] [PATCH v15] This is the ABI for the two halves of a para-virtualized sound driver to communicate with each to other.

On Mon, Dec 05, 2016 at 03:05:29PM +0200, Oleksandr Andrushchenko wrote: > From: Oleksandr Andrushchenko Usually one also puts somethign in the commit description. When I applied this to me tree I got: [konrad@char xen]$ git log --oneline HEAD^.. ecc7711 This

Re: [Xen-devel] [PATCH 0/4] fuzz: basic AFL support

On Tue, 24 Jan 2017, Wei Liu wrote: > On Tue, Jan 24, 2017 at 06:18:10PM +, Julien Grall wrote: > > Hi Wei, > > > > On 20/01/17 12:11, Wei Liu wrote: > > > Provide simple stub programs for AFL fuzzer. For usage, please see > > > README.afl. > > > > > > This series doesn't aim to improve

[Xen-devel] [PATCH v3] kexec: implemented XEN KEXEC STATUS to determine if an image is loaded

Instead of the scripts having to poke at various fields we can provide that functionality via the -S parameter. kexec_loaded/kexec_crash_loaded exposes Linux kernel kexec/crash state. It does not say anything about Xen kexec/crash state. So, we need a special approach to get the latter. Though

Re: [Xen-devel] [PATCH 0/4] fuzz: basic AFL support

On Tue, Jan 24, 2017 at 06:18:10PM +, Julien Grall wrote: > Hi Wei, > > On 20/01/17 12:11, Wei Liu wrote: > > Provide simple stub programs for AFL fuzzer. For usage, please see > > README.afl. > > > > This series doesn't aim to improve fuzzing targets. It is just demonstration > > for how

[Xen-devel] [PATCH v3] xen: credit2: performance counter for load balancing call

The patch introduces a new performance counter that counts how many times we go through the load balancing logic in Credit2. Signed-off-by: Praveen Kumar Acked-by: Dario Faggioli --- diff --git a/xen/common/sched_credit2.c

Re: [Xen-devel] [PATCH v2 3/4] tools/fuzz: add AFL stub program for libefl fuzzer

Wei Liu writes ("[PATCH v2 3/4] tools/fuzz: add AFL stub program for libefl fuzzer"): > And hook it up into build system. Acked-by: Ian Jackson ___ Xen-devel mailing list Xen-devel@lists.xen.org

[Xen-devel] [PATCH v2] xen: credit2: performance counter for load balancing call

The patch introduces a new performance counter that counts how many times we go through the load balancing logic called in Credit2. Signed-off-by: Praveen Kumar Acked-by: Dario Faggioli --- diff --git a/xen/common/sched_credit2.c

Re: [Xen-devel] Is: EPT violations. Was:Re: Problems with pci/vga passthrough

On 01/24/2017 01:44 PM, Diederik de Haas wrote: > On dinsdag 24 januari 2017 13:28:28 CET Boris Ostrovsky wrote: Reported it at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852324 but given Ben Hutchings' reaction it seems to be a Xen problem after all. Relevant part

Re: [Xen-devel] [PATCH] xen, input: try to read screen resolution for xen-kbdfront

On Tue, Jan 24, 2017 at 01:09:55PM +0100, Juergen Gross wrote: > Instead of using the default resolution of 800*600 for the pointing > device of xen-kbdfront try to read the resolution of the (virtual) > framebuffer device. Use the default as fallback only. > > Cc: sta...@vger.kernel.org >

[Xen-devel] [PATCH v2 2/4] tools/fuzz: add AFL stub program for x86 insn emulator fuzzer

This is a basic program to call into the unified fuzzing function. Hook it up into build system so that we can always build test it. Signed-off-by: Wei Liu --- Cc: Andrew Cooper Cc: George Dunlap Cc: Ian Jackson

[Xen-devel] [PATCH v2 1/4] tools/fuzz: add missing dependencies in x86 insn fuzzer build rule

The said file needs the two header files. Signed-off-by: Wei Liu --- Cc: Ian Jackson --- tools/fuzz/x86_instruction_emulator/Makefile | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/fuzz/x86_instruction_emulator/Makefile

[Xen-devel] [PATCH v2 0/4] fuzz: basic AFL suppport

Provide simple stub programs for AFL fuzzer. For usage, please see README.afl. This series doesn't aim to improve fuzzing targets. It is just demonstration for how we could use the same fuzzing code for both oss-fuzz and AFL. The stub programs are identical in libefl and x86 emulator at the

[Xen-devel] [PATCH v2 3/4] tools/fuzz: add AFL stub program for libefl fuzzer

And hook it up into build system. Signed-off-by: Wei Liu --- Cc: Andrew Cooper Cc: George Dunlap Cc: Ian Jackson Cc: Jan Beulich --- .gitignore

[Xen-devel] [PATCH v2 4/4] tools/fuzz: add README.afl

And rename README to README.oss-fuzz. Signed-off-by: Wei Liu --- Cc: Andrew Cooper Cc: George Dunlap Cc: Ian Jackson Cc: Jan Beulich --- tools/fuzz/README.afl

Re: [Xen-devel] Is: EPT violations. Was:Re: Problems with pci/vga passthrough

On dinsdag 24 januari 2017 13:28:28 CET Boris Ostrovsky wrote: > >> Reported it at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852324 > >> but given Ben Hutchings' reaction it seems to be a Xen problem after > >> all. > >> > >> Relevant part of earlier attached dmesg: > >> > >> [

[Xen-devel] [OSSTEST PATCH] sg-check-tested: Do not exit without printing results

In fd2fbb9171f12d5f45e952e2915f3e00bcaacc1a "sg-check-tested: Lift work into new `search' sub, and indirect output" I missed an `exit 0'. As a result sg-check-tested --print-revision= would never print anything! Signed-off-by: Ian Jackson --- sg-check-tested | 2 +-

Re: [Xen-devel] [PATCH 3/5] hotplug/linux: Improve iptables logic

Hi, > AFIACT the duplicate entries are simply because > >> - iptables "$c" FORWARD -w $dev_in_match "$dev" \ >> -"$@" -j ACCEPT 2>/dev/null && >> - iptables "$c" FORWARD -w $dev_out_match "$dev" \ >> --j ACCEPT 2>/dev/null > > this second line, which does not contain "$@", is invoked

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

This run is configured for baseline tests only. flight 68429 ovmf real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68429/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): build-i3863 host-install(3) broken

Re: [Xen-devel] [PATCH] xen: credit2: performance counter for load balancing call

On Tue, 2017-01-24 at 23:23 +0530, Praveen Kumar wrote: > The patch introduces a new performance counter that keeps track of > the load > balancing logic called in credit2 scheduler. > I probably would have written "that counts how many time we go through the load balancing logic in Credit2" Or

Re: [Xen-devel] Is: EPT violations. Was:Re: Problems with pci/vga passthrough

On 01/24/2017 11:11 AM, Jan Beulich wrote: On 24.01.17 at 16:59, wrote: >> Reported it at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852324 but >> given Ben Hutchings' reaction it seems to be a Xen problem after all. >> >> Relevant part of earlier attached

Re: [Xen-devel] [PATCH 0/4] fuzz: basic AFL support

Hi Wei, On 20/01/17 12:11, Wei Liu wrote: Provide simple stub programs for AFL fuzzer. For usage, please see README.afl. This series doesn't aim to improve fuzzing targets. It is just demonstration for how we could use the same fuzzing code for both oss-fuzz and AFL. The stub programs are

Re: [Xen-devel] [PATCH 5/5] hotplug/linux: Add IPv6 support to vif-route

Hi, > I'm afraid I don't really understand IPv6 neighbour discovery > etc. well enough to review this. > > Can you point me to an explanation ? (I understand IPv4 quite well.) It's pretty much that same as IPv4 except instead of being a different protocol (ARP), it's done over ICMPv6 with

[Xen-devel] [PATCH] xen: credit2: performance counter for load balancing call

The patch introduces a new performance counter that keeps track of the load balancing logic called in credit2 scheduler. Signed-off-by: Praveen Kumar --- diff --git a/xen/common/sched_credit2.c b/xen/common/sched_credit2.c index ef8e0d8..f212338 100644 ---

Re: [Xen-devel] [PATCH 2/4] tools/fuzz: add AFL stub program for x86 insn emulator fuzzer

Wei Liu writes ("Re: [PATCH 2/4] tools/fuzz: add AFL stub program for x86 insn emulator fuzzer"): > Hmm... I originally thought exit(1) would cause AFL to think the program > has crashed, but I was wrong. Ah. Yes, indeed. Sorry for not explaining that. > So using exit(1) is more sensible in

Re: [Xen-devel] [PATCH 0/5] Various improvements for the VIF linux hotplug scripts

Sylvain Munaut writes ("[PATCH 0/5] Various improvements for the VIF linux hotplug scripts"): > This patch series contains several improvement to the linux hotplug network > script, mostly adding IPv6 support to the iptables firewall setup and routing > setup. > > The series can also be cloned

Re: [Xen-devel] [PATCH 5/5] hotplug/linux: Add IPv6 support to vif-route

Sylvain Munaut writes ("[PATCH 5/5] hotplug/linux: Add IPv6 support to vif-route"): > Signed-off-by: Sylvain Munaut > --- > docs/man/xl-network-configuration.markdown.5 | 9 > tools/hotplug/Linux/vif-common.sh| 33 >

Re: [Xen-devel] [PATCH 4/5] hotplug/linux: Add IPv6 support to the iptables logic

Sylvain Munaut writes ("[PATCH 4/5] hotplug/linux: Add IPv6 support to the iptables logic"): > This adds the same functions for ip6tables as the one for iptables. > The 'ip' variable can now contain ipv6s for the domain and add > appropriate rules > > - If the 'ip' var is empty then both full

Re: [Xen-devel] [early RFC] ARM PCI Passthrough design document

On 19/01/17 05:09, Manish Jaggi wrote: Hi Julien, Hello Manish, Please trim the quoted e-mail, it is a bit annoying to try to find where you answer. On 12/29/2016 07:34 PM, Julien Grall wrote: DOM0 will issue the hypercall PHYSDEVOP_pci_host_bridge_add for each host bridge available on

Re: [Xen-devel] [PATCH 3/5] hotplug/linux: Improve iptables logic

Sylvain Munaut writes ("[PATCH 3/5] hotplug/linux: Improve iptables logic"): > The main goal of this is to pave the way for IPv6 support, but it > also improves the rules by preventing duplicate incoming packets > rules to be added. > > frob_iptables now takes a list of address to handle as

[Xen-devel] [qemu-mainline test] 104624: trouble: blocked/broken/fail/pass

flight 104624 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/104624/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-raw3 host-install(3)broken REGR. vs.

Re: [Xen-devel] [PATCH 2/4] tools/fuzz: add AFL stub program for x86 insn emulator fuzzer

On Tue, Jan 24, 2017 at 05:30:32PM +, Ian Jackson wrote: > Andrew Cooper writes ("Re: [PATCH 2/4] tools/fuzz: add AFL stub program for > x86 insn emulator fuzzer"): > > On 24/01/17 17:22, Ian Jackson wrote: > > > You don't need to test with stat unless you want to support files > > > bigger

[Xen-devel] [xen-4.0-testing baseline-only test] 68432: tolerable FAIL

This run is configured for baseline tests only. flight 68432 xen-4.0-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68432/ Failures :-/ but no regressions. Tests which did not succeed, including tests which could not be run: test-i386-i386-xl 1

Re: [Xen-devel] [PATCH 1/5] hotplug/linux: Use the '-w' wait flag when calling iptables

Sylvain Munaut writes ("[PATCH 1/5] hotplug/linux: Use the '-w' wait flag when calling iptables"): > Without this, several hotplug script instances might attempt to run at > the same rime and one will fail because it can't get the xtables lock ! > > The 'frob_iptables' is protected by a lock,

Re: [Xen-devel] [PATCH 2/4] tools/fuzz: add AFL stub program for x86 insn emulator fuzzer

Andrew Cooper writes ("Re: [PATCH 2/4] tools/fuzz: add AFL stub program for x86 insn emulator fuzzer"): > On 24/01/17 17:22, Ian Jackson wrote: > > You don't need to test with stat unless you want to support files > > bigger than your static buffer. > > It is expected that AFL data will

Re: [Xen-devel] [PATCH 2/4] tools/fuzz: add AFL stub program for x86 insn emulator fuzzer

On Tue, Jan 24, 2017 at 05:22:37PM +, Ian Jackson wrote: > Wei Liu writes ("Re: [PATCH 2/4] tools/fuzz: add AFL stub program for x86 > insn emulator fuzzer"): > > On Tue, Jan 24, 2017 at 05:05:16PM +, Ian Jackson wrote: > > > If you use read you ought to put it in a loop to cope with

Re: [Xen-devel] [PATCH 2/4] tools/fuzz: add AFL stub program for x86 insn emulator fuzzer

On Tue, Jan 24, 2017 at 05:25:29PM +, Andrew Cooper wrote: > On 24/01/17 17:22, Ian Jackson wrote: > > Wei Liu writes ("Re: [PATCH 2/4] tools/fuzz: add AFL stub program for x86 > > insn emulator fuzzer"): > >> On Tue, Jan 24, 2017 at 05:05:16PM +, Ian Jackson wrote: > >>> If you use read

Re: [Xen-devel] [PATCH 2/4] tools/fuzz: add AFL stub program for x86 insn emulator fuzzer

On 24/01/17 17:22, Ian Jackson wrote: > Wei Liu writes ("Re: [PATCH 2/4] tools/fuzz: add AFL stub program for x86 > insn emulator fuzzer"): >> On Tue, Jan 24, 2017 at 05:05:16PM +, Ian Jackson wrote: >>> If you use read you ought to put it in a loop to cope with potential >>> partial reads.

Re: [Xen-devel] Is: EPT violations. Was:Re: Problems with pci/vga passthrough

On dinsdag 24 januari 2017 09:11:22 CET Jan Beulich wrote: > Now this is a know issue, but I'm pretty convinced one that's entirely > unrelated to your problem. Ok, good to know. Not having a clue on how to achieve what I really want, vga passthrough, I'm just trying to work my way through the

Re: [Xen-devel] [PATCH 2/4] tools/fuzz: add AFL stub program for x86 insn emulator fuzzer

Wei Liu writes ("Re: [PATCH 2/4] tools/fuzz: add AFL stub program for x86 insn emulator fuzzer"): > On Tue, Jan 24, 2017 at 05:05:16PM +, Ian Jackson wrote: > > If you use read you ought to put it in a loop to cope with potential > > partial reads. > > Does fread have better properties than

Re: [Xen-devel] [PATCH 2/4] tools/fuzz: add AFL stub program for x86 insn emulator fuzzer

On Tue, Jan 24, 2017 at 05:05:16PM +, Ian Jackson wrote: > Wei Liu writes ("[PATCH 2/4] tools/fuzz: add AFL stub program for x86 insn > emulator fuzzer"): > > This is a basic program to call into the unified fuzzing function. > ... > > +fd = open(argv[1], O_RDONLY, 0); > > +assert(fd

Re: [Xen-devel] [PATCH v3 3/3] xen: optimize xenbus driver for multiple concurrent xenstore accesses

On 01/24/2017 11:23 AM, Juergen Gross wrote: > On 24/01/17 14:47, Boris Ostrovsky wrote: >> On 01/23/2017 01:59 PM, Boris Ostrovsky wrote: >>> On 01/23/2017 05:09 AM, Juergen Gross wrote: Handling of multiple concurrent Xenstore accesses through xenbus driver either from the kernel or

  1   2   3   >