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

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

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

flight 101861 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/101861/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-armhf-armhf-xl-arndale 3 host-install(3) broken pass in 101848 test-armhf-armhf-libvirt 15

[Xen-devel] [xen-unstable baseline-only test] 67981: tolerable FAIL

This run is configured for baseline tests only. flight 67981 xen-unstable real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/67981/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-amd64-i386-pvgrub 10 guest-start

[Xen-devel] [linux-3.4 test] 101858: regressions - FAIL

flight 101858 linux-3.4 real [real] http://logs.test-lab.xenproject.org/osstest/logs/101858/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl 6 xen-boot fail REGR. vs. 92983

[Xen-devel] [ovmf baseline-only test] 67982: all pass

This run is configured for baseline tests only. flight 67982 ovmf real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/67982/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 90a40219673303f97890d5ea2e367ee2dc04a0b3 baseline

Re: [Xen-devel] Nested virtualization off VMware vSphere 6.0 with EL6 guests crashes on Xen 4.6

On Fri, Feb 05, 2016 at 03:33:44AM -0700, Jan Beulich wrote: > >>> On 04.02.16 at 19:36, wrote: > > (XEN) nvmx_handle_vmwrite 1: IO_BITMAP_A(2000)[0=] > > (XEN) nvmx_handle_vmwrite 0: IO_BITMAP_A(2000)[0=] > > (XEN) nvmx_handle_vmwrite 1:

[Xen-devel] [linux-3.10 test] 101856: regressions - FAIL

flight 101856 linux-3.10 real [real] http://logs.test-lab.xenproject.org/osstest/logs/101856/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-amd64-pvgrub 6 xen-bootfail REGR. vs. 100648

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

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

[Xen-devel] [PULL 2/2] PCMachineState: introduce acpi_build_enabled field

From: Wei Liu Introduce this field to control whether ACPI build is enabled by a particular machine or accelerator. It defaults to true if the machine itself supports ACPI build. Xen accelerator will disable it because Xen is in charge of building ACPI tables for the guest.

Re: [Xen-devel] [Qemu-devel] [PATCH] hw/xen/xen_pvdev: Include qemu/log.h for qemu_log_vprintf()

On Wed, 2 Nov 2016, Peter Maydell wrote: > On 2 November 2016 at 17:34, Stefano Stabellini > wrote: > > On Wed, 2 Nov 2016, Thomas Huth wrote: > >> Olaf Hering reported a build failure due to an undefined reference > >> to 'qemu_log_vprintf'. Explicitely including

[Xen-devel] [PULL 1/2] hw/xen/xen_pvdev: Include qemu/log.h for qemu_log_vprintf()

From: Thomas Huth Olaf Hering reported a build failure due to an undefined reference to 'qemu_log_vprintf'. Explicitely including qemu/log.h seems to fix the issue. Signed-off-by: Thomas Huth Signed-off-by: Stefano Stabellini

[Xen-devel] [PULL 0/2] tags/xen-20161102-tag

-20161102-tag for you to fetch changes up to 021746c131cdfeab9d82ff918795a9f18d20d7ae: PCMachineState: introduce acpi_build_enabled field (2016-11-02 12:26:12 -0700) Xen 2016/11/02

Re: [Xen-devel] [Qemu-devel] [PATCH] hw/xen/xen_pvdev: Include qemu/log.h for qemu_log_vprintf()

On 2 November 2016 at 17:34, Stefano Stabellini wrote: > On Wed, 2 Nov 2016, Thomas Huth wrote: >> Olaf Hering reported a build failure due to an undefined reference >> to 'qemu_log_vprintf'. Explicitely including qemu/log.h seems to >> fix the issue. >> >> Signed-off-by:

Re: [Xen-devel] Xen on Qualcomm

Can you please post the error and details on Xen you are using? Thanks, Sameer On 11/2/2016 3:04 AM, Suresh Kanzariya wrote: Hi, I am trying to run Xen on Qualcomm 410 platform. I have come across below link https://lists.xenproject.org/archives/html/xen-devel/2016-03/msg03144.html which

Re: [Xen-devel] [PATCH 1/1] xen-netfront: cast grant table reference first to type int

From: Dongli Zhang Date: Wed, 2 Nov 2016 09:04:33 +0800 > IS_ERR_VALUE() in commit 87557efc27f6a50140fb20df06a917f368ce3c66 > ("xen-netfront: do not cast grant table reference to signed short") would > not return true for error code unless we cast ref first to type int.

