[Xen-devel] [ovmf test] 95355: regressions - FAIL

flight 95355 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/95355/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail REGR. vs. 94748

[Xen-devel] [xen-unstable test] 95353: tolerable FAIL

flight 95353 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/95353/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail in 95281 pass in 95353 test-armhf-armhf-xl 15

Re: [Xen-devel] [RFC v2] xen/arm: build: add missed dependency for head.S [and 1 more messages]

Hi, On 8 June 2016 at 00:24, Wei Liu wrote: > On Tue, Jun 07, 2016 at 05:01:35PM +0100, Ian Jackson wrote: >> Wei Chen writes ("[RFC v2] xen/arm: build: add missed dependency for >> head.S"): >> > In current Xen build rules, the build system will only check the >> >

Re: [Xen-devel] [RFC v2] xen/arm: build: add missed dependency for head.S

On 7 June 2016 at 21:18, Konrad Rzeszutek Wilk wrote: > On Tue, Jun 07, 2016 at 12:34:43PM +0800, Wei Chen wrote: >> In current Xen build rules, the build system will only check the >> dependencies in current folder and obj-y generated dependencies >> in other folder. >>

Re: [Xen-devel] live migration from new platform to old platform

> -Original Message- > From: Andrew Cooper [mailto:andrew.coop...@citrix.com] > Sent: Tuesday, June 7, 2016 5:47 PM > To: Hao, Xudong ; Xen-devel de...@lists.xenproject.org> > Cc: Zhang, Haozhong ; Wei Liu > > Subject:

[Xen-devel] [qemu-upstream-4.3-testing test] 95369: trouble: blocked/broken

flight 95369 qemu-upstream-4.3-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/95369/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 3 host-install(3) broken

Re: [Xen-devel] [RFC for-4.8 v2 6/7] xen/device-tree: Add an mmio-sram bus

On Mon, Jun 06, 2016 at 07:05:20PM +0100, Julien Grall wrote: > Hi Edgar, > > On 03/06/16 14:29, Edgar E. Iglesias wrote: > >From: "Edgar E. Iglesias" > > > >Add an mmio-sram bus that prevents sram sub areas from > >being re-mapped. These sub-areas describe allocations

[Xen-devel] [PATCH for-4.7 1/1] xen/arm: Rename map_regions_rw_cache and use p2m.default_access

From: "Edgar E. Iglesias" Rename map_regions_rw_cache to map_regions_cache and make it use p2m.default_access. Suggested-by: Julien Grall Signed-off-by: Edgar E. Iglesias --- xen/arch/arm/domain_build.c | 16

[Xen-devel] [libvirt test] 95358: tolerable FAIL - PUSHED

flight 95358 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/95358/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt-xsm 12 migrate-support-checkfail never pass test-armhf-armhf-libvirt-xsm 14

Re: [Xen-devel] [RFC for-4.8 v2 2/7] xen/arm: Rename and generalize un/map_regions_rw_cache

On Mon, Jun 06, 2016 at 06:55:30PM +0100, Julien Grall wrote: > Hi Edgar, > > On 03/06/16 14:29, Edgar E. Iglesias wrote: > >From: "Edgar E. Iglesias" > > > >Rename and generalize un/map_regions_rw_cache into > >un/map_regions. > > I would name it map_regions_mattr

Re: [Xen-devel] libxenvchan license (lGPLv2.1) and xen/include/public/COPYING license?

On Tue, Jun 07, 2016 at 04:54:42PM +0100, Ian Jackson wrote: > Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] libxenvchan license (lGPLv2.1) > and xen/include/public/COPYING license?"): > > On Mon, Jun 06, 2016 at 05:36:23PM -0400, Konrad Rzeszutek Wilk wrote: > > > I picked the list of people on

Re: [Xen-devel] [RFC for-4.8 v2 4/7] xen/device-tree: Make dt_match_node match props

On Mon, Jun 06, 2016 at 06:39:39PM +0100, Julien Grall wrote: > Hi Edgar, > > On 03/06/16 14:29, Edgar E. Iglesias wrote: > >From: "Edgar E. Iglesias" > > > >Make dt_match_node match for existing properties. > >We only search for the existance of the properties, not >

Re: [Xen-devel] [RFC for-4.8 v2 1/7] xen/arm: Add MATTR_MEM_NC for normal non-cacheable memory

On Mon, Jun 06, 2016 at 06:23:47PM +0100, Julien Grall wrote: > Hi Edgar, > > On 03/06/16 14:29, Edgar E. Iglesias wrote: > >From: "Edgar E. Iglesias" > > > >Add the MATTR_MEM_NC macro describing normal non-cacheable memory. > > > >Signed-off-by: Edgar E. Iglesias

[Xen-devel] [qemu-mainline test] 95352: regressions - FAIL

flight 95352 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/95352/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-freebsd10-amd64 10 guest-startfail REGR. vs. 94856

