flight 170041 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170041/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
On 5/3/22 05:43, Luca Fancellu wrote:
>
>
>> On 2 May 2022, at 14:53, Daniel P. Smith
>> wrote:
>>
>> On 5/2/22 09:49, Daniel P. Smith wrote:
>>> On 5/2/22 09:42, Jason Andryuk wrote:
On Mon, May 2, 2022 at 9:31 AM Daniel P. Smith
wrote:
> diff --git a/xen/arch/arm/setup.c
On Fri, Apr 29, 2022 at 11:58 PM Stefano Stabellini
wrote:
> From: Stefano Stabellini
>
Hello Stefano
[Sorry for the possible format issues]
>
> Implement extended regions for dom0less domUs. The implementation is
> based on the libxl implementation.
>
> Signed-off-by: Stefano Stabellini
This commit implements full support for starting the idle domain privileged by
introducing a new flask label xenboot_t which the idle domain is labeled with
at creation. It then provides the implementation for the XSM hook
xsm_set_system_active to relabel the idle domain to the existing xen_t
There are new capabilities, dom0less and hyperlaunch, that introduce internal
hypervisor logic which needs to make resource allocation calls that are
protected by XSM access checks. This creates an issue as a subset of the
hypervisor code is executed under a system domain, the idle domain, that is
This series makes it so that the idle domain is started privileged under the
default policy, which the SILO policy inherits, and under the flask policy. It
then introduces a new one-way XSM hook, xsm_transition_running, that is hooked
by an XSM policy to transition the idle domain to its running
> On 3 May 2022, at 11:35, Luca Fancellu wrote:
>
>
>
>> On 29 Apr 2022, at 21:57, Stefano Stabellini wrote:
>>
>> From: Stefano Stabellini
>>
>> Document how to use the feature and how the implementation works.
>>
>> Signed-off-by: Stefano Stabellini
>
> Reviewed-by Luca Fancellu
>
flight 170038 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170038/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
> On 29 Apr 2022, at 21:57, Stefano Stabellini wrote:
>
> From: Stefano Stabellini
>
> Document how to use the feature and how the implementation works.
>
> Signed-off-by: Stefano Stabellini
Reviewed-by Luca Fancellu
Hi Stefano,
> On 29 Apr 2022, at 21:57, Stefano Stabellini wrote:
>
> From: Stefano Stabellini
>
> When the length of the string is zero of_property_read_string should
> return -ENODATA according to the description of the function.
>
> However, of_property_read_string doesn't check
> On 29 Apr 2022, at 21:57, Stefano Stabellini wrote:
>
> From: Stefano Stabellini
>
> Implement extended regions for dom0less domUs. The implementation is
> based on the libxl implementation.
>
> Signed-off-by: Stefano Stabellini
> ---
> Changes in v5:
> - print the domain
> - coding
On Mon, Apr 25, 2022 at 10:32:10AM +0200, Jan Beulich wrote:
> As of 68a8aa5d7264 ("iommu: make map and unmap take a page count,
> similar to flush") there's no need anymore to have a loop here.
>
> Suggested-by: Roger Pau Monné
> Signed-off-by: Jan Beulich
Reviewed-by: Roger Pau Monné
I
> On 29 Apr 2022, at 21:57, Stefano Stabellini wrote:
>
> From: Stefano Stabellini
>
> When the length of the string is zero of_property_read_string should
> return -ENODATA according to the description of the function.
>
> However, of_property_read_string doesn't check prop->length. If
>
On Mon, Apr 25, 2022 at 10:30:33AM +0200, Jan Beulich wrote:
> Recent changes (likely 5fafa6cf529a ["AMD/IOMMU: have callers specify
> the target level for page table walks"]) have made Coverity notice a
> shift count in iommu_pde_from_dfn() which might in theory grow too
> large. While this isn't
flight 170030 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170030/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
> On 2 May 2022, at 14:53, Daniel P. Smith wrote:
>
> On 5/2/22 09:49, Daniel P. Smith wrote:
>> On 5/2/22 09:42, Jason Andryuk wrote:
>>> On Mon, May 2, 2022 at 9:31 AM Daniel P. Smith
>>> wrote:
diff --git a/xen/arch/arm/setup.c b/xen/arch/arm/setup.c
index d5d0792ed4..b9057222d6
SMCC_WORKAROUND_3 is handling both Spectre v2 and spectre BHB.
So when a guest is asking if we support workaround 1, tell yes if we
apply workaround 3 on exception entry as it handles it.
This will allow guests not supporting Spectre BHB but impacted by
spectre v2 to still handle it correctly.
This patch is adding sb instruction support when it is supported by a
CPU on arm64.
To achieve this, the "sb" macro is moved to sub-arch macros.h so that we
can use sb instruction when available through alternative on arm64 and
keep the current behaviour on arm32.
A new cpuerrata capability is
Following up the handling of Spectre BHB on Arm (XSA-398), this serie
contain several changes which were not needed in the XSA patches but
should be done in Xen:
- Sync sysregs and cpuinfo with latest version of Linux (5.18-rc3)
- Advertise both workaround 1 and 3 if we apply workaround 3 as it
Sync arm64 sysreg bit shift definitions with status of Linux kernel as
of 5.18-rc3 version (linux commit b2d229d4ddb1).
Sync ID registers sanitization with the status of Linux 5.18-rc3 and add
sanitization of ISAR2 registers.
Complete AA64ISAR2 and AA64MMFR1 with more fields.
While there add a
On Tue, May 03, 2022 at 10:17:44AM +0200, Jan Beulich wrote:
> On 02.05.2022 17:20, Roger Pau Monne wrote:
> > The symbol map generation (and thus the debug info attached to Xen) is
> > partially broken when using LLVM LD. That's due to LLD converting
> > almost all symbols from global to local
On 29.04.22 22:57, Stefano Stabellini wrote:
From: Luca Miccio
Add an example application that can be run in dom0 to complete the
dom0less domains initialization so that they can get access to xenstore
and use PV drivers.
The application sets XS_CONNECTION_STATE_RECONNECTING on the xenstore
On 29.04.22 22:57, Stefano Stabellini wrote:
From: Luca Miccio
When xs_introduce_domain is called, send out a notification on the
xenstore event channel so that any (dom0less) domain waiting for the
xenstore interface to be ready can continue with the initialization.
Before sending the
On 29.04.22 23:10, Stefano Stabellini wrote:
From: Luca Miccio
When running as dom0less guest (HVM domain on ARM) the xenstore event
channel is available at domain creation but the shared xenstore
interface page only becomes available later on.
In that case, wait for a notification on the
On Tue, May 03, 2022 at 10:25:02AM +0200, Jan Beulich wrote:
> On 03.05.2022 09:50, Roger Pau Monné wrote:
> > Hello,
> >
> > I've blessed the pair of sabro boxes for production after a successful
> > commission flight:
> >
> > http://logs.test-lab.xenproject.org/osstest/logs/169857/
> >
> >
flight 170014 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170014/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict 7 xen-install fail in
169990 pass in 170014
Hi,
> On 29 Apr 2022, at 21:57, Stefano Stabellini wrote:
>
> From: Luca Miccio
>
> Export evtchn_alloc_unbound and make it __must_check.
>
> If "xen,enhanced" is enabled, then add to dom0less domains:
>
> - the hypervisor node in device tree
> - the xenstore event channel
>
> The xenstore
Expose VIRT_SSBD to guests if the hardware supports setting SSBD in
the LS_CFG MSR (a.k.a. non-architectural way). Different AMD CPU
families use different bits in LS_CFG, so exposing VIRT_SPEC_CTRL.SSBD
allows for an unified way of exposing SSBD support to guests on AMD
hardware that's compatible
Hello,
The following series implements support for MSR_VIRT_SPEC_CTRL
(VIRT_SSBD) on different AMD CPU families.
Note that the support is added backwards, starting with the newer CPUs
that support MSR_SPEC_CTRL and moving to the older ones either using
MSR_VIRT_SPEC_CTRL or the SSBD bit in
Allow HVM guests access to MSR_VIRT_SPEC_CTRL if the platform Xen is
running on has support for it. This requires adding logic in the
vm{entry,exit} paths for SVM in order to context switch between the
hypervisor value and the guest one. The added handlers for context
switch will also be used
Use the logic to set shadow SPEC_CTRL values in order to implement
support for VIRT_SPEC_CTRL (signaled by VIRT_SSBD CPUID flag) for HVM
guests. This includes using the spec_ctrl vCPU MSR variable to store
the guest set value of VIRT_SPEC_CTRL.SSBD, which will be OR'ed with
any SPEC_CTRL values
flight 170029 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170029/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
On 03.05.2022 09:50, Roger Pau Monné wrote:
> Hello,
>
> I've blessed the pair of sabro boxes for production after a successful
> commission flight:
>
> http://logs.test-lab.xenproject.org/osstest/logs/169857/
>
> Note that the boxes don't seem to be able to boot in 32bit mode, see
> the
On 02.05.2022 17:20, Roger Pau Monne wrote:
> The symbol map generation (and thus the debug info attached to Xen) is
> partially broken when using LLVM LD. That's due to LLD converting
> almost all symbols from global to local in the last linking step, and
I'm puzzled by "almost" - is there a
flight 170027 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170027/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
Hello,
I've blessed the pair of sabro boxes for production after a successful
commission flight:
http://logs.test-lab.xenproject.org/osstest/logs/169857/
Note that the boxes don't seem to be able to boot in 32bit mode, see
the following flight where all 32bit jobs failed to install the host:
flight 170020 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170020/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-i386-libvirt
flight 170022 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170022/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
101 - 138 of 138 matches
Mail list logo
