flight 84400 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/84400/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 3 host-install(3) broken in 83951 REGR. vs. 66399
build-amd64-rumpuserxen
flight 84435 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/84435/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail
REGR. vs. 65543
test-amd64-i386-
On Sun, Feb 28, Wei Liu wrote:
> If the current set of compiler flags is not good enough, we should
> improve it. I'm afraid having a third set of maintainer mode flags that
> nobody else uses is going to cause us more headache.
There is nothing wrong with the CFLAGS. They are perfect for develop
flight 84379 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/84379/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 59254
build-amd64-rumpuserx
This run is configured for baseline tests only.
flight 44193 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44193/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 15 guest-l
1) What is this patch about?
This patch introduces an new block operation (BLKIF_OP_EXTRA_FLAG).
A request with BLKIF_OP_EXTRA_FLAG set means the following request is an
extra request which is used to pass through SCSI commands.
This is like a simplified version of XEN_NETIF_EXTRA_* in netif.h.
It
VT-d Posted-Interrupts is an enhancement to CPU side Posted-Interrupt.
With VT-d Posted-Interrupts enabled, external interrupts from
direct-assigned devices can be delivered to guests without VMM
intervention when guest is running in non-root mode.
You can find the VT-d Posted-Interrtups Spec. in
Enable VT-d Posted-Interrupts and add a command line
parameter for it.
CC: Jan Beulich
Signed-off-by: Feng Wu
Reviewed-by: Kevin Tian
Acked-by: Jan Beulich
---
docs/misc/xen-command-line.markdown | 9 -
xen/drivers/passthrough/iommu.c | 3 +++
2 files changed, 11 insertions(+), 1
This is the core logic handling for VT-d posted-interrupts. Basically it
deals with how and when to update posted-interrupts during the following
scenarios:
- vCPU is preempted
- vCPU is slept
- vCPU is blocked
When vCPU is preempted/slept, we update the posted-interrupts during
scheduling by intr
On 02/29/16 10:02, Tian, Kevin wrote:
> > From: Jan Beulich [mailto:jbeul...@suse.com]
> > Sent: Friday, February 26, 2016 4:01 PM
> >
> > >>> On 26.02.16 at 05:37, wrote:
> > >> From: Zhang, Haozhong
> > >> Sent: Tuesday, February 23, 2016 10:05 AM
> > >>
> > >> Signed-off-by: Haozhong Zhang
>
On 2016/2/12 6:22, Rafael J. Wysocki wrote:
> On Thursday, February 11, 2016 04:04:14 PM Stefano Stabellini wrote:
>> > On Wed, 10 Feb 2016, Rafael J. Wysocki wrote:
>>> > > On Tuesday, February 09, 2016 11:19:02 AM Stefano Stabellini wrote:
> > > On Mon, 8 Feb 2016, Rafael J. Wysocki wrote:
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Friday, February 26, 2016 4:01 PM
>
> >>> On 26.02.16 at 05:37, wrote:
> >> From: Zhang, Haozhong
> >> Sent: Tuesday, February 23, 2016 10:05 AM
> >>
> >> Signed-off-by: Haozhong Zhang
> >
> > Reviewed-by: Kevin Tian , except:
> >
> >> +
>
flight 84424 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/84424/
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
flight 84347 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/84347/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-rtds 11 guest-startfail in 84228 pass in 84347
test-armhf-armhf-libvirt-qcow2 9 d
This run is configured for baseline tests only.
flight 44192 linux-3.14 real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44192/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-credit2 19 guest-start/debian.repeat f
flight 84351 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/84351/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail
REGR. vs. 65543
test-amd64-i386-
flight 84335 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/84335/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 60684
build-amd6
On Sat, Feb 27, 2016 at 9:30 AM, Wei Liu wrote:
> Commit 7449fb36 ("migration/save: pass checkpointed_stream from libxl to
> libxc ") failed to initialise rc in the error path.
>
> Reported-by: Olaf Hering
> Signed-off-by: Wei Liu
Reviewed and applied.
> ---
> Cc: Konrad Rzeszutek Wilk
> Cc: I
On Sun, Feb 28, 2016 at 02:10:16PM +, Andrew Cooper wrote:
> On 28/02/16 02:01, Doug Goldstein wrote:
> > On 2/27/16 2:14 AM, Olaf Hering wrote:
> >> Current staging fails to compile:
> >>
> >> [ 276s] libxl_dom_save.c: In function 'libxl__domain_save':
> >> [ 276s] libxl_dom_save.c:328:9: er
On 2/28/16 8:10 AM, Andrew Cooper wrote:
> On 28/02/16 02:01, Doug Goldstein wrote:
>> On 2/27/16 2:14 AM, Olaf Hering wrote:
>> The relevant patch is here and still waiting for an ACK:
>>
>> http://lists.xen.org/archives/html/xen-devel/2016-02/msg02715.html
>>
>> Once that gets merged and I can en
The problem wasn't with xen iommu support but kms/drm and i915 driver.
Passing to the kernel i915.preliminary_hw_support=1 fixes it all :)
Thanks
Le sam. 20 févr. 2016 à 22:44, Thierry Laurion
a écrit :
> Le mar. 26 janv. 2016 à 05:52, Jan Beulich a écrit :
>
>> >>> On 25.01.16 at 22:49, wro
The problem wasn't with xen iommu support but kms/drm and i915 driver.
Passing to the kernel i915.preliminary_hw_support=1 fixes it all :)
Thanks
Le mer. 6 janv. 2016 à 22:11, Thierry Laurion a
écrit :
> Nope. That commit is present in 4.6 and results in x200 being able to boot
> xen.
>
> Not
This patch adds ARM support for guest-request monitor vm-events.
Note: on ARM hypercall instruction skipping must be done manually
by the caller. This will probably be changed in a future patch.
Summary of changes:
== Moved to common-side:
* XEN_DOMCTL_MONITOR_EVENT_GUEST_REQUEST handling (moved
flight 44191 distros-debian-stretch real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44191/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-i386-stretch-netboot-pvgrub 9 debian-di-install fail like 38744
test-amd64-amd
flight 84313 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/84313/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 3 host-install(3) broken in 83951 REGR. vs. 66399
build-amd64-rumpuserxen
On 28/02/16 15:47, Wei Liu wrote:
> On Sun, Feb 28, 2016 at 10:39:17AM +0100, Olaf Hering wrote:
>> On Sat, Feb 27, Olaf Hering wrote:
>>
>>> -O2 -Wall
>>> -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
>> I think the cause is the lack of a "maintainer mode", which should
>> enable realworld
On Sun, Feb 28, 2016 at 10:39:17AM +0100, Olaf Hering wrote:
> On Sat, Feb 27, Olaf Hering wrote:
>
> > -O2 -Wall
> > -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
>
> I think the cause is the lack of a "maintainer mode", which should
> enable realworld CFLAGS. Either a new configure knob
This run is configured for baseline tests only.
flight 44190 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44190/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-qemuu-nested-intel 6 xen-boot
On 02/24/16 09:54, Jan Beulich wrote:
> >>> On 24.02.16 at 16:48, wrote:
> > On 02/24/16 07:24, Jan Beulich wrote:
> >> >>> On 24.02.16 at 14:28, wrote:
> >> > On 02/18/16 10:17, Jan Beulich wrote:
> >> >> >>> On 01.02.16 at 06:44, wrote:
> >> >> > 3.3 Guest ACPI Emulation
> >> >> >
> >> >> > 3
On 28/02/16 02:01, Doug Goldstein wrote:
> On 2/27/16 2:14 AM, Olaf Hering wrote:
>> Current staging fails to compile:
>>
>> [ 276s] libxl_dom_save.c: In function 'libxl__domain_save':
>> [ 276s] libxl_dom_save.c:328:9: error: 'rc' may be used uninitialized in
>> this function
>>
>> It was intro
Signed-off-by: Haozhong Zhang
Reviewed-by: Kevin Tian
---
CC: Ian Campbell
CC: Ian Jackson
CC: Jan Beulich
CC: Keir Fraser
CC: Tim Deegan
CC: Kevin Tian
---
docs/man/xl.cfg.pod.5 | 14 +-
docs/misc/tscmode.txt | 21 +
2 files changed, 34 insertions(+), 1
Both VMX and SVM save/load vcpu's TSC when saving/loading vcpu's
context, so this patch moves saving/loading vcpu's TSC to the common
functions hvm_[save|load]_cpu_ctxt().
Signed-off-by: Haozhong Zhang
Acked-by: Jan Beulich
Acked-by: Kevin Tian
Reviewed-by: Boris Ostrovsky
---
CC: Keir Fraser
This patch adds a field tsc_scaling_ratio in struct hvm_domain to record
the per-domain TSC scaling ratio, and sets it in tsc_set_info().
Before setting the per-domain TSC scaling ratio, we check its validity
in tsc_set_info(). If an invalid ratio is given, we will leave the
default value in tsc_s
This patch adds the initialization and setup code for VMX TSC scaling.
Signed-off-by: Haozhong Zhang
Acked-by: Jan Beulich
Acked-by: Kevin Tian
---
CC: Keir Fraser
CC: Jan Beulich
CC: Andrew Cooper
CC: Jun Nakajima
CC: Kevin Tian
---
Changes in v6:
* Adapt to the macro renaming in patch 1
This patch implements a common function hvm_scale_tsc() to scale TSC by
using TSC scaling information collected by architecture code.
Signed-off-by: Haozhong Zhang
---
CC: Keir Fraser
CC: Jan Beulich
CC: Andrew Cooper
CC: Boris Ostrovsky
CC: Suravee Suthikulpanit
CC: Aravind Gopalakrishnan
This patchset adds support for VMX TSC scaling feature which is
available on Intel Skylake Server CPU. The specification of VMX TSC
scaling can be found at
http://www.intel.com/content/www/us/en/processors/timestamp-counter-scaling-virtualization-white-paper.html
VMX TSC scaling allows guest TSC w
flight 84300 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/84300/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 59254
build-amd64-rumpuserx
From: Shannon Zhao
Create STAO table for Dom0. This table is used to tell Dom0 whether it
should ignore UART defined in SPCR table or the ACPI namespace names.
Look at below url for details:
http://wiki.xenproject.org/mediawiki/images/0/02/Status-override-table.pdf
Signed-off-by: Parth Dixit
S
From: Shannon Zhao
Prepare EFI system table for Dom0 to describe the information of UEFI.
Cc: Jan Beulich
Signed-off-by: Parth Dixit
Signed-off-by: Shannon Zhao
---
v4: use already existing xz_crc32_init and xz_crc32
---
xen/arch/arm/domain_build.c | 2 ++
xen/common/efi/boot.c | 44 +
From: Shannon Zhao
Add a new dilivery type:
val[63:56] == 3: val[15:8] is flag: val[7:0] is a PPI.
To the flag, bit 0 stands the interrupt mode is edge(1) or level(0) and
bit 1 stands the interrupt polarity is active low(1) or high(0).
Cc: Jan Beulich
Signed-off-by: Shannon Zhao
---
v4: rebase
From: Parth Dixit
Create a helper function for mapping with cached attributes and
read-only range.
Signed-off-by: Parth Dixit
Signed-off-by: Shannon Zhao
---
v4: use p2m_access_r
---
xen/arch/arm/p2m.c| 26 ++
xen/include/asm-arm/p2m.h | 10 ++
2 files
From: Shannon Zhao
Copy and modify XSDT table before passing it to Dom0. Repalce the entry
value of the copied table. Add a new entry for STAO table as well. And
keep entry value of other reused tables unchanged.
Signed-off-by: Shannon Zhao
Acked-by: Stefano Stabellini
---
xen/arch/arm/domain
From: Parth Dixit
ACPI memory is seperate from conventional memory and should be marked
as reserved while passing to DOM0. Create a new meminfo structure to
store all the acpi tables listed in uefi.
Signed-off-by: Parth Dixit
Signed-off-by: Shannon Zhao
Acked-by: Stefano Stabellini
---
xen/a
From: Shannon Zhao
These patches are Part 4 (and last part) of the previous patch set I
sent which adds ACPI support for arm64 on Xen[1]. Split them as an
individual set for convenient reviewing.
These patches create UEFI and ACPI tables which are mapped to Dom0's
space and add other preparation
From: Shannon Zhao
Copy and modify FADT table before passing it to Dom0. Set PSCI_COMPLIANT
and PSCI_USE_HVC.
Signed-off-by: Shannon Zhao
---
xen/arch/arm/domain_build.c | 43 +++
1 file changed, 43 insertions(+)
diff --git a/xen/arch/arm/domain_build.c
From: Shannon Zhao
Copy RSDP table and replace rsdp->xsdt_physical_address with new address
of XSDT table, so it can point to the right XSDT table.
Signed-off-by: Shannon Zhao
Acked-by: Stefano Stabellini
---
xen/arch/arm/domain_build.c | 36
1 file change
From: Shannon Zhao
Map the UEFI and ACPI tables which we created to non-RAM space in Dom0.
Signed-off-by: Shannon Zhao
---
xen/arch/arm/domain_build.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
index 1ec6271..0
From: Shannon Zhao
Add a new member in gic_hw_operations which is used to creat MADT table
for Dom0.
Signed-off-by: Shannon Zhao
---
xen/arch/arm/gic-v2.c | 34 ++
xen/arch/arm/gic-v3.c | 47 +++
xen/arch/arm/g
From: Shannon Zhao
Copy main MADT table contents and distributor subtable from physical
ACPI MADT table. Make other subtables through the callback of
gic_hw_ops.
Signed-off-by: Shannon Zhao
---
v4: use make_hwdom_madt callback to create MADT
---
xen/arch/arm/domain_build.c | 50 +++
From: Shannon Zhao
Map all other tables to Dom0 using 1:1 mappings.
Signed-off-by: Shannon Zhao
---
v4: fix commit message
---
xen/arch/arm/domain_build.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
i
From: Shannon Zhao
Store the event-channel interrupt number and flag in HVM parameter
HVM_PARAM_CALLBACK_IRQ. Then Dom0 could get it through hypercall
HVMOP_get_param.
Signed-off-by: Shannon Zhao
---
v4: always set HVM_PARAM_CALLBACK_IRQ parameter
---
xen/arch/arm/domain_build.c | 10 +
From: Naresh Bhat
Add ACPI support on arm64 xen hypervisor. Enable EFI support on ARM.
Signed-off-by: Naresh Bhat
Signed-off-by: Shannon Zhao
---
V4: add comments to explain why efi_enabled = 1 needs
---
xen/arch/arm/Kconfig | 1 +
xen/common/efi/runtime.c | 8 ++--
xen/includ
From: Shannon Zhao
It needs to map platform or amba device mmio to Dom0 on ARM. But when
booting with ACPI, it can't get the mmio region in Xen due to lack of
AML interpreter to parse DSDT table. Therefore, let Dom0 call a
hypercall to map mmio region when it adds the devices.
Signed-off-by: Sha
From: Shannon Zhao
It needs to copy and change the contents of some ACPI and EFI tables for
Dom0. Here define a enum for those tables.
Signed-off-by: Parth Dixit
Signed-off-by: Shannon Zhao
---
xen/include/asm-arm/acpi.h | 12
1 file changed, 12 insertions(+)
diff --git a/xen/in
From: Shannon Zhao
Create a DT for Dom0 for ACPI-case only. DT contains minimal required
informations such as Dom0 bootargs, initrd, efi description table and
address of uefi memory table.
Also port the document of this device tree bindings from Linux.
Cc: Jan Beulich
Signed-off-by: Naresh Bha
From: Shannon Zhao
We will create EFI table, memory description table and some of acpi
tables and we're going to map them to kinfo->gnttab_start of Dom0.
Add placeholder for the starting address for loading in DOM0 and the
size of new added tables. Also add a placeholder to store the new
created
From: Shannon Zhao
These tables are aligned with 64bit.
Signed-off-by: Shannon Zhao
---
v4: aligned with 64bit
---
xen/arch/arm/acpi/lib.c| 14 ++
xen/include/asm-arm/acpi.h | 2 ++
2 files changed, 16 insertions(+)
diff --git a/xen/arch/arm/acpi/lib.c b/xen/arch/arm/acpi/lib
From: Shannon Zhao
Permit access all Xen unused SPIs for Dom0 except the interrupts that
Xen uses. Then when Dom0 configures the interrupt, it could set the
interrupt type and route it to Dom0.
Signed-off-by: Shannon Zhao
---
v4: only permmit access all Xen unused SPIs for Dom0 and don't set ty
From: Shannon Zhao
Firstly it permits full MMIO capabilities for Dom0. Then deny MMIO
access of Xen used devices, such as UART, SMMU. Currently, it only
denies the MMIO access of UART and for other Xen used devices it could
be added later when they are supported.
Signed-off-by: Shannon Zhao
---
From: Shannon Zhao
Interrupt information is described in DSDT and is not available at the
time of booting. Check if the interrupt is permitted to access and set
the interrupt type, route it to guest dynamically only for SPI
and Dom0.
Signed-off-by: Parth Dixit
Signed-off-by: Shannon Zhao
---
From: Shannon Zhao
Create a few EFI memory descriptors to tell Dom0 the RAM region
information, ACPI table regions and EFI tables reserved resions.
Cc: Jan Beulich
Signed-off-by: Parth Dixit
Signed-off-by: Shannon Zhao
---
v4: use a single descriptor for new created tables
---
xen/arch/arm/d
From: Shannon Zhao
Estimate the memory required for loading acpi/efi tables in Dom0. Make
the length of each table aligned with 64bit. Alloc the pages to store
the new created EFI and ACPI tables and free these pages when
destroying domain.
Cc: Jan Beulich
Signed-off-by: Parth Dixit
Signed-off
flight 84355 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/84355/
Perfect :-)
All tests in this flight passed
version targeted for testing:
xen abf8824fe530bcf060c757596f68663c87546a6a
baseline version:
xen 2066ddd2327daeb2d9
On Sat, Feb 27, Olaf Hering wrote:
> -O2 -Wall
> -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
I think the cause is the lack of a "maintainer mode", which should
enable realworld CFLAGS. Either a new configure knob gets added (and
used!) or the existing EXTRA_CFLAGS_* have to be used by c
flight 84243 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/84243/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail
REGR. vs. 65543
test-amd64-i386-
65 matches
Mail list logo
