flight 137076 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137076/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stopfail like 137031
test-armhf-armhf-libvirt-raw 13
Signed-off-by: Baodong Chen
---
xen/common/cpu.c | 10 --
xen/include/xen/cpu.h | 4 ++--
2 files changed, 2 insertions(+), 12 deletions(-)
diff --git a/xen/common/cpu.c b/xen/common/cpu.c
index f388d89..a526b55 100644
--- a/xen/common/cpu.c
+++ b/xen/common/cpu.c
@@ -51,16 +51,6
> On Mar 28, 2019, at 11:04, Woods, Brian wrote:
>
> This patch series add support and enablement for mwait on AMD Naples
> and Rome processors. Newer AMD processors support mwait, but only for
> c1, and for c2 halt is used. The mwait-idle driver is modified to be
> able to use both mwait and
On 5/30/19 8:16 AM, Ben Hutchings wrote:
I'm looking at CVE-2015-8553 which is fixed by:
commit 7681f31ec9cdacab4fd10570be924f2cef6669ba
Author: Konrad Rzeszutek Wilk
Date: Wed Feb 13 18:21:31 2019 -0500
xen/pciback: Don't disable PCI_COMMAND on PCI device reset.
I'm aware that this
keyhandler mainly used for debug usage by developers which can dump
xen module(eg. timer, scheduler) status at runtime by input
character from console.
Signed-off-by: Baodong Chen
---
xen/arch/arm/gic.c | 2 ++
xen/arch/x86/apic.c | 2 ++
xen/common/Kconfig | 9
flight 137065 xen-4.7-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137065/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-prev 6 xen-buildfail REGR. vs. 133596
flight 137064 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137064/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-migrupgrade 22 guest-migrate/src_host/dst_host fail REGR. vs.
127792
Hi all,
Please propose topics by either editing the running agenda document at
https://cryptpad.fr/pad/#/2/pad/edit/WZr2VTdfmaPdvIxjXp+cgSF- or by replying to
the mail.
Ideally by Tuesday!
Note that I am using another sharing mechanism as per request. Let me know if
you have difficulties
Best
On Thu, May 30, 2019 at 10:17:32PM +0200, Federico Vaga wrote:
> On Thursday, May 30, 2019 1:23:53 AM CEST Mauro Carvalho Chehab wrote:
> > Mostly due to x86 and acpi conversion, several documentation
> > links are still pointing to the old file. Fix them.
>
> For the Italian documentation I just
From: Colin Ian King
The variable err is assigned with the value -ENOMEM that is never
read and it is re-assigned a new value later on. The assignment is
redundant and can be removed.
Addresses-Coverity: ("Unused value")
Signed-off-by: Colin Ian King
---
drivers/net/xen-netback/interface.c |
drivers/firmware/qcom_scm.c:469:47: error: passing argument 3 of
`dma_alloc_coherent' from incompatible pointer type
[-Werror=incompatible-pointer-types]
This is fixed by
firmware: qcom_scm: Use proper types for dma mappings
but this is not present in all relevant stable branches.
We
flight 137057 qemu-upstream-4.11-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137057/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvopsbroken in 134504
build-arm64
flight 137063 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137063/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 saverestore-support-checkfail like 137022
test-armhf-armhf-libvirt-raw 13
On 29.05.19 20:06, Julien Grall wrote:
Hi,
On 20/05/2019 23:56, Stefano Stabellini wrote:
On Tue, 14 May 2019, Julien Grall wrote:
None of the parameters of secondary_start are actually used. So turn
secondary_start to a function with no parameters.
Also modify the assembly code to avoid
On 21.05.19 13:09, Julien Grall wrote:
Hi,
On 5/20/19 11:56 PM, Stefano Stabellini wrote:
On Tue, 14 May 2019, Julien Grall wrote:
The current value of HSCTLR_BASE for Arm64 is pretty wrong. It would
actually turn on SCTLR_EL2.nAA (bit 6) on hardware implementing
ARMv8.4-LSE.
Furthermore,
On 29.05.19 18:32, Julien Grall wrote:
BTW, do you hear about plans for the new vgic? Some time ago it was said that
new vgic implementation going to replace the old one, and optimizing the old is
worthless. But as I see, there are no updates into that area yet.
We need help to make it
On 29.05.19 18:32, Julien Grall wrote:
It would have been nice to at least fix up the commit message with the typoes
(and rewording) I mentioned in my previous e-mail.
Your commit message needs to explained why this is fine to keep the interrupt
masked a bit longer. I wrote the explanation
flight 137055 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137055/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-amd 12 guest-start/redhat.repeat fail REGR. vs.
133580
On Thu, May 30, 2019 at 7:18 AM Petre Pircalabu
wrote:
>
> This patchset adds a new mechanism of sending synchronous vm_event
> requests and handling vm_event responses without using a ring.
> As each synchronous request pauses the vcpu until the corresponding
> response is handled, it can be
I'm looking at CVE-2015-8553 which is fixed by:
commit 7681f31ec9cdacab4fd10570be924f2cef6669ba
Author: Konrad Rzeszutek Wilk
Date: Wed Feb 13 18:21:31 2019 -0500
xen/pciback: Don't disable PCI_COMMAND on PCI device reset.
I'm aware that this change is incompatible with qemu < 2.5, but
Using clang and lld 8 requires installing the packages from the
official llvm apt repositories, so modify the Debian Docker files for
stretch and unstable to add the llvm repo and install clang and lld
from it.
Also add some jobs to test building Xen with clang 8 and lld.
Signed-off-by: Roger
Signed-off-by: Roger Pau Monné
---
Cc: Doug Goldstein
Cc: Wei Liu
---
automation/scripts/containerize | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/automation/scripts/containerize b/automation/scripts/containerize
index a7809b3010..474530f945 100755
---
This patchset adds a new mechanism of sending synchronous vm_event
requests and handling vm_event responses without using a ring.
As each synchronous request pauses the vcpu until the corresponding
response is handled, it can be stored in a slotted memory buffer
(one per vcpu) shared between the
The domain reference can be part of the vm_event_domain structure
because for every call to a vm_event interface function both the latter
and it's corresponding domain are passed as parameters.
Affected functions:
- __vm_event_claim_slot / vm_event_claim_slot / vm_event_claim_slot_nosleep
-
In high throughput introspection scenarios where lots of monitor
vm_events are generated, the ring buffer can fill up before the monitor
application gets a chance to handle all the requests thus blocking
other vcpus which will have to wait for a slot to become available.
This patch adds support
Define the type for each of the supported vm_event rings (paging,
monitor and sharing) and replace the ring param field with this type.
Replace XEN_DOMCTL_VM_EVENT_OP_ occurrences with their corresponding
XEN_VM_EVENT_TYPE_ counterpart.
Signed-off-by: Petre Pircalabu
---
vm_event_get_response, vm_event_resume, and vm_event_mark_and_pause are
used only in xen/common/vm_event.c.
Signed-off-by: Petre Pircalabu
---
xen/common/vm_event.c | 6 +++---
xen/include/xen/vm_event.h | 3 ---
2 files changed, 3 insertions(+), 6 deletions(-)
diff --git
To accommodate a second implementation of the vm_event subsystem, the
current one (ring) should be decoupled from the xen/vm_event.h interface.
Signed-off-by: Petre Pircalabu
---
xen/common/vm_event.c | 407 ++---
xen/include/xen/vm_event.h | 56
Split xen-access in order to accommodate both vm_event interfaces
(legacy and NG). By default, the legacy vm_event is selected but
this can be changed by adding the '-n' flag in the command line.
Signed-off-by: Petre Pircalabu
---
tools/tests/xen-access/Makefile | 7 +-
Decouple implementation from interface to allow vm_event_check to be
used regardless of the vm_event underlying implementation.
Signed-off-by: Petre Pircalabu
---
xen/arch/arm/mem_access.c | 2 +-
xen/arch/x86/mm/mem_access.c | 4 ++--
xen/arch/x86/mm/mem_paging.c | 2 +-
The vm_event_domain members are not accessed outside vm_event.c so it's
better to hide de implementation details.
Signed-off-by: Petre Pircalabu
---
xen/common/vm_event.c | 27 +++
xen/include/xen/sched.h | 27 +--
2 files changed, 28
From: Andrii Anisov
The structure member last_run_time is used by credit scheduler only.
So move it from a generic vcpu structure to the credit scheduler private
vcpu definition.
With this move we have slight changes in functionality:
- last_run_time is not updated for an idle vcpu. But the
flight 137049 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137049/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ws16-amd64 10 windows-install fail REGR. vs. 137015
Tests which did not
Ian Jackson writes ("Re: Stable trees (4.6 and 4.7), building on stretch,
osstest, redux"):
> I have now pushed all of these to 4.6 and 4.7 and it builds for me.
> I will kill the current, doomed, 4.6 and 4.7 flights.
I have now also backported
5f28de0b0e474e01931b719fa27ca30b8aa446e0
libxl:
On 5/30/19 5:04 AM, Christoph Hellwig wrote:
> Please don't add your private flag to page-flags.h. The whole point of
> the private flag is that you can use it in any way you want withou
> touching the common code.
There is already a bunch of aliases for various sub-components
(including Xen)
Hi Oleksandr,
Hello, Anchal!
On 3/29/19 1:19 AM, Anchal Agarwal wrote:
[snip]
Great, could you please let us know what is the progress and further
plans
on that, so we do not work on the same code and can coordinate our
efforts somehow? Anchal, could
flight 137056 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137056/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 21d9dc21f81828538af02ca9c2d86a36551b0771
baseline version:
ovmf
From: Oleksandr Tyshchenko
In case iommu_ops have been already set, we should not update it.
Signed-off-by: Oleksandr Tyshchenko
Signed-off-by: Andrii Anisov
---
This patch is extracted from [1], as agreed here [2].
[1]
Default: enabled.
Can be disabled for smaller code footprint.
Signed-off-by: Baodong Chen
---
xen/common/Kconfig | 6 ++
xen/common/Makefile | 2 +-
xen/include/xen/trace.h | 18 +-
3 files changed, 24 insertions(+), 2 deletions(-)
diff --git a/xen/common/Kconfig
3.18 doesn't boot on Xen any more and Linux stable upstream say it
will not be fixed because it's EOL. Thanks to them for that
confirmation.
While we are here, drop all earlier Linux branches too. We are
wasting our time fetching them, seeing if they have changed, and then
doing nothing.
CC:
Hello George,
On 5/30/19 17:05, George Dunlap wrote:
On May 30, 2019, at 6:47 AM, Baodong Chen wrote:
So remove 'keyhandler.h' include.
Also add 'static' prefix for 'schud_bull_def'
Signed-off-by: Baodong Chen
Thanks for the patch — these changes look good. I think the title would be
* Remove unused dependency 'keyhandler.h'
* Make sched_null_def static
Signed-off-by: Baodong Chen
Reviewed-by: George Dunlap
---
xen/common/sched_null.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/xen/common/sched_null.c b/xen/common/sched_null.c
index
Please don't add your private flag to page-flags.h. The whole point of
the private flag is that you can use it in any way you want withou
touching the common code.
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
> On May 30, 2019, at 6:47 AM, Baodong Chen wrote:
>
> So remove 'keyhandler.h' include.
> Also add 'static' prefix for 'schud_bull_def'
>
> Signed-off-by: Baodong Chen
Thanks for the patch — these changes look good. I think the title would be
better something like:
xen/sched_null:
>
>> +return false;
>> +
>> +rc = hvmemul_linear_to_phys(gla, , bytes, , pfec, );
>
> As said before - I don't think it's a good idea to do the page walk
> twice: This and the pre-existing one can easily return different
> results.
What preexisting page walk are you talking about
From: Andrii Anisov
Existing interface to register runstate are with its virtual address
is prone to issues which became more obvious with KPTI enablement in
guests. The nature of those issues is the fact that the guest could
be interrupted by the hypervisor at any time, and there is no
From: Andrii Anisov
An RFC version of the runstate registration with phys address.
Runstate area access is implemented with mapping on each update once for
all accesses.
Signed-off-by: Andrii Anisov
---
xen/arch/arm/domain.c | 63 ++---
xen/common/domain.c |
From: Andrii Anisov
---
Resending the series, because the previous try went with mangled threading.
---
Following discussion [1] it is introduced and implemented a runstate
registration interface which uses guest's phys address instead of a virtual one.
The new hypercall employes the same data
From: Andrii Anisov
An RFC version of the runstate registration with phys address.
Runstate area access is implemented with mapping on each access, like
old interface did.
Signed-off-by: Andrii Anisov
---
xen/arch/arm/domain.c | 63 ++-
So remove 'keyhandler.h' include.
Also add 'static' prefix for 'schud_bull_def'
Signed-off-by: Baodong Chen
---
xen/common/sched_null.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/xen/common/sched_null.c b/xen/common/sched_null.c
index a59dbb2..c9700f1 100644
---
flight 137044 linux-4.19 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/137044/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-pvops 6 kernel-build fail REGR. vs. 129313
Tests which are
51 matches
Mail list logo
