This email only tracks big items for xen.git tree. Please reply for items you
would like to see in 4.11 so that people have an idea what is going on and
prioritise accordingly.
You're welcome to provide description and use cases of the feature you're
working on.
= Timeline =
We now adopt a
flight 120949 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120949/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
Hi,
There is an 'e' option when running the following xl command:
- xl create
- xl restore
- xl migrate
- xl remus
The 'e' option is used to "Do not wait in the background (on ) for the
death of the domain". This option dates back to Dec 2009.
Would you please help me understand the objective
Hi Andre,
On 03/15/2018 08:30 PM, Andre Przywara wrote:
Adds the sorting function to cover the case where you have more IRQs
to consider than you have LRs. We consider their priorities.
This uses the new sort_list() implementation imported from Linux.
This is based on Linux commit
Hi,
On 03/15/2018 08:30 PM, Andre Przywara wrote:
Provide a vgic_queue_irq_unlock() function which decides whether a
given IRQ needs to be queued to a VCPU's ap_list.
This should be called whenever an IRQ becomes pending or enabled,
either as a result of a hardware IRQ injection, from devices
flight 120877 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120877/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-ws16-amd64 16 guest-localmigrate/x10 fail REGR. vs.
12
flight 120866 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120866/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-xsm7 xen-boot fail REGR. vs. 118324
Hi Andre,
On 03/15/2018 08:30 PM, Andre Przywara wrote:
The new VGIC implementation centers around a struct vgic_irq instance
per virtual IRQ.
Provide a function to retrieve the right instance for a given IRQ
number and (in case of private interrupts) the right VCPU.
This also includes the
Hi Andre,
On 03/15/2018 08:30 PM, Andre Przywara wrote:
Add a new header file for the new and improved GIC implementation.
The big change is that we now have a struct vgic_irq per IRQ instead
of spreading all the information over various bitmaps in the ranks.
We include this new header
Hi Andre,
On 03/15/2018 08:30 PM, Andre Przywara wrote:
The event channel IRQ has level triggered semantics, however the current
VGIC treats everything as edge triggered.
To correctly process those IRQs, we have to lower the (virtual) IRQ line
at some point in time, depending on whether ther
flight 120879 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120879/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 34d808add3dc23aaa37e1c9edb2fcc2b50118367
baseline version:
ovmf
The null_dom() static inline is just used when debug=y so it results in
a error with the default CFLAGS and debug=n.
Signed-off-by: Doug Goldstein
---
sched_null.c:123:32: error: unused function 'null_dom'
[-Werror,-Wunused-function]
Feel free to fix this better.
---
Hi Andre,
On 03/15/2018 08:30 PM, Andre Przywara wrote:
The ARM Generic Timer uses a level-sensitive interrupt semantic. We
easily catch when the line goes high, as this triggers the hardware IRQ.
However we have to sync the state of the interrupt condition at certain
points to catch when the
Hi Andre,
On 03/15/2018 08:30 PM, Andre Przywara wrote:
To synchronize level triggered interrupts which are mapped into a guest,
we need to update the virtual line level at certain points in time.
For a hardware mapped interrupt the GIC is the only place where we can
easily access this
Hi Stefano,
On 03/16/2018 08:27 PM, Stefano Stabellini wrote:
On Mon, 12 Mar 2018, julien.gr...@arm.com wrote:
From: Julien Grall
A recent update to the ARM SMCCC_ARCH_WORKAROUND_1 specification (see [1])
allows firmware to return a non zero, positive value, to describe
On 03/16/2018 04:05 PM, Andre Przywara wrote:
Hi,
Hi Andre,
On 15/03/18 20:30, Andre Przywara wrote:
+}
+}
+
+static void gicv2_set_pending_state(struct irq_desc *irqd, bool pending)
+{
+ASSERT(spin_is_locked(>lock));
+
+if ( pending )
+{
+/* The INPROGRESS bit
Hi,
On 03/18/2018 03:00 PM, Edgar E. Iglesias wrote:
On Sun, Mar 18, 2018 at 02:50:26PM +0530, Amit Singh Tomar wrote:
Signed-off-by: Amit Singh Tomar
Reviewed-by: Edgar E. Iglesias
Acked-by: Julien Grall
And
flight 120869 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120869/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvshim broken
test-amd64-amd64-qemuu-nested-intel 14
flight 120867 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120867/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail REGR. vs. 115539
Tests which did not
flight 120859 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120859/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-raw 5 host-ping-check-native fail REGR. vs. 120037
flight 120872 rumprun real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120872/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumprun 6 rumprun-buildfail REGR. vs. 106754
build-i386-rumprun
flight 120863 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120863/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt-xsm 14 saverestore-support-checkfail like 120785
test-armhf-armhf-libvirt 14
On Sun, Mar 18, 2018 at 02:50:26PM +0530, Amit Singh Tomar wrote:
> Signed-off-by: Amit Singh Tomar
Reviewed-by: Edgar E. Iglesias
> ---
> Changes since v1:
> * Addressed Andre's comment.
> ---
> xen/arch/arm/platforms/xilinx-zynqmp.c |
flight 120846 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120846/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvops 6 kernel-build fail REGR. vs. 118294
build-i386-pvops
flight 120905 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120905/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 0012ae8afb4a6e76f2847119f2c6850fbf41d9b7
baseline version:
xen
Signed-off-by: Amit Singh Tomar
---
Changes since v1:
* Addressed Andre's comment.
---
xen/arch/arm/platforms/xilinx-zynqmp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/arm/platforms/xilinx-zynqmp.c
Signed-off-by: Amit Singh Tomar
---
docs/misc/arm/early-printk.txt | 1 +
xen/arch/arm/Rules.mk | 1 +
xen/arch/arm/arm64/debug-mvebu.inc | 48 ++
3 files changed, 50 insertions(+)
create mode 100644
flight 120835 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/120835/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 6 xen-install fail REGR. vs. 120654
28 matches
Mail list logo