flight 163627 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163627/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 163474
Tests which
flight 163610 xen-unstable real [real]
flight 163626 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/163610/
http://logs.test-lab.xenproject.org/osstest/logs/163626/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be
Hi,
I am doing some NUMA testing on Xen. And I find the DMA restriction is
based on NUMA node number [1].
if ( !dma_bitsize && (num_online_nodes() > 1) )
dma_bitsize = arch_get_dma_bitsize();
On Arm64, we will set dma_bitsize [2] to 0, that means we don't need to
reserve DMA memory.
flight 163619 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163619/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 163474
Tests which
qemu can't start a xen vm after commit d8fb7d0969d5
"vl: switch -M parsing to keyval" with:
$ ./qemu-system-i386 -M xenfv
Unexpected error in object_property_find_err() at ../qom/object.c:1298:
qemu-system-i386: Property 'xenfv-3.1-machine.accel' not found
Aborted (core dumped)
The
The function domain_pause_for_debugger() is conditionally compiled if
CONFIG_CRASH_DEBUG=y. Instead of placing an extra #ifdef inside
domain.c, this commit moves domain_pause_for_debugger() into
x86/debugger.c which is only built by Kbuild given CONFIG_CRASH_DEBUG=y.
Signed-off-by: Bobby
The function debugger_trap_entry() is rather large for an inlined
function. This commit moves debugger_trap_entry() into debugger.c and
makes it not inlined.
Signed-off-by: Bobby Eshleman
---
xen/arch/x86/Makefile | 1 +
xen/arch/x86/debugger.c| 41
ARM doesn't actually use debugger_trap_* anything, and is stubbed out.
Simply remove the calls. This also renders TRAP_invalid_op unused in
any common code, so remove that definition too.
Signed-off-by: Bobby Eshleman
---
xen/arch/arm/traps.c | 6 --
xen/include/xen/debugger.h | 5
Previously Xen required all architectures implement the debugger_trap_*
functions whether or not it actually needs them.
This commit makes debugger_trap* functions resolve to arch-specific
function definitions if CONFIG_CRASH_DEBUG=y, but resolves to a set of
common no-op stubs if
Currently, any architecture wishing to use common/ is likely
to be required to implement the functions found in "asm/debugger.h".
Some architectures, however, do not have an actual use for these
functions and so are forced to implement stubs. This patch does the
following:
* Supplies common
flight 163612 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163612/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 162359
Current unit8_t for pirq argument in this interface is too restrictive
causing failures on modern hardware with lots of GSIs. That extends down to
XEN_DOMCTL_irq_permission ABI structure where it needs to be fixed up
as well.
Internal Xen structures appear to be fine. Existing users of the
On 12/07/2021 21:32, Daniel P. Smith wrote:
> The generic event channel labeling has not been used by any XSM module since
> its introduction. This commit removes the capability leaving FLASK labeling
> field always present. In the future if a new XSM module needs to have its own
> channel label,
On 12/07/2021 21:32, Daniel P. Smith wrote:
> diff --git a/xen/include/xen/alternative-call.h
> b/xen/include/xen/alternative-call.h
> new file mode 100644
> index 00..11d1c26068
> --- /dev/null
> +++ b/xen/include/xen/alternative-call.h
> @@ -0,0 +1,65 @@
> +/* SPDX-License-Identifier:
On 12/07/2021 21:32, Daniel P. Smith wrote:
> To reduce retpolines convert all the pointer function calls of the
> xsm_ops hooks over to the alternative_call infrastructure.
>
> Signed-off-by: Daniel P. Smith
> ---
> xen/include/xsm/xsm.h | 195 +-
> 1
On 12/07/2021 21:32, Daniel P. Smith wrote:
> diff --git a/xen/include/xsm/xsm.h b/xen/include/xsm/xsm.h
> index ad3cddbf7d..a8805f514b 100644
> --- a/xen/include/xsm/xsm.h
> +++ b/xen/include/xsm/xsm.h
> @@ -747,16 +747,14 @@ extern int xsm_dt_policy_init(void **policy_buffer,
> size_t
On 12/07/2021 21:32, Daniel P. Smith wrote:
> The flask XSM module provided the ability to switch from flask back to
> the dummy XSM module during runtime. With this removal the only way to
> switch between XSM modules is at boot time.
>
> Signed-off-by: Daniel P. Smith
This patch wants
flight 163600 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163600/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-freebsd11-amd64 13 guest-startfail REGR. vs. 163321
On 12/07/2021 21:32, Daniel P. Smith wrote:
> Based on feedback from 2021 Xen Developers Summit the xsm-roles RFC
> patch set is being split into two separate patch sets. This is the first
> patch set and is focused purely on the clean up and refactoring of the
> XSM hooks.
>
> This patch set
flight 163597 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163597/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-xsm7 xen-install fail REGR. vs. 152332
flight 163614 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163614/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 163474
Tests which
On Fri, 9 Jul 2021, Andre Przywara wrote:
> On Tue, 15 Jun 2021 07:12:08 +0100
> Wei Chen wrote:
>
> Hi Wei,
>
> > I have some thoughts of using kvmtool Virtio implementation
> > for Xen. I copied my markdown file to this email. If you have
> > time, could you please help me review it?
> >
> >
With the eliminations of default priv from all the XSM hook call sites, this
renders the XSM_ASSERT_ACTION macro unneeded. This commit cleans up all the
dummy hooks, removing the macro.
Signed-off-by: Daniel P. Smith
---
xen/xsm/dummy.h | 253 +++-
1
With the elimination of switching how dummy.h gets included, the function
declaration macros are no longer necessary. This commit expands them out to the
only value for which they will ever be set. This results in function
declaration lengths changing and since some definitions did not even follow
The passing of an xsm_default_t at each of the xsm hook call sites
served different functions depending on whether XSM was enabled or not.
When XSM was not enabled it attempted to function as a link-time check
that declared default action at the call site matched the default
declared action for
The generic event channel labeling has not been used by any XSM module since
its introduction. This commit removes the capability leaving FLASK labeling
field always present. In the future if a new XSM module needs to have its own
channel label, this or a new form can be introduced.
---
The only difference between !CONFIG_XSM and CONFIG_XSM when SILO and FLASK are
not enabled is whether the XSM hooks in dummy.h are called as static inline
functions or as function pointers to static functions. As such this commit,
* eliminates CONFIG_XSM
* introduces CONFIG_XSM_EVTCHN_LABELING
Multiple preprocessor defines were used as a mechanism to selective
include parts of the xsm.h header file. This makes it difficult to know
which portion is being included at anyone time. This commit works to
simplify this by separating the core structure and functions of XSM into
xsm-core.h away
To reduce retpolines convert all the pointer function calls of the
xsm_ops hooks over to the alternative_call infrastructure.
Signed-off-by: Daniel P. Smith
---
xen/include/xsm/xsm.h | 195 +-
1 file changed, 99 insertions(+), 96 deletions(-)
diff --git
The flask XSM module provided the ability to switch from flask back to
the dummy XSM module during runtime. With this removal the only way to
switch between XSM modules is at boot time.
Signed-off-by: Daniel P. Smith
---
xen/xsm/flask/flask_op.c | 32
1 file
This converts the global xsm_ops from being a pointer to a struct xsm_ops to
being an
explicit instance. It then reworks the XSM modules init function to
return their xsm_ops struct which is copied in to the global xsm_ops.
Signed-off-by: Daniel P. Smith
---
xen/include/xsm/xsm.h| 215
Based on feedback from 2021 Xen Developers Summit the xsm-roles RFC
patch set is being split into two separate patch sets. This is the first
patch set and is focused purely on the clean up and refactoring of the
XSM hooks.
This patch set refactors the xsm_ops wrapper hooks to use the
From: Andrew Cooper
The alternative call infrastructure is x86-only for now, but the common iommu
code has a variant and more common code wants to use the infrastructure.
Introduce CONFIG_ALTERNATIVE_CALL and a conditional implemetnation so common
code can use the optimisation when available,
Hi Bertrand,
On 12/07/2021 11:50, Bertrand Marquis wrote:
+#define __ARM64_FTR_BITS(SIGNED, VISIBLE, STRICT, TYPE, SHIFT, WIDTH,
SAFE_VAL) \
+ { \
+ .sign = SIGNED, \
+ .visible = VISIBLE,
Hi Bertrand,
On 12/07/2021 17:29, Bertrand Marquis wrote:
On 12 Jul 2021, at 12:13, Julien Grall wrote:
On 12/07/2021 12:03, Bertrand Marquis wrote:
Hi Julien,
Hi Bertrand,
On 12 Jul 2021, at 11:16, Julien Grall wrote:
Hi Bertrand,
On 29/06/2021 18:08, Bertrand Marquis wrote:
flight 163607 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163607/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 163474
Tests which
On 07/07/2021 14:22, Jan Beulich wrote:
This amends commit 980d6acf1517 ("IOMMU: make DMA containment of
quarantined devices optional").
Signed-off-by: Jan Beulich
Reviewed-by: Paul Durrant
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,13 @@ The format is based on [Keep a Changelog
On 07/07/2021 14:21, Jan Beulich wrote:
During the multiple renames of the sub-option I apparently forgot to
update the left side of the &&, and this pretty consistently.
Fixes: 980d6acf1517 ("IOMMU: make DMA containment of quarantined devices
optional")
Reported-by: Andrew Cooper
On Fri, 9 Jul 2021, Ian Jackson wrote:
> Julien Grall writes ("Re: gitlab merge request -> list patchbomb workflows"):
> > I have recently started to use b4 [1] to fetch patches and collect tags
> > from the mailing list. I am wondering if the tools could be extended to
> > also allow a quick
flight 163598 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163598/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 162359
On Wed, Jul 07, 2021 at 05:48:57PM +0200, Jan Beulich wrote:
> On 01.07.2021 16:09, Anthony PERARD wrote:
> > --- a/xen/common/Makefile
> > +++ b/xen/common/Makefile
> > @@ -80,8 +80,12 @@ config.gz: $(CONF_FILE)
> >
> > config_data.o: config.gz
> >
> > -config_data.S:
Hi Julien,
> On 12 Jul 2021, at 12:13, Julien Grall wrote:
>
>
>
> On 12/07/2021 12:03, Bertrand Marquis wrote:
>> Hi Julien,
>
> Hi Bertrand,
>
>>> On 12 Jul 2021, at 11:16, Julien Grall wrote:
>>>
>>> Hi Bertrand,
>>>
>>> On 29/06/2021 18:08, Bertrand Marquis wrote:
Define a
On Wed, Jul 07, 2021 at 05:40:02PM +0200, Jan Beulich wrote:
> On 01.07.2021 16:09, Anthony PERARD wrote:
> > And thus avoiding checking for those variable over and over again.
> >
> > Signed-off-by: Anthony PERARD
>
> Acked-by: Jan Beulich
> in its present shape since all you do is move
flight 163594 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163594/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-nested-amd 16 xen-boot/l1 fail REGR. vs. 163458
Tests which are
On Wed, Jul 07, 2021 at 05:26:13PM +0200, Jan Beulich wrote:
> On 01.07.2021 16:09, Anthony PERARD wrote:
> > --- a/xen/test/Makefile
> > +++ b/xen/test/Makefile
> > @@ -4,15 +4,10 @@ tests all: build
> >
> > ifneq ($(XEN_TARGET_ARCH),x86_32)
> > # Xen 32-bit x86 hypervisor no longer
On Wed, Jul 07, 2021 at 05:15:44PM +0200, Jan Beulich wrote:
> On 01.07.2021 16:09, Anthony PERARD wrote:
> > The make variable $(subdir-y) isn't used yet but will be in a
> > following patch. Anything in $(subdir-y) doesn't to have a '/' as
> > suffix as we already now it's a directory.
> >
> >
On Wed, Jul 07, 2021 at 05:03:12PM +0200, Jan Beulich wrote:
> On 01.07.2021 16:09, Anthony PERARD wrote:
> > Signed-off-by: Anthony PERARD
>
> Hmm, I was clearly under the impression (or at least assuming)
> that $(targets) would be included in what gets cleaned by the
> general rule.
On Wed, Jul 07, 2021 at 04:58:29PM +0200, Jan Beulich wrote:
> On 01.07.2021 16:09, Anthony PERARD wrote:
> > Improvement are:
> > - give the path to xlat.lst as argument
> > - include `grep -v` in compat-build-source.py script, we don't need to
> > write this in several scripted language.
> >
flight 163602 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163602/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 163474
Tests which
On Tue, Jul 06, 2021 at 12:59:57PM -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, Jul 06, 2021 at 05:57:21PM +0100, Will Deacon wrote:
> > On Tue, Jul 06, 2021 at 10:46:07AM -0400, Konrad Rzeszutek Wilk wrote:
> > > On Tue, Jul 06, 2021 at 04:05:13PM +0200, Christoph Hellwig wrote:
> > > > On Tue,
On Wed, Jul 07, 2021 at 04:45:11PM +0200, Jan Beulich wrote:
> On 01.07.2021 16:09, Anthony PERARD wrote:
> > xen/Makefile| 11 ---
> > xen/Rules.mk| 2 +-
> > xen/arch/x86/mm/Makefile| 9 -
> >
The alternative call infrastructure is x86-only for now, but the common iommu
code has a variant and more common code wants to use the infrastructure.
Introduce CONFIG_ALTERNATIVE_CALL and a conditional implemetnation so common
code can use the optimisation when available, without requiring all
On 12/07/2021 12:03, Bertrand Marquis wrote:
Hi Julien,
Hi Bertrand,
On 12 Jul 2021, at 11:16, Julien Grall wrote:
Hi Bertrand,
On 29/06/2021 18:08, Bertrand Marquis wrote:
Define a sanitize_cpu function to be called on secondary cores to
sanitize the cpuinfo structure from the boot
On Thu, Jul 08, 2021 at 01:03:46PM +0100, Andrew Cooper wrote:
> On 01/07/2021 15:09, Anthony PERARD wrote:
> > diff --git a/xen/Rules.mk b/xen/Rules.mk
> > index f778058f80a6..6a0cdfde2eed 100644
> > --- a/xen/Rules.mk
> > +++ b/xen/Rules.mk
> > @@ -147,17 +147,22 @@ include
Hi Julien,
> On 12 Jul 2021, at 11:16, Julien Grall wrote:
>
> Hi Bertrand,
>
> On 29/06/2021 18:08, Bertrand Marquis wrote:
>> Define a sanitize_cpu function to be called on secondary cores to
>> sanitize the cpuinfo structure from the boot CPU.
>> The safest value is taken when possible and
On Wed, Jul 07, 2021 at 04:25:33PM +0200, Jan Beulich wrote:
> On 01.07.2021 16:09, Anthony PERARD wrote:
> > In Arm and X86 makefile, generating the linker script is the same, so
> > we can simply have both call the same macro.
> >
> > We need to add *.lds files into extra-y so that Rules.mk can
On Wed, Jul 07, 2021 at 04:18:18PM +0200, Jan Beulich wrote:
> On 01.07.2021 16:09, Anthony PERARD wrote:
> > xen/Rules.mk| 7 +--
> > xen/arch/x86/mm/Makefile| 2 +-
> > xen/arch/x86/mm/hap/Makefile| 2 +-
> > xen/arch/x86/mm/shadow/Makefile | 2 +-
> > 4
Hi Julien,
> On 12 Jul 2021, at 10:36, Julien Grall wrote:
>
>
>
> On 29/06/2021 18:08, Bertrand Marquis wrote:
>> Import structures declared in Linux file arch/arm64/kernel/cpufeature.c
>> and import the required types.
>> Current code has been imported from Linux 5.13-rc5 (Commit ID
>>
Hi Bertrand,
On 29/06/2021 18:08, Bertrand Marquis wrote:
Define a sanitize_cpu function to be called on secondary cores to
sanitize the cpuinfo structure from the boot CPU.
The safest value is taken when possible and the system is marked tainted
if we encounter values which are incompatible
flight 163595 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163595/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 163474
Tests which
Hi Christoph and Robin:
I introduced new interface set_memory_decrypted_map() to hide all
the hypervisor code behind it in the latest version. In current generic
code, only swiotlb bounce buffer needs to be decrypted and remapped in
the same time and so keep set_memory_decrypted(). If there
On 29/06/2021 18:08, Bertrand Marquis wrote:
Import structures declared in Linux file arch/arm64/kernel/cpufeature.c
and import the required types.
Current code has been imported from Linux 5.13-rc5 (Commit ID
cd1245d75ce93b8fd206f4b34eb58bcfe156d5e9)
Those structure will be used to sanitize
flight 163577 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163577/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-freebsd11-amd64 13 guest-startfail REGR. vs. 163321
Hi Igor,
On 08/07/2021 03:06, Igor Druzhinin wrote:
On 07/07/2021 14:21, Julien Grall wrote:
On 07/07/2021 14:14, Jan Beulich wrote:
On 07.07.2021 14:59, Julien Grall wrote:
On 07/07/2021 13:54, Jan Beulich wrote:
On 07.07.2021 14:51, Julien Grall wrote:
On 07/07/2021 02:02, Igor Druzhinin
AArch64 system registers are 64bit whereas AArch32 ones
are 32bit or 64bit. MSR/MRS are expecting 64bit values thus
we should get rid of helpers READ/WRITE_SYSREG32
in favour of using READ/WRITE_SYSREG.
The last place in code making use of READ/WRITE_SYSREG32
on arm64 is in TVM_REG macro defining
flight 163585 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163585/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 162359
On 12.07.2021 10:33, Julien Grall wrote:
>
>
> On 12/07/2021 07:26, Michal Orzel wrote:
>> Hi Julien,
>
> Hi Michal,
>
>> On 09.07.2021 17:21, Julien Grall wrote:
>>> Hi Michal,
>>>
>>> On 09/07/2021 13:40, Michal Orzel wrote:
AArch64 system registers are 64bit whereas AArch32 ones
Hi Juergen,
On 09/07/2021 13:34, Juergen Gross wrote:
On 08.07.21 19:40, Julien Grall wrote:
Hi Juergen,
On 08/06/2021 06:58, Juergen Gross wrote:
Xenstored is absolutely mandatory for a Xen host and it can't be
restarted, so being killed by OOM-killer in case of memory shortage is
to be
On 12/07/2021 07:26, Michal Orzel wrote:
Hi Julien,
Hi Michal,
On 09.07.2021 17:21, Julien Grall wrote:
Hi Michal,
On 09/07/2021 13:40, Michal Orzel wrote:
AArch64 system registers are 64bit whereas AArch32 ones
are 32bit or 64bit. MSR/MRS are expecting 64bit values thus
we should get
flight 163573 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163573/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-xsm7 xen-install fail REGR. vs. 152332
flight 163588 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163588/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-amd64-libvirt
flight 163568 xen-unstable real [real]
flight 163591 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/163568/
http://logs.test-lab.xenproject.org/osstest/logs/163591/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be
Hi Julien,
On 09.07.2021 17:21, Julien Grall wrote:
> Hi Michal,
>
> On 09/07/2021 13:40, Michal Orzel wrote:
>> AArch64 system registers are 64bit whereas AArch32 ones
>> are 32bit or 64bit. MSR/MRS are expecting 64bit values thus
>> we should get rid of helpers READ/WRITE_SYSREG32
>> in favour
flight 163586 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163586/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 163474
Tests which
74 matches
Mail list logo