Re: [Xen-devel] [PATCH] hw/xen/xen_pvdev: Include qemu/log.h for qemu_log_vprintf()

On Wed, Nov 02, Thomas Huth wrote: > Olaf Hering reported a build failure due to an undefined reference > to 'qemu_log_vprintf'. Explicitely including qemu/log.h seems to > fix the issue. > > Signed-off-by: Thomas Huth Tested-by: Olaf Hering Olaf

Re: [Xen-devel] [RFC PATCH 11/24] ARM: vGICv3: handle virtual LPI pending and property tables

On Wed, 2 Nov 2016, Julien Grall wrote: > Hi Stefano, > > On 02/11/16 17:41, Stefano Stabellini wrote: > > On Wed, 2 Nov 2016, Julien Grall wrote: > > > > +} > > > > + > > > > +ptr = vmap(pages, nr_pages); > > > > > > I am not a big fan of the vmap solution for various reasons: > > > -

Re: [Xen-devel] [RFC PATCH 11/24] ARM: vGICv3: handle virtual LPI pending and property tables

Hi Stefano, On 02/11/16 17:41, Stefano Stabellini wrote: On Wed, 2 Nov 2016, Julien Grall wrote: +} + +ptr = vmap(pages, nr_pages); I am not a big fan of the vmap solution for various reasons: - the VMAP area is small (only 1GB) it will not scale (you seem to use it to map

Re: [Xen-devel] [RFC PATCH 03/24] ARM: GICv3 ITS: allocate device and collection table

Hi, On 24/10/16 15:30, Vijay Kilari wrote: > On Wed, Sep 28, 2016 at 11:54 PM, Andre Przywara > wrote: >> Each ITS maps a pair of a DeviceID (usually the PCI b/d/f triplet) and >> an EventID (the MSI payload or interrupt ID) to a pair of LPI number >> and collection ID,

Re: [Xen-devel] [PATCH] x86emul: {L, S}{G, I}DT ignore operand size overrides in 64-bit mode

On 02/11/16 16:12, Jan Beulich wrote: > This affects not only the layout of the data (always 2+8 bytes), but > also the contents (no truncation to 24 bits occurs). > > Signed-off-by: Jan Beulich Reviewed-by: Andrew Cooper , although wouldn't it be

Re: [Xen-devel] [RFC PATCH 11/24] ARM: vGICv3: handle virtual LPI pending and property tables

On Wed, 2 Nov 2016, Julien Grall wrote: > > +} > > + > > +ptr = vmap(pages, nr_pages); > > I am not a big fan of the vmap solution for various reasons: > - the VMAP area is small (only 1GB) it will not scale (you seem > to use it to map pretty much all memory provisioned for the

Re: [Xen-devel] [PATCH for-4.8] x86/emul: Reject LGDT/LIDT attempts with non-canonical base addresses

On 02/11/16 15:42, Jan Beulich wrote: On 02.11.16 at 15:52, wrote: >> No sane OS would deliberately try this, but make Xen's emulation match real >> hardware by delivering #GP(0), rather than suffering a VMEntry failure. >> >> Signed-off-by: Andrew Cooper

Re: [Xen-devel] [PATCH] hw/xen/xen_pvdev: Include qemu/log.h for qemu_log_vprintf()

On Wed, 2 Nov 2016, Thomas Huth wrote: > Olaf Hering reported a build failure due to an undefined reference > to 'qemu_log_vprintf'. Explicitely including qemu/log.h seems to > fix the issue. > > Signed-off-by: Thomas Huth The fix makes sense: Acked-by: Stefano Stabellini

[Xen-devel] [ovmf baseline-only test] 67980: all pass

This run is configured for baseline tests only. flight 67980 ovmf real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/67980/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 1c8ca9a012ce19a1096625ef9e810036e8346827 baseline

Re: [Xen-devel] [RFC PATCH 11/24] ARM: vGICv3: handle virtual LPI pending and property tables

Hi Andre, On 28/09/16 19:24, Andre Przywara wrote: Allow a guest to provide the address and size for the memory regions it has reserved for the GICv3 pending and property tables. We sanitise the various fields of the respective redistributor registers and map those pages into Xen's address

Re: [Xen-devel] [PATCH v3.1 03/15] xen/x86: allow calling {sh/hap}_set_allocation with the idle domain

On Tue, Nov 01, 2016 at 10:45:05AM +, Tim Deegan wrote: > At 10:34 -0600 on 31 Oct (1477910088), Jan Beulich wrote: > > >>> On 29.10.16 at 10:59, wrote: > > > ... and using the "preempted" parameter. The solution relies on just > > > calling > > > softirq_pending if the

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

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

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

flight 101850 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/101850/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-xsm 3 host-install(3)broken REGR. vs. 101835 build-amd64-xsm

[Xen-devel] [ANNOUNCEMENT] Xen 4.8 RC5

Hi all Xen 4.8 rc5 is tagged. You can check that out from xen.git: git://xenbits.xen.org/xen.git 4.8.0-rc5 For you convenience, please find tarball and signature at: https://downloads.xenproject.org/release/xen/4.8.0-rc5/ Please send bug reports and test reports to

Re: [Xen-devel] [PATCH v3] features: declare the Credit2 scheduler as Supported.

On Wed, Nov 02, 2016 at 04:49:37PM +0100, Dario Faggioli wrote: > On Wed, 2016-11-02 at 15:39 +, Wei Liu wrote: > > On Wed, Nov 02, 2016 at 04:05:03PM +0100, Dario Faggioli wrote: > > > > > > Credit2 is available in tree as an "Experimental" scheduler since > > > a few years. Recently, effort

Re: [Xen-devel] [RFC PATCH 02/24] ARM: GICv3: allocate LPI pending and property table

On 24/10/16 15:28, Vijay Kilari wrote: Hi Vijay, thanks for having a look! > On Wed, Sep 28, 2016 at 11:54 PM, Andre Przywara > wrote: >> The ARM GICv3 ITS provides a new kind of interrupt called LPIs. >> The pending bits and the configuration data (priority, enable

[Xen-devel] [PATCH] x86emul: {L, S}{G, I}DT ignore operand size overrides in 64-bit mode

This affects not only the layout of the data (always 2+8 bytes), but also the contents (no truncation to 24 bits occurs). Signed-off-by: Jan Beulich --- This will only apply cleanly on top of https://lists.xenproject.org/archives/html/xen-devel/2016-11/msg00170.html. ---

Re: [Xen-devel] [PATCH v3] features: declare the Credit2 scheduler as Supported.

Dario Faggioli writes ("Re: [PATCH v3] features: declare the Credit2 scheduler as Supported."): > On Wed, 2016-11-02 at 15:39 +, Wei Liu wrote: > > On Wed, Nov 02, 2016 at 04:05:03PM +0100, Dario Faggioli wrote: > > > In fact, Credit2's much more modern (wrt Credit1) design and > > > cleaner

Re: [Xen-devel] [PATCH v3] features: declare the Credit2 scheduler as Supported.

> Signed-off-by: Dario Faggioli > --- > Changes since v2: > * 'EXPERIMENTAL' tag removed from Kconfig; > * reworded paragraph on SCHEDOP DOMCTL & SYSCTL from Dom0. > --- > Cc: George Dunlap > Cc: Anshul Makkar >

Re: [Xen-devel] [PATCH v2] PCMachineState: introduce acpi_build_enabled field

On Tue, Nov 01, 2016 at 03:30:59PM -0700, Stefano Stabellini wrote: > On Tue, 1 Nov 2016, Eduardo Habkost wrote: > > On Tue, Nov 01, 2016 at 05:44:16PM +, Wei Liu wrote: > > > Introduce this field to control whether ACPI build is enabled by a > > > particular machine or accelerator. > > > > >

Re: [Xen-devel] [PATCH v3] features: declare the Credit2 scheduler as Supported.

On Wed, 2016-11-02 at 15:39 +, Wei Liu wrote: > On Wed, Nov 02, 2016 at 04:05:03PM +0100, Dario Faggioli wrote: > > > > Credit2 is available in tree as an "Experimental" scheduler since > > a few years. Recently, effort started for making it production > > ready > > and, eventually, the new

Re: [Xen-devel] GRUB ARM Xen patches

On 02/11/16 12:33, Daniel Kiper wrote: Hi, Hi Daniel, Julien asked me to apply some GRUB ARM Xen patches. On the basis of his requested I identified following patch(es): - [PATCH] arm64: xen_boot: Fix xen boot using Grub on AARCH64

Re: [Xen-devel] [PATCH v3] features: declare the Credit2 scheduler as Supported.

On 02/11/16 15:05, Dario Faggioli wrote: > Credit2 is available in tree as an "Experimental" scheduler since > a few years. Recently, effort started for making it production ready > and, eventually, the new Xen's default scheduler. As a consequence of > that, it has undergone a greatd deal of

Re: [Xen-devel] [PATCH for-4.8] x86/emul: Reject LGDT/LIDT attempts with non-canonical base addresses

>>> On 02.11.16 at 15:52, wrote: > No sane OS would deliberately try this, but make Xen's emulation match real > hardware by delivering #GP(0), rather than suffering a VMEntry failure. > > Signed-off-by: Andrew Cooper Reviewed-by: Jan

Re: [Xen-devel] [PATCH v3] features: declare the Credit2 scheduler as Supported.

On Wed, Nov 02, 2016 at 04:05:03PM +0100, Dario Faggioli wrote: > Credit2 is available in tree as an "Experimental" scheduler since > a few years. Recently, effort started for making it production ready > and, eventually, the new Xen's default scheduler. As a consequence of > that, it has

Re: [Xen-devel] [PATCH v3] features: declare the Credit2 scheduler as Supported.

>>> On 02.11.16 at 16:05, wrote: > Credit2 is available in tree as an "Experimental" scheduler since > a few years. Recently, effort started for making it production ready > and, eventually, the new Xen's default scheduler. As a consequence of > that, it has undergone a

[Xen-devel] [xen-unstable test] 101848: tolerable FAIL - PUSHED

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

Re: [Xen-devel] [RFC PATCH 06/24] ARM: GICv3 ITS: introduce host LPI array

Hi, On 27/10/16 23:59, Stefano Stabellini wrote: On Wed, 28 Sep 2016, Andre Przywara wrote: The number of LPIs on a host can be potentially huge (millions), although in practise will be mostly reasonable. So prematurely allocating an array of struct irq_desc's for each LPI is not an option.

Re: [Xen-devel] Maximum number of vcpus for HVM?

On 02/11/2016 06:01, "Andrew Cooper" wrote: >On 02/11/16 09:36, Juergen Gross wrote: >> According to >> >> https://wiki.xenproject.org/wiki/Xen_Project_Release_Features >> >> HVM guests can have up to 256 vcpus. The definition in >> >>

Re: [Xen-devel] [RFC PATCH 05/24] ARM: GICv3 ITS: introduce ITS command handling

Hi Andre, On 28/09/16 19:24, Andre Przywara wrote: To be able to easily send commands to the ITS, create the respective wrapper functions, which take care of the ring buffer. The first two commands we implement provide methods to map a collection to a redistributor (aka host core) and to flush

[Xen-devel] [PATCH v3] features: declare the Credit2 scheduler as Supported.

Credit2 is available in tree as an "Experimental" scheduler since a few years. Recently, effort started for making it production ready and, eventually, the new Xen's default scheduler. As a consequence of that, it has undergone a greatd deal of development, testing and benchmarking. In fact,

Re: [Xen-devel] [PATCH for-4.8] libxl: disallow enabling PoD and ALTP2M at the same time

On Wed, Nov 02, 2016 at 02:43:58PM +, Ian Jackson wrote: > Wei Liu writes ("[PATCH for-4.8] libxl: disallow enabling PoD and ALTP2M at > the same time"): > > That combination would cause Xen to crash. Note that this is not a > > security issue because ALTP2M is experimental. > > Acked-by:

[Xen-devel] [PATCH for-4.8] x86/emul: Reject LGDT/LIDT attempts with non-canonical base addresses

No sane OS would deliberately try this, but make Xen's emulation match real hardware by delivering #GP(0), rather than suffering a VMEntry failure. Signed-off-by: Andrew Cooper --- CC: Jan Beulich CC: Wei Liu ---

Re: [Xen-devel] [PATCH for-4.8] libxl: disallow enabling PoD and ALTP2M at the same time

Wei Liu writes ("[PATCH for-4.8] libxl: disallow enabling PoD and ALTP2M at the same time"): > That combination would cause Xen to crash. Note that this is not a > security issue because ALTP2M is experimental. Acked-by: Ian Jackson You mean, though Note that

[Xen-devel] [PATCH for-4.8] libxl: disallow enabling PoD and ALTP2M at the same time

That combination would cause Xen to crash. Note that this is not a security issue because ALTP2M is experimental. Signed-off-by: Wei Liu --- Cc: Ian Jackson Maybe backport this to 4.6 and 4.7? --- tools/libxl/libxl_create.c | 7 +++ 1 file

Re: [Xen-devel] [RFC PATCH 00/24] [FOR 4.9] arm64: Dom0 ITS emulation

Hi, On 28/09/16 19:24, Andre Przywara wrote: Andre Przywara (24): ARM: GICv3 ITS: parse and store ITS subnodes from hardware DT ARM: GICv3: allocate LPI pending and property table ARM: GICv3 ITS: allocate device and collection table ARM: GICv3 ITS: map ITS command buffer ARM: GICv3

Re: [Xen-devel] [BUG] altp2m from domU crashes the host

Andrew, Thank you for the tip. The crash does not happen when the "maxmem" option in the config file is disabled. I still get funny behavior with my driver, but I need to investigate that further. Regards, Matt On 11/02/2016 08:23 AM, Andrew Cooper wrote: > On 02/11/16 13:16, Matt Leinhos

Re: [Xen-devel] [RFC PATCH 04/24] ARM: GICv3 ITS: map ITS command buffer

Hello Andre, On 28/09/16 19:24, Andre Przywara wrote: Instead of directly manipulating the tables in memory, an ITS driver sends commands via a ring buffer to the ITS h/w to create or alter the LPI mappings. Allocate memory for that buffer and tell the ITS about it to be able to send ITS

Re: [Xen-devel] [BUG] altp2m from domU crashes the host

On 02/11/16 13:16, Matt Leinhos wrote: > Hello, > > I am working on a Linux driver that exercises the altp2m interface from > a guest VM. Unfortunately, something goes horribly wrong and I end up > crashing the Xen host. > > dom0 is Ubuntu 16.04; the domU guest is running Centos with Linux kernel

[Xen-devel] [BUG] altp2m from domU crashes the host

Hello, I am working on a Linux driver that exercises the altp2m interface from a guest VM. Unfortunately, something goes horribly wrong and I end up crashing the Xen host. dom0 is Ubuntu 16.04; the domU guest is running Centos with Linux kernel 3.10.0-327. Following these steps on a domU guest

[Xen-devel] GRUB ARM Xen patches

Hi, Julien asked me to apply some GRUB ARM Xen patches. On the basis of his requested I identified following patch(es): - [PATCH] arm64: xen_boot: Fix xen boot using Grub on AARCH64 https://lists.gnu.org/archive/html/grub-devel/2016-02/msg00205.html - [PATCH v6 0/4] arm64,xen: add

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

flight 101854 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/101854/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-libvirt 16 guest-start.2fail REGR. vs. 101839 Regressions which are

Re: [Xen-devel] [PATCH 3/3] xen/x86: Use non-canonical pointers for ERR_PTR() errors

>>> On 01.11.16 at 11:46, wrote: > The top of the virutal address space is owned by 64bit PV kernels. Code which > fails to correctly check an ERR_PTR() value might follow the pointer into > guest space. > > Mitigate this risk by sliding the ERR_PTR() error range into

Re: [Xen-devel] [PATCH 2/3] xen/err: Support an optional per-arch slide for the error region

>>> On 01.11.16 at 11:46, wrote: > --- a/xen/include/xen/err.h > +++ b/xen/include/xen/err.h > @@ -15,19 +15,28 @@ > */ > #define MAX_ERRNO4095 > > +/* > + * Individual architectures may wish to slide the error region away from its > + * default position at the

Re: [Xen-devel] [PATCH 1/3] xen/err: Use static inlines and boolean types

>>> On 01.11.16 at 11:46, wrote: > IS_ERR() and IS_ERR_OR_NULL() both return boolean values. > > No functional change. I'm definitely fine with this part. However, ... > @@ -14,7 +15,10 @@ > */ > #define MAX_ERRNO4095 > > -#define IS_ERR_VALUE(x)

Re: [Xen-devel] [PATCH v2] features: declare the Credit2 scheduler as Supported.

>>> On 02.11.16 at 12:22, wrote: > On Wed, 2016-11-02 at 04:59 -0600, Jan Beulich wrote: >> > > > On 02.11.16 at 11:22, wrote: >> > The control domain can issue DOMCTL_SCHEDOP and SYSCTL_SCHEDOP >> > hypercalls. Auditing such code, nothing

Re: [Xen-devel] [PATCH v2] features: declare the Credit2 scheduler as Supported.

On Wed, 2016-11-02 at 04:59 -0600, Jan Beulich wrote: > > > > On 02.11.16 at 11:22, wrote: > > The control domain can issue DOMCTL_SCHEDOP and SYSCTL_SCHEDOP > > hypercalls. Auditing such code, nothing that looks like a security > > risk has been found (E.g., there's no

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

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

Re: [Xen-devel] xc_hvm_inject_trap() races

> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 2 November, 2016 12:46 > To: Andrei Vlad LUTAS > Cc: rcojoc...@bitdefender.com; andrew.coop...@citrix.com; xen- > de...@lists.xenproject.org; ta...@tklengyel.com > Subject: RE: RE:

[Xen-devel] [linux-3.4 test] 101846: regressions - FAIL

flight 101846 linux-3.4 real [real] http://logs.test-lab.xenproject.org/osstest/logs/101846/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl 6 xen-boot fail REGR. vs. 92983

Re: [Xen-devel] [PATCH v2] features: declare the Credit2 scheduler as Supported.

>>> On 02.11.16 at 11:22, wrote: > 3) Is there any information leakage? > > The only information which the scheduler exposes to unprivileged > guests is the timing information. This may be able to be used for > side-channel attacks to probabilistically infer things

Re: [Xen-devel] [PATCH v2] features: declare the Credit2 scheduler as Supported.

On Wed, 2016-11-02 at 10:37 +, Andrew Cooper wrote: > On 02/11/16 10:22, Dario Faggioli wrote: > > > > > --- > >  docs/features/sched_credit2.pandoc |2 +- > >  xen/common/sched_credit2.c |2 -- > >  2 files changed, 1 insertion(+), 3 deletions(-) > > There is also text in

Re: [Xen-devel] xc_hvm_inject_trap() races

>>> On 02.11.16 at 11:22, wrote: >> From: Jan Beulich [mailto:jbeul...@suse.com] >> Sent: 2 November, 2016 12:05 >> >>> On 02.11.16 at 10:53, wrote: >> > The decision whether further events are needed or not is NOT made >> > based on the contents

Re: [Xen-devel] [PATCH v2] features: declare the Credit2 scheduler as Supported.

On 02/11/16 10:22, Dario Faggioli wrote: > --- > docs/features/sched_credit2.pandoc |2 +- > xen/common/sched_credit2.c |2 -- > 2 files changed, 1 insertion(+), 3 deletions(-) There is also text in Kconfig which should be adjusted. We should probably have a checklist of items

Re: [Xen-devel] [PATCH 04/12] xen: make use of xenbus_read_unsigned() in xen-tpmfront

On Mon, Oct 31, 2016 at 05:48:22PM +0100, Juergen Gross wrote: > Use xenbus_read_unsigned() instead of xenbus_scanf() when possible. > This requires to change the type of one read from int to unsigned, > but this case has been wrong before: negative values are not allowed > for the modified case.

Re: [Xen-devel] [PATCH] features: declare the Credit2 scheduler as Supported.

[Cc-list trimmed] On Thu, 2016-10-27 at 16:01 +0100, George Dunlap wrote: > On 25/10/16 09:18, Dario Faggioli wrote: > Do you want to send such a patch, or would you prefer it if I tried > to > write something up? > Here:  https://lists.xen.org/archives/html/xen-devel/2016-11/msg00144.html For

[Xen-devel] [xen-unstable-coverity test] 101857: all pass - PUSHED

flight 101857 xen-unstable-coverity real [real] http://logs.test-lab.xenproject.org/osstest/logs/101857/ Perfect :-) All tests in this flight passed as required version targeted for testing: xen 496673a2ada93c201fbe1cc83146c8bd8e79169d baseline version: xen

Re: [Xen-devel] xc_hvm_inject_trap() races

> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 2 November, 2016 12:05 > To: Andrei Vlad LUTAS > Cc: rcojoc...@bitdefender.com; andrew.coop...@citrix.com; xen- > de...@lists.xenproject.org; ta...@tklengyel.com > Subject: RE: RE:

[Xen-devel] [PATCH v2] features: declare the Credit2 scheduler as Supported.

Credit2 is available in tree as an "Experimental" scheduler since a few years. Recently, effort started for making it production ready and, eventually, the new Xen's default scheduler. As a consequence of that, it has undergone a greatd deal of development, testing and benchmarking. In fact,

[Xen-devel] [PATCH] hw/xen/xen_pvdev: Include qemu/log.h for qemu_log_vprintf()

Olaf Hering reported a build failure due to an undefined reference to 'qemu_log_vprintf'. Explicitely including qemu/log.h seems to fix the issue. Signed-off-by: Thomas Huth --- hw/xen/xen_pvdev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [Xen-devel] [PATCH 0/2] Fix Xen boot on XGene

Hi Stefano, On 01/11/2016 19:29, Stefano Stabellini wrote: On Mon, 31 Oct 2016, Julien Grall wrote: Hi Stefano, On 26/10/16 23:12, Stefano Stabellini wrote: On Wed, 26 Oct 2016, Julien Grall wrote: Hi, Apologize for not respecting the netiquette. On Tue, 25 Oct 2016, 5:49 p.m. Stefano

Re: [Xen-devel] [PATCH for-4.8] flask: build policy in different locations

On Fri, Oct 28, 2016 at 04:17:17PM +0100, Wei Liu wrote: > The flask policy can be build twice -- one for hypervisor and one for > tools. > > Before this patch, everything is built inside tools/flask/policy > directory. It is possible to have a race to write to the same output > file when

Re: [Xen-devel] PCIe devices that are hotplugged after MMIO has been setup fail due to _CRS not covering 64-bit area

>>> On 01.11.16 at 15:39, wrote: > Also I realized that "Range Size and Alignment Requirement" aren't meet > with the code I wrote - as the size (2^n) must be aligned on the > 2^n boundary, and that is certainly not meet. Yes, this would better be obeyed to. > Anyhow the

Re: [Xen-devel] [PATCH v2] build: make debug option affect tools only

On Wed, Nov 02, 2016 at 02:53:32AM -0600, Jan Beulich wrote: > >>> On 01.11.16 at 20:22, wrote: > > The debug option in Config.mk affects hypervisor, tools and stubdom by > > appending different flags to CFLAGS. Mini-os under extra is not > > affected because it already has

Re: [Xen-devel] Maximum number of vcpus for HVM?

On 02/11/16 09:36, Juergen Gross wrote: > According to > > https://wiki.xenproject.org/wiki/Xen_Project_Release_Features > > HVM guests can have up to 256 vcpus. The definition in > > include/public/hvm/hvm_info_table.h: > > /* Maximum we can support with current vLAPIC ID mapping. */ > #define

Re: [Xen-devel] xc_hvm_inject_trap() races

On 11/02/2016 11:05 AM, Tamas K Lengyel wrote: > On Nov 2, 2016 09:57, "Razvan Cojocaru" > wrote: >> >> On 11/02/2016 10:49 AM, Jan Beulich wrote: >> > The fact that {vmx,svm}_inject_trap() combine the new exception >> > with an

Re: [Xen-devel] Maximum number of vcpus for HVM?

On 02/11/16 10:59, Jan Beulich wrote: On 02.11.16 at 10:36, wrote: >> According to >> >> https://wiki.xenproject.org/wiki/Xen_Project_Release_Features >> >> HVM guests can have up to 256 vcpus. The definition in >> >> include/public/hvm/hvm_info_table.h: >> >> /* Maximum we

Re: [Xen-devel] xc_hvm_inject_trap() races

>>> On 02.11.16 at 10:53, wrote: >> From: Jan Beulich [mailto:jbeul...@suse.com] >> Sent: 2 November, 2016 11:38 >> >>> On 02.11.16 at 10:13, wrote: >> >> From: Jan Beulich [mailto:jbeul...@suse.com] >> >> Sent: 2 November, 2016 10:50 >> >> >>> On

Re: [Xen-devel] xc_hvm_inject_trap() races

>>> On 02.11.16 at 10:38, wrote: > With some HVI re-engineering I think I may be able to make everything work if > the existing API would return an error in case it cannot inject the #PF. > Would that be possible? As said in another reply - at the time of the hypercall

Re: [Xen-devel] Maximum number of vcpus for HVM?

>>> On 02.11.16 at 10:36, wrote: > According to > > https://wiki.xenproject.org/wiki/Xen_Project_Release_Features > > HVM guests can have up to 256 vcpus. The definition in > > include/public/hvm/hvm_info_table.h: > > /* Maximum we can support with current vLAPIC ID mapping.

Re: [Xen-devel] xc_hvm_inject_trap() races

> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 2 November, 2016 11:38 > To: rcojoc...@bitdefender.com; Andrei Vlad LUTAS > > Cc: andrew.coop...@citrix.com; xen-de...@lists.xenproject.org; > ta...@tklengyel.com > Subject: RE: RE:

[Xen-devel] [distros-debian-squeeze test] 67978: tolerable FAIL

flight 67978 distros-debian-squeeze real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/67978/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-amd64-amd64-squeeze-netboot-pygrub 9 debian-di-install fail like 67937

Re: [Xen-devel] xc_hvm_inject_trap() races

> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 2 November, 2016 11:31 > To: Razvan Cojocaru > Cc: Andrei Vlad LUTAS ; > andrew.coop...@citrix.com; xen-de...@lists.xenproject.org; > ta...@tklengyel.com >

Re: [Xen-devel] xc_hvm_inject_trap() races

>>> On 02.11.16 at 10:13, wrote: >> From: Jan Beulich [mailto:jbeul...@suse.com] >> Sent: 2 November, 2016 10:50 >> >>> On 01.11.16 at 23:17, wrote: >> > We don't really care when and how the #PF is handled. We don't care if >> > the page is paged

[Xen-devel] Maximum number of vcpus for HVM?

According to https://wiki.xenproject.org/wiki/Xen_Project_Release_Features HVM guests can have up to 256 vcpus. The definition in include/public/hvm/hvm_info_table.h: /* Maximum we can support with current vLAPIC ID mapping. */ #define HVM_MAX_VCPUS128 and its usage in

Re: [Xen-devel] xc_hvm_inject_trap() races

>>> On 02.11.16 at 10:11, wrote: > On 11/02/2016 11:05 AM, Jan Beulich wrote: > On 02.11.16 at 09:57, wrote: >>> On 11/02/2016 10:49 AM, Jan Beulich wrote: The fact that {vmx,svm}_inject_trap() combine the new exception with an

Re: [Xen-devel] xc_hvm_inject_trap() races

> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 2 November, 2016 10:50 > To: rcojoc...@bitdefender.com; Andrei Vlad LUTAS > > Cc: andrew.coop...@citrix.com; xen-de...@lists.xenproject.org; > ta...@tklengyel.com > Subject: RE: RE:

Re: [Xen-devel] xc_hvm_inject_trap() races

On 11/02/2016 11:05 AM, Jan Beulich wrote: On 02.11.16 at 09:57, wrote: >> On 11/02/2016 10:49 AM, Jan Beulich wrote: >>> The fact that {vmx,svm}_inject_trap() combine the new exception >>> with an already injected one (and blindly discard events other than >>> hw

Re: [Xen-devel] xc_hvm_inject_trap() races

On Nov 2, 2016 09:57, "Razvan Cojocaru" wrote: > > On 11/02/2016 10:49 AM, Jan Beulich wrote: > > The fact that {vmx,svm}_inject_trap() combine the new exception > > with an already injected one (and blindly discard events other than > > hw exceptions), otoh, looks like

Re: [Xen-devel] xc_hvm_inject_trap() races

>>> On 02.11.16 at 09:57, wrote: > On 11/02/2016 10:49 AM, Jan Beulich wrote: >> The fact that {vmx,svm}_inject_trap() combine the new exception >> with an already injected one (and blindly discard events other than >> hw exceptions), otoh, looks like indeed wants to be

Re: [Xen-devel] [PATCH for-4.8 v2] tools/tests/x86_emulator: Pass -no-pie -fno-pic to gcc on x86_32

>>> On 01.11.16 at 19:00, wrote: > --- a/tools/tests/x86_emulator/Makefile > +++ b/tools/tests/x86_emulator/Makefile > @@ -45,6 +45,10 @@ x86_emulate/x86_emulate.c x86_emulate/x86_emulate.h: > > HOSTCFLAGS += $(CFLAGS_xeninclude) > > +ifeq ($(XEN_TARGET_ARCH),x86_32)

Re: [Xen-devel] Xen on Qualcomm

Hi, I am trying to run Xen on Qualcomm 410 platform. I have come across below link https://lists.xenproject.org/archives/html/xen-devel/2016-03/msg03144.html which suggest a patch to fix Xen crashes on Qualcomm Technology, So does anyone has any information on the post support which Qualcomm

Re: [Xen-devel] xc_hvm_inject_trap() races

On 11/02/2016 10:49 AM, Jan Beulich wrote: > The fact that {vmx,svm}_inject_trap() combine the new exception > with an already injected one (and blindly discard events other than > hw exceptions), otoh, looks like indeed wants to be controllable by > the caller: When the event comes from the

Re: [Xen-devel] [PATCH v2] build: make debug option affect tools only

>>> On 01.11.16 at 20:22, wrote: > The debug option in Config.mk affects hypervisor, tools and stubdom by > appending different flags to CFLAGS. Mini-os under extra is not > affected because it already has its own build system when it is > separated from xen.git. > > It is

Re: [Xen-devel] xc_hvm_inject_trap() races

>>> On 01.11.16 at 23:17, wrote: > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 1 November, 2016 18:40 Andrei Vlad LUTAS 11/01/16 5:13 PM >>> >>>First of all, to answer your original question: the injection decision >>>is made when the

  1   2   >