Re: [Xen-devel] [PATCH] [RFC] xsm: add a default policy to .init.data

On Mon, May 23, 2016 at 10:51:29AM -0400, Daniel De Graaf wrote: > This includes the policy in tools/flask/policy in the hypervisor so that > the bootloader does not need to load a policy to get sane behavior from > an XSM-enabled hypervisor. > > RFC because this adds a binding between xen's

Re: [Xen-devel] [PATCH 5/5] flask/policy: comment out unused xenstore example

On 06/07/2016 04:02 PM, Konrad Rzeszutek Wilk wrote: On Tue, Jun 07, 2016 at 03:51:20PM -0400, Daniel De Graaf wrote: On 06/07/2016 03:45 PM, Konrad Rzeszutek Wilk wrote: On Mon, May 23, 2016 at 11:05:33AM -0400, Daniel De Graaf wrote: Signed-off-by: Daniel De Graaf

Re: [Xen-devel] [PATCH 5/5] flask/policy: comment out unused xenstore example

On Tue, Jun 07, 2016 at 03:51:20PM -0400, Daniel De Graaf wrote: > On 06/07/2016 03:45 PM, Konrad Rzeszutek Wilk wrote: > >On Mon, May 23, 2016 at 11:05:33AM -0400, Daniel De Graaf wrote: > >>Signed-off-by: Daniel De Graaf > > > >Would it be good to include in the

Re: [Xen-devel] [PATCH 4/5] flask/policy: xenstore stubdom policy

On Tue, Jun 07, 2016 at 03:48:02PM -0400, Daniel De Graaf wrote: > On 06/07/2016 03:44 PM, Konrad Rzeszutek Wilk wrote: > >On Mon, May 23, 2016 at 11:05:32AM -0400, Daniel De Graaf wrote: > >>This adds the xenstore_t type to the example policy for use by a > >>xenstore stub domain. > > > >Is there

Re: [Xen-devel] [PATCH 1/5] flask/policy: split into modules

On Tue, Jun 07, 2016 at 03:39:59PM -0400, Daniel De Graaf wrote: > On 06/07/2016 03:22 PM, Konrad Rzeszutek Wilk wrote: > >On Mon, May 23, 2016 at 11:05:29AM -0400, Daniel De Graaf wrote: > >>This makes it easier to enable or disable parts of the XSM policy. > >> > > > >Hey Daniel, > > > >I am no

Re: [Xen-devel] [PATCH 5/5] flask/policy: comment out unused xenstore example

On 06/07/2016 03:45 PM, Konrad Rzeszutek Wilk wrote: On Mon, May 23, 2016 at 11:05:33AM -0400, Daniel De Graaf wrote: Signed-off-by: Daniel De Graaf Would it be good to include in the description something like: "You should be using the xenstore stubdomain".? Thanks.

Re: [Xen-devel] [PATCH 4/5] flask/policy: xenstore stubdom policy

On 06/07/2016 03:44 PM, Konrad Rzeszutek Wilk wrote: On Mon, May 23, 2016 at 11:05:32AM -0400, Daniel De Graaf wrote: This adds the xenstore_t type to the example policy for use by a xenstore stub domain. Is there a link somewhere or docs that oultines how to how create/build such stub

Re: [Xen-devel] [PATCH 5/5] flask/policy: comment out unused xenstore example

On Mon, May 23, 2016 at 11:05:33AM -0400, Daniel De Graaf wrote: > Signed-off-by: Daniel De Graaf Would it be good to include in the description something like: "You should be using the xenstore stubdomain".? Thanks. > --- > tools/flask/policy/policy/access_vectors |

Re: [Xen-devel] [PATCH 4/5] flask/policy: xenstore stubdom policy

On Mon, May 23, 2016 at 11:05:32AM -0400, Daniel De Graaf wrote: > This adds the xenstore_t type to the example policy for use by a > xenstore stub domain. Is there a link somewhere or docs that oultines how to how create/build such stub domain? The docs/misc/stubdom.txt sadly does not have any

Re: [Xen-devel] [PATCH 3/5] flask/policy: Remove unused support for binary modules

On Mon, May 23, 2016 at 11:05:31AM -0400, Daniel De Graaf wrote: > Signed-off-by: Daniel De Graaf Reviewed-by: Konrad Rzeszutek Wilk with my very limited knowledge of the policy language. But it just looks to delete a lot and copy-n-paste the

Re: [Xen-devel] [PATCH 1/5] flask/policy: split into modules

On 06/07/2016 03:22 PM, Konrad Rzeszutek Wilk wrote: On Mon, May 23, 2016 at 11:05:29AM -0400, Daniel De Graaf wrote: This makes it easier to enable or disable parts of the XSM policy. Hey Daniel, I am no expert on this so please take it with a grain of salt. That can actually be helpful

Re: [Xen-devel] [PATCH 2/5] flask/policy: move user definitions and constraints into modules

