flight 131583 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131583/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-examine4 memdisk-try-append fail in 131564 pass in 131583
test-amd64-i386-libvirt-qemuu-de
flight 131592 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131592/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131580 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131580/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-examine 8 reboot fail REGR. vs. 128858
test-amd64-i386-qemu
flight 131591 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131591/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131590 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131590/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131588 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131588/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131578 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131578/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-amd64-pvgrub 7 xen-bootfail REGR. vs. 125898
test-amd64-amd64-ru
From: "Kirill A. Shutemov"
[ Upstream commit 16877a5570e0c5f4270d5b17f9bab427bcae9514 ]
There is a guard hole at the beginning of the kernel address space, also
used by hypervisors. It occupies 16 PGD entries.
This reserved range is not defined explicitely, it is calculated relative
to other en
From: "Kirill A. Shutemov"
[ Upstream commit 254eb5505ca0ca749d3a491fc6668b6c16647a99 ]
The LDT remap placement has been changed. It's now placed before the direct
mapping in the kernel virtual address space for both paging modes.
Change address markers order accordingly.
Fixes: d52888aa2753 (
From: "Kirill A. Shutemov"
[ Upstream commit 254eb5505ca0ca749d3a491fc6668b6c16647a99 ]
The LDT remap placement has been changed. It's now placed before the direct
mapping in the kernel virtual address space for both paging modes.
Change address markers order accordingly.
Fixes: d52888aa2753 (
From: "Kirill A. Shutemov"
[ Upstream commit 16877a5570e0c5f4270d5b17f9bab427bcae9514 ]
There is a guard hole at the beginning of the kernel address space, also
used by hypervisors. It occupies 16 PGD entries.
This reserved range is not defined explicitely, it is calculated relative
to other en
The pull request you sent on Thu, 20 Dec 2018 19:28:23 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for-linus-4.21-rc1-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/460023a5d1d2aa0f733b6708b2fae5ea9f9dfec0
Thank you!
--
Deet-doot-dot, I
Patchew URL:
https://patchew.org/QEMU/1545422632-2-1-git-send-email-liam.merw...@oracle.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 1545422632-2-1-git-send-email-liam.merw...@oracle.com
Type: series
Subject: [Qemu-d
flight 131586 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131586/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131585 freebsd-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131585/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
freebsd 5234db76104dc41f94e4899413ba19062c03ddce
baseline version:
freebsd 13391961c77
On Mon, Dec 24, 2018 at 8:51 PM Russell King - ARM Linux
wrote:
>
> Having discussed with Matthew offlist, I think we've come to the
> following conclusion - there's a number of drivers that buggily
> ignore vm_pgoff.
>
> So, what I proposed is:
>
> static int __vm_insert_range(struct vm_struct *v
flight 131567 linux-4.19 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131567/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-shadow7 xen-boot fail REGR. vs. 129313
test-amd64-amd64-pai
On 2018/12/21 18:20, Andrew Cooper wrote:
>> +static unsigned int __initdata opt_cpuid_mask_l7s0_eax = ~0u;
>> +integer_param("cpuid_mask_l7s0_eax", opt_cpuid_mask_l7s0_eax);
>> +static unsigned int __initdata opt_cpuid_mask_l7s0_ebx = ~0u;
>> +integer_param("cpuid_mask_l7s0_ebx", opt_cpuid_ma
From: Andrii Anisov
PPI are pcpu private, so their processing is not concurrent and do not
need pcpu shared flags and correspondent lockings. So avoid odd bits
sets, checks and locks.
Signed-off-by: Andrii Anisov
---
xen/arch/arm/gic.c| 8 ++--
xen/arch/arm/irq.c| 32 +
From: Andrii Anisov
This reduces the number of context switches in case we have coming guest
interrupts from different sources at a high rate. What is likely for
multimedia use-cases.
Having irqs unlocked here makes us go through trap path again in case we
have a new guest interrupt arrived (even
From: Andrii Anisov
This reduces some code and conditions in an IRQ processing path,
reducing IRQ latency for a build supported GICV2 only.
Signed-off-by: Andrii Anisov
---
Its a patch [1] with a better message and removed build errors.
Comments from Andre are not addressed yet.
[1] https://l
From: Andrii Anisov
This function is called under IRQs disabled already, so drop additional
flags save and restore.
Signed-off-by: Andrii Anisov
---
This patch is a part of [1] and already sent to the list [2].
[1] https://lists.xenproject.org/archives/html/xen-devel/2018-11/msg03293.html
[2]
From: Andrii Anisov
Simplify context restore from idle vcpu to the one ran before it.
This improves low cpu load but high irq rate use-cases.
Signed-off-by: Andrii Anisov
---
xen/arch/arm/domain.c | 21 +++--
xen/include/xen/sched.h | 1 +
2 files changed, 12 insertions(+),
From: Julien Grall
This makes function enter_hypervisor_head() being executed with
irqs locked. This also give a fine side effect - it assures that
LRs are cleared prior to any IRQs processing, which leads to a
better (faster) IRQs processing.
Signed-off-by: Julien Grall
[Andrii: add a justific
From: Andrii Anisov
Because the HCR value is only changed by the hypervisor,
we can rely on a cached value and do not do peripheral register
reads for this register.
Signed-off-by: Andrii Anisov
---
xen/arch/arm/gic-v2.c | 43 +--
xen/arch/arm/gic-v3
From: Andrii Anisov
Avoid excessive conversions between `pending_irq` and irq number and
priority. This is a tiny but pure optimization.
Also it aligns a `gic_raise_guest_irq()` function interface to its
current implementation in the meaning that it is removed a clearly
ignored priority argument
From: Andrii Anisov
For GICV2 pending_irq allocation is not concurrent, so reduce
some code under lock.
This code is not supposed to work with GICv3
Signed-off-by: Andrii Anisov
---
xen/arch/arm/gic-v3-its.c | 2 ++
xen/arch/arm/gic-v3-lpi.c | 2 ++
xen/arch/arm/gic-v3.c | 2 ++
xen/arch/
From: Andrii Anisov
After the patch "xen/arm: Re-enable interrupt later in the trap path"
this function is called with irqs already locked.
Signed-off-by: Andrii Anisov
---
xen/arch/arm/gic-vgic.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/xen/arch/arm/gic-vgic.
From: Andrii Anisov
This saves one write to peripheral HCR register per hypervisor entry for
most cases.
Signed-off-by: Andrii Anisov
---
xen/arch/arm/gic-v2.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/xen/arch/arm/gic-v2.c b/xen/arch/arm/gic-v2.c
index 1a744c5
From: Andrii Anisov
All bit operations for gic, vgic and gic-vgic are performed under
spinlocks, so there is no need for atomic bit ops here, they only
introduce excessive call to functions used more expensive exclusive
ARM instructions.
Signed-off-by: Andrii Anisov
---
This patch was not chan
From: Andrii Anisov
Do not put already disabled IRQs into any of queues, and remove
an IRQ from all queues on disable. Insert the IRQ into queues on
enable if needed. This also allows simplification of under-lock
decission of events needed delivery.
Signed-off-by: Andrii Anisov
---
xen/arch/ar
From: Andrii Anisov
This patch series is an attempt to reduce IRQ latency with the
old GIC implementation (gic-vgic). These patches originally based
on XEN 4.10 release. The motivation was to improve benchmark
results of a system given to a customer for evaluation.
This patch series is tailored f
From: Andrii Anisov
Pause_flags is not related to vgic spinlock, so reduce code
under lock.
Signed-off-by: Andrii Anisov
---
Comments from Julien [1] are not addressed yet.
[1] https://lists.xenproject.org/archives/html/xen-devel/2018-11/msg03306.html
---
xen/arch/arm/vgic.c | 13 ++
From: Andrii Anisov
Cache line size assumed 64 byte as for H3. Align the `struct
pending_irq` and allocate lrs shadow aligned to cache line size.
Signed-off-by: Andrii Anisov
---
xen/arch/arm/domain.c| 4
xen/arch/arm/vgic.c | 9 +
xen/include/asm-arm/config.h | 2
flight 131582 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131582/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
flight 131564 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131564/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-libvirt-pair 10 xen-boot/src_host fail in 131537 pass in
131564
test-armhf-armhf-xl-rtds
flight 131581 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/131581/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 129475
build-i386-xsm
37 matches
Mail list logo