On Mon, May 23, 2016 at 11:05:30AM -0400, Daniel De Graaf wrote: > This also renames the example users created by vm_role. Hey! Thank you for posting this. > > Signed-off-by: Daniel De Graaf > --- > docs/misc/xsm-flask.txt| 34 >

Re: [Xen-devel] [PATCH 1/5] flask/policy: split into modules

On Mon, May 23, 2016 at 11:05:29AM -0400, Daniel De Graaf wrote: > This makes it easier to enable or disable parts of the XSM policy. > Hey Daniel, I am no expert on this so please take it with a grain of salt. .. snip.. > diff --git a/tools/flask/policy/modules/default_role.te >

Re: [Xen-devel] 4.7 qemu regression: HVM guests fail to boot from xvda

On Fri, Jun 03, Ian Jackson wrote: > There are two problems with this `hdtype' approach. > > Firstly, it is global. That is, it applies to all disks of the > particular guest. But then maybe we don't care about that because > this anomalous major-number-stealing behaviour is probably per-guest

[Xen-devel] [PATCH V7 1/3] drivers/pl011: Don't configure baudrate

The default baud and clock_hz configuration parameters are hardcoded (commit 60ff980995008caf) for Versatile Express. Other platforms, these default values may not be valid and might cause problems by programming registers IBRD and FBRD incorrectly. So, removing driver logic that sets the

[Xen-devel] [PATCH V7 2/3] drivers/pl011: Use combination of UARTRIS and UARTMSC instead of UARTMIS

The Masked interrupt status register (UARTMIS) is not described in ARM SBSA 2.x document. Anding of two registers UARTMSC and UARTRIS values gives the same information as register UARTMIS. UARTRIS, UARTMSC and UARTMIS definitions are found in PrimeCell UART PL011 (Revision: r1p4). - 3.3.10

[Xen-devel] [PATCH V7 3/3] arm/acpi: Add Server Base System Architecture UART support

The ARM Server Base System Architecture describes a generic UART interface. It doesn't support clock control registers, modem control, DMA and hardware flow control features. So, extend the driver probe() to handle SBSA interface and skip the accessing PL011 registers that are not described in

Re: [Xen-devel] [RFC 0/8] xen/arm: acpi: Support SPIs routing

Hi Julien, Sure, I'll test this patchset on Qualcomm Technologies QDF2XXX platform and update results. On 06/07/2016 11:48 AM, Julien Grall wrote: > Hi all, > > Currently, Xen does not route SPIs to DOM0 when ACPI is inuse after > the functionality has been reverted in Xen 4.7 by commit

[Xen-devel] [PATCH for-4.7] docs/livepatch: Update URL to livepatch-build-tools.git

.. in the design document. The official location is: git://xenbits.xen.org/livepatch-builds-tools.git Wiki is also updated with this URL. Signed-off-by: Konrad Rzeszutek Wilk --- Cc: Andrew Cooper Cc: George Dunlap

Re: [Xen-devel] Remaining patches for 4.7 and anticipated release date

On Tue, Jun 07, 2016 at 12:43:16PM -0400, Konrad Rzeszutek Wilk wrote: > On June 7, 2016 12:22:54 PM EDT, Wei Liu wrote: > >Committers, > > > >I have some patches outstanding. Here is the list: > > > >1. xen/arm: build: add missed dependency for head.S (either v1 or v2) > >2.

Re: [Xen-devel] [PATCH for-4.7] travis: drop broken LLVM repos

On Tue, Jun 07, 2016 at 01:09:04PM -0400, Doug Goldstein wrote: > On 6/7/16 12:20 PM, Wei Liu wrote: > > On Tue, Jun 07, 2016 at 12:08:52PM -0400, Doug Goldstein wrote: > >> LLVM repos are currently down so drop them from being installed so we > >> can get some testing back. > >> --- > >>

Re: [Xen-devel] [PATCH v3 09/16] xen/arm: Introduce alternative runtime patching

> + > +/* > + * We might be patching the stop_machine state machine, so implement a > + * really simple polling protocol here. > + */ > +static int __apply_alternatives_multi_stop(void *unused) > +{ > +static int patched = 0; > +struct alt_region region = { > +.begin =

Re: [Xen-devel] [PATCH for-4.7] travis: drop broken LLVM repos

On 6/7/16 12:20 PM, Wei Liu wrote: > On Tue, Jun 07, 2016 at 12:08:52PM -0400, Doug Goldstein wrote: >> LLVM repos are currently down so drop them from being installed so we >> can get some testing back. >> --- >> .travis.yml | 2 -- >> 1 file changed, 2 deletions(-) >> >> diff --git

Re: [Xen-devel] [PATCH for-4.7] travis: drop broken LLVM repos

On 6/7/16 12:17 PM, Ian Jackson wrote: > Doug Goldstein writes ("[PATCH for-4.7] travis: drop broken LLVM repos"): >> LLVM repos are currently down so drop them from being installed so we >> can get some testing back. > > This is unfortunate churn to be having in our tree. I'm happy for > this

Re: [Xen-devel] [PATCH 3/3] libxl: update vcpus bitmap in retrieved guest config

On Tue, 2016-06-07 at 17:46 +0100, Wei Liu wrote: > > > I agree it would be good to set the exact bits though -- if you > > > can > > > tell > > > me which field to test.  > > > > > Perhaps at least mention something about all this either in a > > comment > > or in the changelog? > > > What

[Xen-devel] [RFC 4/8] xen/arm: gic: set_type: Pass the type in parameter rather than in desc->arch.type

A follow-up patch will not store the type in desc->arch.type. Also, the callback prototype is more logical. Signed-off-by: Julien Grall --- xen/arch/arm/gic-v2.c | 3 +-- xen/arch/arm/gic-v3.c | 3 +-- xen/arch/arm/gic.c| 9 -

[Xen-devel] [RFC 5/8] xen/arm: gic: Document how gic_set_irq_type should be called

Changing the value of Int_config is UNPREDICTABLE when the corresponding interrupt is not disabled. The driver is assuming the interrupt will be disabled by the caller of gic_set_irq_type. Add an ASSERT to ensure it. Signed-off-by: Julien Grall --- xen/arch/arm/gic.c | 6

[Xen-devel] [RFC 0/8] xen/arm: acpi: Support SPIs routing

Hi all, Currently, Xen does not route SPIs to DOM0 when ACPI is inuse after the functionality has been reverted in Xen 4.7 by commit 909bd14. In the previous approach, the SPIs was routed when DOM0 was writing into ISENABLER. However, this has resulted to deadlock (see more details in [1]) as

[Xen-devel] [RFC 6/8] Revert "xen/arm: warn the user that we cannot route SPIs to Dom0 on ACPI"

This reverts commit f91c84edebe67296e4051af055dbf0adafb13a37. SPI routing for ACPI support will be added in a follow-up patch. Signed-off-by: Julien Grall --- xen/arch/arm/vgic.c | 15 --- 1 file changed, 15 deletions(-) diff --git a/xen/arch/arm/vgic.c

[Xen-devel] [RFC 3/8] xen/arm: gic: split set_irq_properties

The callback set_irq_properties will configure the GIC for a specific IRQ with the type and the priority. In a follow-up patch, Xen will configure the type and the priority at different stage of the routing. So split it in 2 separate callbacks. At the same time, move the ASSERT to check the

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

flight 95378 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/95378/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass test-armhf-armhf-xl 12

[Xen-devel] [RFC 1/8] xen/arm: gic: Consolidate the IRQ affinity set in a single place

The code to set the IRQ affinity is duplicated: once in gicv{2,3}_set_properties and the other is gicv{2,3}_irq_set_affinity. Remove the code from gicv{2,3}_set_properties and call directly the affinity set helper from the common code. Signed-off-by: Julien Grall ---

[Xen-devel] [RFC 7/8] xen/arm: Allow DOM0 to set the irq type when ACPI is inuse

The function route_irq_to_guest mandates the IRQ type, stored in desc->arch.type, to be valid. However, in case of ACPI, these information is not part of the static tables. Therefore Xen needs to rely on DOM0 to provide a valid type based on the firmware tables. A new helper,

[Xen-devel] [RFC 8/8] xen/arm: acpi: route all unused IRQs to DOM0

It is not possible to know which IRQs will be used by DOM0 when ACPI is inuse. The approach implemented by this patch, will route all unused IRQs to DOM0 before it has booted. The number of IRQs routed is based on the maximum SPIs supported by the hardware (up to ~1000). However, some of them

[Xen-devel] [RFC 2/8] xen/arm: gic: Do not configure affinity for guest IRQ during routing

The affinity of a guest IRQ is set every time the guest enable it (see vgic_enable_irqs). It is not necessary to set the affinity when the IRQ is routed to the guest because Xen will never receive the IRQ until it hass been enabled by the guest. Signed-off-by: Julien grall

Re: [Xen-devel] [PATCH 3/3] libxl: update vcpus bitmap in retrieved guest config

On Tue, Jun 07, 2016 at 06:22:27PM +0200, Dario Faggioli wrote: > On Tue, 2016-06-07 at 17:03 +0100, Wei Liu wrote: > > On Tue, Jun 07, 2016 at 03:45:29PM +0100, Anthony PERARD wrote: > > >  > > > > --- a/tools/libxl/libxl.c > > > > +++ b/tools/libxl/libxl.c > > > > @@ -7222,6 +7222,57 @@ void

[Xen-devel] [xen-4.6-testing test] 95346: trouble: broken/fail/pass

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

Re: [Xen-devel] Remaining patches for 4.7 and anticipated release date

On June 7, 2016 12:22:54 PM EDT, Wei Liu wrote: >Committers, > >I have some patches outstanding. Here is the list: > >1. xen/arm: build: add missed dependency for head.S (either v1 or v2) >2. x86/mce: handle reserved domain ID in XEN_MC_msrinject >3. Revert "x86/hvm: add

Re: [Xen-devel] [PATCH 3/3] libxl: update vcpus bitmap in retrieved guest config

On Tue, Jun 07, 2016 at 05:36:05PM +0100, Anthony PERARD wrote: > On Tue, Jun 07, 2016 at 05:03:07PM +0100, Wei Liu wrote: > > On Tue, Jun 07, 2016 at 03:45:29PM +0100, Anthony PERARD wrote: > > > On Tue, Jun 07, 2016 at 12:24:02PM +0100, Wei Liu wrote: > > > > ... because the available vcpu

Re: [Xen-devel] [PATCH 3/3] libxl: update vcpus bitmap in retrieved guest config

On Tue, Jun 07, 2016 at 05:03:07PM +0100, Wei Liu wrote: > On Tue, Jun 07, 2016 at 03:45:29PM +0100, Anthony PERARD wrote: > > On Tue, Jun 07, 2016 at 12:24:02PM +0100, Wei Liu wrote: > > > ... because the available vcpu bitmap can change during domain life time > > > due to cpu hotplug and

Re: [Xen-devel] [PATCH OSSTEST v2 0/2] Test booting hvm guest with empty cdrom drive

On Tue, Jun 07, 2016 at 02:58:05PM +0100, Ian Jackson wrote: > Wei Liu writes ("[PATCH OSSTEST v2 0/2] Test booting hvm guest with empty > cdrom drive"): > > This can only go in after the bug is fixed and possibly backported to all > > the > > trees we care about. It won't pass osstest self

Re: [Xen-devel] [RFC v2] xen/arm: build: add missed dependency for head.S [and 1 more messages]

On Tue, Jun 07, 2016 at 05:01:35PM +0100, Ian Jackson wrote: > Wei Chen writes ("[RFC v2] xen/arm: build: add missed dependency for head.S"): > > In current Xen build rules, the build system will only check the > > dependencies in current folder and obj-y generated dependencies > > in other

[Xen-devel] Remaining patches for 4.7 and anticipated release date

Committers, I have some patches outstanding. Here is the list: 1. xen/arm: build: add missed dependency for head.S (either v1 or v2) 2. x86/mce: handle reserved domain ID in XEN_MC_msrinject 3. Revert "x86/hvm: add support for pcommit instruction" 4. xen/serial: Fix incorrect length of strncmp

Re: [Xen-devel] [PATCH 3/3] libxl: update vcpus bitmap in retrieved guest config

On Tue, 2016-06-07 at 17:03 +0100, Wei Liu wrote: > On Tue, Jun 07, 2016 at 03:45:29PM +0100, Anthony PERARD wrote: > >  > > > --- a/tools/libxl/libxl.c > > > +++ b/tools/libxl/libxl.c > > > @@ -7222,6 +7222,57 @@ void libxl_mac_copy(libxl_ctx *ctx, > > > libxl_mac *dst, libxl_mac *src) > > >  

Re: [Xen-devel] [PATCH for-4.7] travis: drop broken LLVM repos

On Tue, Jun 07, 2016 at 12:08:52PM -0400, Doug Goldstein wrote: > LLVM repos are currently down so drop them from being installed so we > can get some testing back. > --- > .travis.yml | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/.travis.yml b/.travis.yml > index d2e1bec..5bae60d

Re: [Xen-devel] [PATCH for-4.7] travis: drop broken LLVM repos

Doug Goldstein writes ("[PATCH for-4.7] travis: drop broken LLVM repos"): > LLVM repos are currently down so drop them from being installed so we > can get some testing back. This is unfortunate churn to be having in our tree. I'm happy for this removal commit to go in, but isn't there a way to

[Xen-devel] [PATCH v3 03/16] xen/arm: Add macros to handle the MIDR

Add new macros to easily get different parts of the register and to check if a given MIDR match a CPU model range. The latter will be really useful to handle errata later. The macros have been imported from the header arch/arm64/include/asm/cputype.h in Linux v4.6-rc3. Also remove MIDR_MASK

[Xen-devel] [PATCH v3 01/16] xen/arm: Makefile: Sort the entries alphabetically

Signed-off-by: Julien Grall Acked-by: Stefano Stabellini --- Changes in v3: - Rebase on staging (conflict with s/xsplice/livepatch). Changes in v2: - Add Stefano's acked-by --- xen/arch/arm/Makefile | 40

[Xen-devel] [PATCH v3 15/16] xen/arm: traps: Don't inject a fault if the translation VA -> IPA fails

Based on ARM ARM (D4.5.3 in ARM DDI 0486A and B3.12.7 in ARM DDI 0406C.c), a Stage 1 translation error has priority over a Stage 2 translation error. Therefore gva_to_ipa can only fail if another vCPU is playing with the page table. Rather than injecting a custom fault, replay the instruction

[Xen-devel] [PATCH v3 09/16] xen/arm: Introduce alternative runtime patching

Some of the processor erratum will require to modify code sequence. As those modifications may impact the performance, they should only be enabled on affected cores. Furthermore, Xen may also want to take advantage of new hardware features coming up with v8.1 and v8.2. This patch adds an

[Xen-devel] [PATCH v3 13/16] xen/arm: arm64: Add Cortex-A53 cache errata workaround

The ARM errata 819472, 827319 and 824069 define the same workaround for these hardware issues in certain Cortex-A53 parts. The cache instructions "dc cvac" and "dc cvau" need to be upgraded to "dc civac". Use the alternative framework to replace those instructions only on affected cores. Whilst

[Xen-devel] [PATCH v3 02/16] xen/arm: Include the header asm-arm/system.h in asm-arm/page.h

The header asm-arm/page.h makes use of the macro dsb defined in the header asm-arm/system.h. Currently, the includer has to specify both of them. This can be avoided by including asm-arm/system.h in asm-arm/page.h. Signed-off-by: Julien Grall Acked-by: Stefano Stabellini

Re: [Xen-devel] [PATCH 3/3] libxl: update vcpus bitmap in retrieved guest config

On Tue, Jun 07, 2016 at 03:45:29PM +0100, Anthony PERARD wrote: > On Tue, Jun 07, 2016 at 12:24:02PM +0100, Wei Liu wrote: > > ... because the available vcpu bitmap can change during domain life time > > due to cpu hotplug and unplug. > > > > For QEMU upstream, we interrogate QEMU for the number

[Xen-devel] [PATCH for-4.7] travis: drop broken LLVM repos

LLVM repos are currently down so drop them from being installed so we can get some testing back. --- .travis.yml | 2 -- 1 file changed, 2 deletions(-) diff --git a/.travis.yml b/.travis.yml index d2e1bec..5bae60d 100644 --- a/.travis.yml +++ b/.travis.yml @@ -40,7 +40,6 @@ addons: apt:

Re: [Xen-devel] [PATCH v5 5/9] monitor: ARM SMC events

On Jun 7, 2016 04:30, "Stefano Stabellini" wrote: > > On Tue, 7 Jun 2016, Jan Beulich wrote: > > >>> On 06.06.16 at 18:38, wrote: > > > On 06/06/16 17:14, Tamas K Lengyel wrote: > > >> On Mon, Jun 6, 2016 at 9:56 AM, Tamas K Lengyel

[Xen-devel] [PATCH v3 16/16] xen/arm: arm64: Document Cortex-A57 erratum 834220

The ARM erratum applies to certain revisions of Cortex-A57. The processor may report a Stage 2 translation fault as the result of Stage 1 fault for load crossing a page boundary when there is a permission fault or device memory fault at stage 1 and a translation fault at Stage 2. So Xen needs to

[Xen-devel] [PATCH v3 07/16] xen/arm: arm64: Reserve a brk immediate to fault on purpose

It may not possible to return a proper error when encoding an instruction. Instead, a handcrafted instruction will be returned. Also, provide the encoding for the faulting instruction. Signed-off-by: Julien Grall Acked-by: Stefano Stabellini ---

[Xen-devel] [PATCH v3 06/16] xen/arm: arm64: Move the define BRK_BUG_FRAME into a separate header

New immediates will be defined in the future. To keep track of the immediates allocated, gather all of them in a separate header. Also rename BRK_BUG_FRAME to BKR_BUG_FRAME_IMM. Signed-off-by: Julien Grall Reviewed-by: Stefano Stabellini ---

[Xen-devel] [PATCH v3 12/16] xen/arm: Document the errata implemented in Xen

The new document will help to keep track of each erratum Xen is able to handle. The text is based on the Linux doc in Documents/arm64/silicon-errata.txt. Also list the current errata that Xen is aware of. Signed-off-by: Julien Grall --- Changes in v3: - Fix

[Xen-devel] [PATCH v3 08/16] xen/arm: arm64: Add helpers to decode and encode branch instructions

We may need to update branch instruction when patching Xen. The code has been imported from the files arch/arm64/kernel/insn.c and arch/arm64/include/asm/insn.h in Linux v4.6. Note that only the necessary helpers have been imported. Signed-off-by: Julien Grall Acked-by:

[Xen-devel] [PATCH v3 04/16] xen/arm: Add cpu_hwcap bitmap

This will be used to know if a feature, which Xen cares, is available accross all the CPUs. This code is a light version of arch/arm64/kernel/cpufeature.c from Linux v4.6-rc3. Signed-off-by: Julien Grall Reviewed-by: Stefano Stabellini ---

[Xen-devel] [PATCH v3 10/16] xen/arm: cpufeature: Provide an helper to check if a capability is supported

The CPU capabilities will be set depending on the value found in the CPU registers. This patch provides a generic to go through a set of capabilities and find which one should be enabled. The parameter "info" is used to display the kind of capability updated (e.g workaround, feature...).

[Xen-devel] [PATCH v3 00/16] xen/arm: Introduce alternative runtime patching for ARM64

Hello, Some of the processor errata will require to modify code sequence. As those modifications may impact the performance, they should only be enabled on affected cores. Furthermore, Xen may also want to take advantage of new hardware features coming up with v8.1 and v8.2. The first part of

[Xen-devel] [PATCH v3 11/16] xen/arm: Detect silicon revision and set cap bits accordingly

After each CPU has been started, we iterate through a list of CPU errata to detect CPUs which need from hypervisor code patches. For each bug there is a function which check if that a particular CPU is affected. This needs to be done on every CPUs to cover heterogenous system properly. If a

[Xen-devel] [PATCH v3 14/16] xen/arm: arm64: Add cortex-A57 erratum 832075 workaround

The ARM erratum 832075 applies to certain revisions of Cortex-A57, one of the workarounds is to change device loads into using load-acquire semantics. Use the alternative framework to enable the workaround only on affected cores. Whilst a guest could trigger the deadlock, it can be broken when

[Xen-devel] [PATCH v3 05/16] xen/arm64: Add an helper to invalidate all instruction caches

Signed-off-by: Julien Grall Acked-by: Stefano Stabellini --- Changes in v2: - Add Stefano's acked-by --- xen/include/asm-arm/arm64/page.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/xen/include/asm-arm/arm64/page.h

Re: [Xen-devel] [RFC v2] xen/arm: build: add missed dependency for head.S [and 1 more messages]

Wei Chen writes ("[RFC v2] xen/arm: build: add missed dependency for head.S"): > In current Xen build rules, the build system will only check the > dependencies in current folder and obj-y generated dependencies > in other folder. > > But Makefile may add some objects to ALL_OBJS. These objects

Re: [Xen-devel] Commit moratorium for branching 4.7

On Tue, Jun 07, 2016 at 02:55:39PM +0100, Ian Jackson wrote: > Ian Jackson writes ("Commit moratorium for branching 4.7"): > > At Wei's request, I am starting to branch the tree, so that > > xen-unstable can diverge from the *-4.7 preparation branches. > > > > Please don't commit anything until

Re: [Xen-devel] [libvirt] Questions about virtlogd

On Tue, Jun 07, 2016 at 02:21:17PM +0100, Daniel P. Berrange wrote: > On Tue, Jun 07, 2016 at 01:11:53PM +0100, Wei Liu wrote: > > Hello libvirt maintainers, > > > > Libvirt implements virtlogd in version 1.3 which now handles logging > > for QEMU process. I am wondering if it is possible to make

Re: [Xen-devel] libxenvchan license (lGPLv2.1) and xen/include/public/COPYING license?

Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] libxenvchan license (lGPLv2.1) and xen/include/public/COPYING license?"): > On Mon, Jun 06, 2016 at 05:36:23PM -0400, Konrad Rzeszutek Wilk wrote: > > I picked the list of people on this email from the git log on > > tools/misc/libvchan/ > > (albeit

[Xen-devel] BUG: NOW() seems to (sometimes) go backwards!

Hi, I've been fighting with this during the past few days, while testing and benchmarking some of the modification I'm doing to Credit2. In summary, what I see is NOW() going backwards. The issues shows up when I call NOW() on different pCPUs, and compare the results (which is something the

Re: [Xen-devel] Commit moratorium for branching 4.7

George Dunlap writes ("Re: Commit moratorium for branching 4.7"): > On 07/06/16 15:26, Jan Beulich wrote: > > Perhaps we can use the same model as I think we used last time, > > with the person committing to unstable being responsible to also > > put things applicable to 4.7 there? And with that

Re: [Xen-devel] [PATCH RFC 19/20] acpi: Set HW_REDUCED_ACPI in FADT if IOAPIC is not supported

>>> On 07.06.16 at 17:17, wrote: > On 06/07/2016 10:12 AM, Jan Beulich wrote: > On 07.06.16 at 16:02, wrote: >>> On 06/07/2016 02:06 AM, Jan Beulich wrote: >>> On 06.06.16 at 19:31, wrote: > On

Re: [Xen-devel] [PATCH RFC 19/20] acpi: Set HW_REDUCED_ACPI in FADT if IOAPIC is not supported

On 06/07/2016 10:12 AM, Jan Beulich wrote: On 07.06.16 at 16:02, wrote: >> On 06/07/2016 02:06 AM, Jan Beulich wrote: >> On 06.06.16 at 19:31, wrote: On 06/06/2016 09:38 AM, Jan Beulich wrote: On 06.04.16 at 03:25,

Re: [Xen-devel] Xen 4.7 crash

On 6/7/2016 9:40 AM, Aaron Cornelius wrote: On 6/7/2016 5:53 AM, Ian Jackson wrote: Aaron Cornelius writes ("Re: [Xen-devel] Xen 4.7 crash"): We realized that we had forgotten to remove the domain from the permissions list when the domain is deleted (which would cause the error we saw). The

Re: [Xen-devel] [PATCH RFC 18/20] libxc/acpi: Build ACPI tables for HVMlite guests

>>> On 07.06.16 at 16:47, wrote: > On 06/07/2016 10:10 AM, Jan Beulich wrote: > On 07.06.16 at 15:59, wrote: >>> On 06/07/2016 02:17 AM, Jan Beulich wrote: >>> On 06.06.16 at 18:59, wrote: > On

Re: [Xen-devel] [PATCH RFC 18/20] libxc/acpi: Build ACPI tables for HVMlite guests

On 06/07/2016 10:10 AM, Jan Beulich wrote: On 07.06.16 at 15:59, wrote: >> On 06/07/2016 02:17 AM, Jan Beulich wrote: >> On 06.06.16 at 18:59, wrote: On 06/06/2016 09:29 AM, Jan Beulich wrote: On 06.04.16 at 03:25,

Re: [Xen-devel] [PATCH 3/3] libxl: update vcpus bitmap in retrieved guest config

On Tue, Jun 07, 2016 at 12:24:02PM +0100, Wei Liu wrote: > ... because the available vcpu bitmap can change during domain life time > due to cpu hotplug and unplug. > > For QEMU upstream, we interrogate QEMU for the number of vcpus. For > others, we look directly into xenstore for information. >

Re: [Xen-devel] Commit moratorium for branching 4.7

On 07/06/16 15:26, Jan Beulich wrote: On 07.06.16 at 15:55, wrote: >> Ian Jackson writes ("Commit moratorium for branching 4.7"): >>> At Wei's request, I am starting to branch the tree, so that >>> xen-unstable can diverge from the *-4.7 preparation branches. >>>

Re: [Xen-devel] [PATCH RFC 15/20] acpi: Move ACPI code to xen/common/libacpi

On 06/07/2016 08:24 AM, Roger Pau Monné wrote: > On Mon, Jun 06, 2016 at 12:09:21PM -0400, Boris Ostrovsky wrote: >> On 06/06/2016 09:05 AM, Jan Beulich wrote: >> On 06.04.16 at 03:25, wrote: .gitignore|

Re: [Xen-devel] 4.7 qemu regression: HVM guests fail to boot from xvda

On Tue, Jun 07, George Dunlap wrote: > In every part of the whole system -- in dom0, in the guest, in > everything -- I use xvda; *except* in the parts dealing with the guest > config, where for some reason I mysteriously put 'hda', which ends up > producing an xvda either when booted PV or when

Re: [Xen-devel] Commit moratorium for branching 4.7

>>> On 07.06.16 at 15:55, wrote: > Ian Jackson writes ("Commit moratorium for branching 4.7"): >> At Wei's request, I am starting to branch the tree, so that >> xen-unstable can diverge from the *-4.7 preparation branches. >> >> Please don't commit anything until I'm

Re: [Xen-devel] [PATCH RESEND 00/14] Xen ARM DomU ACPI support

On 06/07/2016 06:54 AM, Julien Grall wrote: > Hello Boris, > > On 06/06/16 17:50, Boris Ostrovsky wrote: >> On 06/06/2016 11:37 AM, Boris Ostrovsky wrote: What I don't want to see is that x86 builds its ACPI table in libxc while ARM builds its in libxl. That would make future merger

Re: [Xen-devel] Basic bare metal ARM domain interface

On 07/06/16 00:31, Ivan Pavic wrote: Hello Julien, Hello Ivan, On Fri, Jun 03, 2016 at 11:23:33AM +0100, Julien Grall wrote: On 02/06/16 20:09, Ivan Pavic wrote: Hello Julien, Hello Ivan, On Thu, Jun 02, 2016 at 12:41:02PM +0100, Julien Grall wrote: Which compiler led to use a

Re: [Xen-devel] [PATCH RESEND 06/14] libxl/arm: Construct ACPI FADT table

On 07/06/16 15:13, Shannon Zhao wrote: On 2016年06月07日 21:17, Julien Grall wrote: Hello Shannon, It just occurred to me that the way to build the ACPI tables, I am not speaking about the value, is very similar to what QEMU does. Yeah, TBH, I really refer to that in QEMU and there is no

Re: [Xen-devel] [PATCH v2 1/2] xen-pciback: return proper values during BAR sizing

>>> On 07.06.16 at 16:06, wrote: > On 06/07/2016 02:30 AM, Jan Beulich wrote: >> Reads following writes with all address bits set to 1 should return all >> changeable address bits as one, not the BAR size (nor, as was the case >> for the upper half of 64-bit BARs, the

  1   2   3   >