Hi,
On 04/03/2022 17:46, Marco Solieri wrote:
From: Luca Miccio
Based on the intrinsic nature of cache coloring, it is trivial to state
that each domain that is colored is also not direct mapped.
Set the directmap variable to false when coloring is enabled.
This is basically fixing a bug
flight 168483 xen-4.15-testing real [real]
flight 168497 xen-4.15-testing real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/168483/
http://logs.test-lab.xenproject.org/osstest/logs/168497/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
Hi,
On 04/03/2022 17:46, Marco Solieri wrote:
From: Luca Miccio
During domU creation process the colors selection has to be passed to
the Xen hypercall.
This is generally done using what Xen calls GUEST_HANDLE_PARAMS. In this
case a simple bitmask for the coloring configuration suffices.
flight 168495 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168495/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
Hi,
On 04/03/2022 17:46, Marco Solieri wrote:
From: Luca Miccio
The size of the LLC way is a crucial parameter for the cache coloring
support, since it determines the maximum number of available colors on
the platform. This parameter can currently be retrieved only from
the way_size bootarg
flight 168485 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168485/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-win7-amd64 19 guest-stopfail like 168334
test-amd64-amd64-xl-qemut-win7-amd64
Hi,
On 04/03/2022 17:46, Marco Solieri wrote:
From: Luca Miccio
Dom0 color configuration is parsed in the Xen command line. Add an
helper function to check the user selection. If no configuration is
provided by the user, all the available colors supported by the
hardware will be assigned to
flight 168486 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168486/
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. 168466
Tests which did
flight 168492 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168492/
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
The definition of compat_platform_op_t is in compat/platform.h
already, so include that file from hypercall.h instead of repeating
the typedef.
This allows to remove the related include statement from
arch/x86/x86_64/platform_hypercall.c.
Signed-off-by: Juergen Gross
Acked-by: Jan Beulich
---
Switch some non style compliant types (u32, s32, s64) of hypercall
handler parameters to style compliant ones.
Signed-off-by: Juergen Gross
Reviewed-by: Jan Beulich
---
V4:
- carved out from following patch (Julien Grall)
---
xen/arch/x86/include/asm/hypercall.h | 10 +-
do_physdev_op() prototypes on Arm and x86 differ in their return type,
so rename the Arm one in order to prepare using a common generated
header file.
Signed-off-by: Juergen Gross
---
V4:
- new patch
---
xen/arch/arm/include/asm/hypercall.h | 2 +-
xen/arch/arm/physdev.c | 2 +-
Instead of repeating similar data multiple times use a single source
file and a generator script for producing prototypes and call sequences
of the hypercalls.
As the script already knows the number of parameters used add generating
a macro for populating an array with the number of parameters
Today most hypercall handlers have a return type of long, while the
compat ones return an int. There are a few exceptions from that rule,
however.
Get rid of the exceptions by letting compat handlers always return int
and others always return long, with the exception of the Arm specific
Instead of using a function table use the generated macros for calling
the appropriate hypercall handlers.
This makes the calls of the handlers type safe.
For deprecated hypercalls define stub functions.
Signed-off-by: Juergen Gross
Tested-by: Michal Orzel
---
V2:
- make hypercall_args[]
Remove the hypercall handler's prototypes in the related header files
and use the generated ones instead.
Some handlers having been static before need to be made globally
visible.
Signed-off-by: Juergen Gross
Acked-by: Jan Beulich
---
xen/arch/arm/include/asm/hypercall.h | 1 -
Instead of using a function table use the generated macros for calling
the appropriate hypercall handlers.
This is beneficial to performance and avoids speculation issues.
With calling the handlers using the correct number of parameters now
it is possible to do the parameter register clobbering
The entry point used for the vcpu_op hypercall on Arm is different
from the one on x86 today, as some of the common sub-ops are not
supported on Arm. The Arm specific handler filters out the not
supported sub-ops and then calls the common handler. This leads to the
weird call hierarchy:
In order to avoid indirect function calls on the hypercall path as
much as possible this series is removing the hypercall function tables
and is replacing the hypercall handler calls via the function array
by automatically generated call macros.
Another by-product of generating the call macros is
Instead of including asm/hypercall.h always use xen/hypercall.h.
Additionally include xen/hypercall.h from all sources containing a
hypercall handler.
This prepares for generating the handlers' prototypes at build time.
Add a guard in asm/hypercall.h to catch direct inclusion.
Signed-off-by:
Now that the hypercall handlers are all being called directly instead
through a function vector, the "cf_check" attribute can be removed.
Signed-off-by: Juergen Gross
---
V4:
- new patch
---
xen/arch/x86/compat.c | 6 +++---
xen/arch/x86/cpu/mcheck/mce.c | 2 +-
Xen enabled CET for supporting architectures. The control flow aspect of
CET expects functions that can be called indirectly (i.e., via function
pointers) to start with an ENDBR64 instruction. Otherwise a control flow
exception is raised.
This expectation breaks livepatching flows because we
flight 168488 qemu-mainline real [real]
flight 168499 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/168488/
http://logs.test-lab.xenproject.org/osstest/logs/168499/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
On 08.03.22 15:01, Andrew Cooper wrote:
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know the
content is safe.
For livepatching, we need to look at a potentially clobbered function and
Hi Jan,
> On 4 Mar 2022, at 7:23 am, Jan Beulich wrote:
>
> On 03.03.2022 17:31, Rahul Singh wrote:
>>> On 1 Mar 2022, at 1:55 pm, Jan Beulich wrote:
>>> On 01.03.2022 14:34, Rahul Singh wrote:
> On 24 Feb 2022, at 2:57 pm, Jan Beulich wrote:
> On 15.02.2022 16:25, Rahul Singh wrote:
On 09.03.2022 11:08, Rahul Singh wrote:
> Hi Jan,
>
>> On 4 Mar 2022, at 7:23 am, Jan Beulich wrote:
>>
>> On 03.03.2022 17:31, Rahul Singh wrote:
On 1 Mar 2022, at 1:55 pm, Jan Beulich wrote:
On 01.03.2022 14:34, Rahul Singh wrote:
>> On 24 Feb 2022, at 2:57 pm, Jan Beulich
flight 168480 xen-4.12-testing real [real]
flight 168494 xen-4.12-testing real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/168480/
http://logs.test-lab.xenproject.org/osstest/logs/168494/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
From: Julien Grall
At the moment, switch_ttbr() is switching the TTBR whilst the MMU is
still on.
Switching TTBR is like replacing existing mappings with new ones. So
we need to follow the break-before-make sequence.
In this case, it means the MMU needs to be switched off while the
TTBR is
Hi,
On 04/03/2022 19:47, Julien Grall wrote:
On 04/03/2022 17:46, Marco Solieri wrote:
From: Luca Miccio
Introduce a new implementation of setup_pagetables that uses coloring
logic in order to isolate Xen code using its color selection.
Page tables construction is essentially copied, except
On 09.03.2022 12:34, Juergen Gross wrote:
> XEN_SHSTK should be on per default now that it is supported officially.
> Only let the prompt depend on EXPERT.
>
> Signed-off-by: Juergen Gross
Reviewed-by: Jan Beulich
> --- a/xen/arch/x86/Kconfig
> +++ b/xen/arch/x86/Kconfig
> @@ -117,8 +117,8 @@
On Tue, Mar 08, 2022 at 05:31:17PM +, Jane Malalane wrote:
> Add XEN_SYSCTL_PHYSCAP_X86_ASSISTED_XAPIC and
> XEN_SYSCTL_PHYSCAP_X86_ASSISTED_X2APIC to report accelerated xapic
> and x2apic, on x86 hardware.
> No such features are currently implemented on AMD hardware.
>
> HW assisted xAPIC
On Wed, Mar 09, 2022 at 10:47:06AM +, Rahul Singh wrote:
> Hi Roger,
>
> > On 9 Mar 2022, at 10:16 am, Roger Pau Monné wrote:
> >
> > On Wed, Mar 09, 2022 at 10:08:12AM +, Rahul Singh wrote:
> >> Hi Jan,
> >>
> >>> On 4 Mar 2022, at 7:23 am, Jan Beulich wrote:
> >>>
> >>> On
On Tue, Mar 08, 2022 at 05:36:43PM +, Jane Malalane wrote:
> diff --git a/tools/libs/light/libxl_arm.c b/tools/libs/light/libxl_arm.c
> index 39fdca1b49..ba5b8f433f 100644
> --- a/tools/libs/light/libxl_arm.c
> +++ b/tools/libs/light/libxl_arm.c
> @@ -1384,8 +1384,9 @@ void
>
On Wed, Mar 09, 2022 at 10:08:12AM +, Rahul Singh wrote:
> Hi Jan,
>
> > On 4 Mar 2022, at 7:23 am, Jan Beulich wrote:
> >
> > On 03.03.2022 17:31, Rahul Singh wrote:
> >>> On 1 Mar 2022, at 1:55 pm, Jan Beulich wrote:
> >>> On 01.03.2022 14:34, Rahul Singh wrote:
> > On 24 Feb 2022,
On 09.03.2022 10:30, Roger Pau Monné wrote:
> On Tue, Mar 08, 2022 at 05:58:49PM +0100, Jan Beulich wrote:
>> On 08.03.2022 17:41, Roger Pau Monné wrote:
>>> On Tue, Mar 08, 2022 at 04:13:55PM +0100, Jan Beulich wrote:
On 08.03.2022 15:46, Roger Pau Monné wrote:
> On Tue, Mar 08, 2022 at
The of_find_compatible_node() function returns a node pointer with
refcount incremented, We should use of_node_put() on it when done
Add the missing of_node_put() to release the refcount.
Fixes: 9b08aaa3199a ("ARM: XEN: Move xen_early_init() before efi_init()")
Signed-off-by: Miaoqian Lin
---
Hi Roger,
> On 9 Mar 2022, at 10:16 am, Roger Pau Monné wrote:
>
> On Wed, Mar 09, 2022 at 10:08:12AM +, Rahul Singh wrote:
>> Hi Jan,
>>
>>> On 4 Mar 2022, at 7:23 am, Jan Beulich wrote:
>>>
>>> On 03.03.2022 17:31, Rahul Singh wrote:
> On 1 Mar 2022, at 1:55 pm, Jan Beulich wrote:
From: Julien Grall
In a follow-up patch, the base address for the common mappings will
vary between arm32 and arm64. To avoid any duplication, define
every mapping in the common region from the previous one.
Take the opportunity to add mising *_SIZE for some mappings.
Signed-off-by: Julien
From: Julien GralL
In follow-up patches we will need to have part of Xen identity mapped in
order to safely switch the TTBR.
On some platform, the identity mapping may have to start at 0. If we always
keep the identity region mapped, NULL pointer ference would lead to access
to valid mapping.
From: Julien Grall
Xen is currently not fully compliant with the Arm because it will
switch the TTBR with the MMU on.
In order to be compliant, we need to disable the MMU before
switching the TTBR. The implication is the page-tables should
contain an identity mapping of the code switching the
From: Julien Grall
Hi all,
Currently, Xen on Arm will switch TTBR whilst the MMU is on. This is
similar to replacing existing mappings with new ones. So we need to
follow a break-before-make sequence.
When switching the TTBR, we need to temporary disable the MMU
before update the TTBR. This
From: Julien Grall
Switching TTBR while the MMU is on is not safe. Now that the identity
mapping will not clash with the rest of the memory layout, we can avoid
creating temporary page-tables every time a CPU is brought up.
Signed-off-by: Julien Grall
---
xen/arch/arm/arm64/head.S | 29
XEN_SHSTK should be on per default now that it is supported officially.
Only let the prompt depend on EXPERT.
Signed-off-by: Juergen Gross
---
xen/arch/x86/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/xen/arch/x86/Kconfig b/xen/arch/x86/Kconfig
index
On Wed, Mar 09, 2022 at 04:40:24PM +0100, Jan Beulich wrote:
> On 09.03.2022 16:03, Roger Pau Monné wrote:
> > On Mon, Feb 14, 2022 at 04:07:09PM +0100, Jan Beulich wrote:
> >> On 01.02.2022 17:46, Roger Pau Monne wrote:
> >>> Use the logic to set shadow SPEC_CTRL values in order to implement
>
On 09.03.2022 16:56, Jane Malalane wrote:
> On 08/03/2022 14:41, Jan Beulich wrote:
>> [CAUTION - EXTERNAL EMAIL] DO NOT reply, click links, or open attachments
>> unless you have verified the sender and know the content is safe.
>>
>> On 08.03.2022 15:31, Jane Malalane wrote:
>>> On 08/03/2022
Hi Roger,
On 09/03/2022 12:28, Roger Pau Monné wrote:
On Tue, Mar 08, 2022 at 02:52:55PM +, Julien Grall wrote:
Hi,
On 08/03/2022 13:49, Roger Pau Monne wrote:
Hello,
The content in v3 has been split in two patches, but is still mostly the
same. The main difference is that first patch
flight 168481 xen-4.13-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168481/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemut-win7-amd64 19 guest-stop fail like 167817
test-armhf-armhf-libvirt 16
flight 168482 xen-4.14-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168482/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-vhd broken
test-armhf-armhf-xl-vhd 5
On Tue, Mar 08, 2022 at 05:58:49PM +0100, Jan Beulich wrote:
> On 08.03.2022 17:41, Roger Pau Monné wrote:
> > On Tue, Mar 08, 2022 at 04:13:55PM +0100, Jan Beulich wrote:
> >> On 08.03.2022 15:46, Roger Pau Monné wrote:
> >>> On Tue, Mar 08, 2022 at 03:09:17PM +0100, Jan Beulich wrote:
> On
On Tue, Mar 08, 2022 at 02:52:55PM +, Julien Grall wrote:
> Hi,
>
> On 08/03/2022 13:49, Roger Pau Monne wrote:
> > Hello,
> >
> > The content in v3 has been split in two patches, but is still mostly the
> > same. The main difference is that first patch does a bit of cleanup of
> > the build
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Roger Pau Monné
CC: Wei Liu
---
CHANGELOG.md | 6 ++
1 file changed, 6 insertions(+)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 83d85fad5bbc..577517383ec9 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,12 @@ The format is
Andrew Cooper (2):
x86/CET: Remove XEN_SHSTK's dependency on EXPERT
Changelog: Add __ro_after_init and CET
CHANGELOG.md | 6 ++
xen/arch/x86/Kconfig | 4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
--
2.11.0
On 09.03.2022 13:28, Roger Pau Monne wrote:
> If livepatching support is enabled build the hypervisor with
> -f{function,data}-sections compiler options, which is required by the
> livepatching tools to detect changes and create livepatches.
>
> This shouldn't result in any functional change on
On 08.03.2022 18:36, Jane Malalane wrote:
> @@ -685,13 +687,31 @@ int arch_sanitise_domain_config(struct
> xen_domctl_createdomain *config)
> }
> }
>
> -if ( config->arch.misc_flags & ~XEN_X86_MSR_RELAXED )
> +if ( config->arch.misc_flags & ~(XEN_X86_MSR_RELAXED |
> +
On Tue, Feb 15, 2022 at 04:33:15PM +, Jane Malalane wrote:
> On 15/02/2022 15:21, Jan Beulich wrote:
> > [CAUTION - EXTERNAL EMAIL] DO NOT reply, click links, or open attachments
> > unless you have verified the sender and know the content is safe.
> >
> > On 15.02.2022 16:10, Jane Malalane
flight 168484 xen-4.16-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168484/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 168136
On 04.03.2022 18:46, Marco Solieri wrote:
> @@ -438,6 +441,263 @@ mfn_t __init alloc_boot_pages(unsigned long nr_pfns,
> unsigned long pfn_align)
>
>
>
> +static DEFINE_SPINLOCK(heap_lock);
Please take the opportunity and shrink the number of consecutive blank lines
above here.
> +
>
CET-SS hardware is now available from multiple vendors, and the feature has
downstream users. Enable it by default.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Roger Pau Monné
CC: Wei Liu
---
xen/arch/x86/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On 09.03.2022 13:39, Andrew Cooper wrote:
> --- a/xen/arch/x86/Kconfig
> +++ b/xen/arch/x86/Kconfig
> @@ -117,8 +117,8 @@ config HVM
> If unsure, say Y.
>
> config XEN_SHSTK
> - bool "Supervisor Shadow Stacks (EXPERT)"
> - depends on HAS_AS_CET_SS && EXPERT
> + bool
On 09.03.2022 13:39, Andrew Cooper wrote:
> --- a/CHANGELOG.md
> +++ b/CHANGELOG.md
> @@ -6,6 +6,12 @@ The format is based on [Keep a
> Changelog](https://keepachangelog.com/en/1.0.0/)
>
> ## [unstable
> UNRELEASED](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=staging) -
> TBD
>
On Tue, Mar 08, 2022 at 05:36:43PM +, Jane Malalane wrote:
> Introduce a new per-domain creation x86 specific flag to
> select whether hardware assisted virtualization should be used for
> x{2}APIC.
>
> A per-domain option is added to xl in order to select the usage of
> x{2}APIC hardware
So it can be explicitly placed ahead of the rest of the .text content
in the linker script (and thus the resulting image). This is a
prerequisite for further work that will add a catch-all to the text
section (.text.*).
Note that placement of the sections inside of .text is also slightly
adjusted
If livepatching support is enabled build the hypervisor with
-f{function,data}-sections compiler options, which is required by the
livepatching tools to detect changes and create livepatches.
This shouldn't result in any functional change on the hypervisor
binary image, but does however require
Hello,
The content in v3 has been split in two patches, but is still mostly the
same. The main difference is that first patch does a bit of cleanup of
the build logic now that the header object file doesn't need to be the
first one passed to the linker script.
Thanks, Roger.
Roger Pau Monne
On 04.03.2022 18:46, Marco Solieri wrote:
> --- a/xen/common/page_alloc.c
> +++ b/xen/common/page_alloc.c
> @@ -230,6 +230,13 @@ static bool __read_mostly scrub_debug;
> #define scrub_debugfalse
> #endif
>
> +#ifdef CONFIG_COLORING
> +/* Minimum size required for buddy allocator to work
When verifying that a livepatch can be applied, we may as well want to
inspect the target function to be patched. To do so, we need to resolve
this function's address before running the arch-specific
livepatch_verify hook.
Signed-off-by: Bjoern Doebel
Acked-by: Konrad Rzeszutek Wilk
On Mon, Feb 14, 2022 at 04:07:09PM +0100, Jan Beulich wrote:
> On 01.02.2022 17:46, Roger Pau Monne wrote:
> > 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
On Wed, Mar 09, 2022 at 02:58:06PM +, Andrew Cooper wrote:
> On 09/03/2022 12:28, Roger Pau Monne wrote:
> > diff --git a/xen/arch/x86/xen.lds.S b/xen/arch/x86/xen.lds.S
> > index 960c51eb4c..4103763f63 100644
> > --- a/xen/arch/x86/xen.lds.S
> > +++ b/xen/arch/x86/xen.lds.S
> > @@ -87,9
On 3/9/22 1:18 AM, Christoph Hellwig wrote:
On Tue, Mar 08, 2022 at 04:38:21PM -0500, Boris Ostrovsky wrote:
On 3/1/22 5:53 AM, Christoph Hellwig wrote:
Allow to pass a remap argument to the swiotlb initialization functions
to handle the Xen/x86 remap case. ARM/ARM64 never did any remapping
This was missed previously, and would yield a fatal #CP for any HVM domain
which issues a physdevop hypercall.
Reported-by: Juergen Gross
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Roger Pau Monné
CC: Wei Liu
CC: Juergen Gross
---
xen/arch/x86/hvm/hypercall.c | 2 +-
1 file
On 09.03.2022 16:20, Andrew Cooper wrote:
> This was missed previously, and would yield a fatal #CP for any HVM domain
> which issues a physdevop hypercall.
>
> Reported-by: Juergen Gross
> Signed-off-by: Andrew Cooper
Reviewed-by: Jan Beulich
On 09.03.2022 16:03, Roger Pau Monné wrote:
> On Mon, Feb 14, 2022 at 04:07:09PM +0100, Jan Beulich wrote:
>> On 01.02.2022 17:46, Roger Pau Monne wrote:
>>> 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
On 09.03.2022 16:50, Rahul Singh wrote:
>> On 9 Mar 2022, at 10:17 am, Jan Beulich wrote:
>> On 09.03.2022 11:08, Rahul Singh wrote:
On 4 Mar 2022, at 7:23 am, Jan Beulich wrote:
On 03.03.2022 17:31, Rahul Singh wrote:
>> On 1 Mar 2022, at 1:55 pm, Jan Beulich wrote:
>> On
On Wed, Mar 09, 2022 at 03:50:12PM +, Rahul Singh wrote:
> Hi Jan,
>
> > On 9 Mar 2022, at 10:17 am, Jan Beulich wrote:
> >
> > On 09.03.2022 11:08, Rahul Singh wrote:
> >> Hi Jan,
> >>
> >>> On 4 Mar 2022, at 7:23 am, Jan Beulich wrote:
> >>>
> >>> On 03.03.2022 17:31, Rahul Singh
On 09.03.2022 15:45, Jan Beulich wrote:
> On 04.03.2022 18:46, Marco Solieri wrote:
>> --- a/xen/common/page_alloc.c
>> +++ b/xen/common/page_alloc.c
>> @@ -230,6 +230,13 @@ static bool __read_mostly scrub_debug;
>> #define scrub_debugfalse
>> #endif
>>
>> +#ifdef CONFIG_COLORING
>> +/*
Xen enabled CET for supporting architectures. The control flow aspect of
CET expects functions that can be called indirectly (i.e., via function
pointers) to start with an ENDBR64 instruction. Otherwise a control flow
exception is raised.
This expectation breaks livepatching flows because we
On 04.03.2022 18:46, Marco Solieri wrote:
> From: Luca Miccio
>
> Initialize colored heap and allocator data structures. It is assumed
> that pages are given to the init function is in ascending order.
I don't think this is a good assumption to make.
> To
> ensure that, pages are retrieved
On 09/03/2022 12:28, Roger Pau Monne wrote:
> diff --git a/xen/arch/x86/xen.lds.S b/xen/arch/x86/xen.lds.S
> index 960c51eb4c..4103763f63 100644
> --- a/xen/arch/x86/xen.lds.S
> +++ b/xen/arch/x86/xen.lds.S
> @@ -87,9 +87,12 @@ SECTIONS
> *(.text.cold)
> *(.text.unlikely
On 09.03.2022 15:53, Bjoern Doebel wrote:
> Changes since r1:
> * use sizeof_field() to avoid unused variable warning
> * make metadata variable const in arch_livepatch_revert
> * rebase on top and make use of Andrew Cooper's was_endbr64() patch
> * use padding byte to store offset rather than
Hi Jan,
> On 9 Mar 2022, at 10:17 am, Jan Beulich wrote:
>
> On 09.03.2022 11:08, Rahul Singh wrote:
>> Hi Jan,
>>
>>> On 4 Mar 2022, at 7:23 am, Jan Beulich wrote:
>>>
>>> On 03.03.2022 17:31, Rahul Singh wrote:
> On 1 Mar 2022, at 1:55 pm, Jan Beulich wrote:
> On 01.03.2022 14:34,
On 08/03/2022 14:41, Jan Beulich wrote:
> [CAUTION - EXTERNAL EMAIL] DO NOT reply, click links, or open attachments
> unless you have verified the sender and know the content is safe.
>
> On 08.03.2022 15:31, Jane Malalane wrote:
>> On 08/03/2022 12:33, Roger Pau Monné wrote:
>>> On Tue, Mar 08,
> From: Bjoern Doebel
> Sent: Wednesday, March 9, 2022 2:53 PM
> To: xen-devel@lists.xenproject.org
> Cc: Michael Kurth ; Martin Pohlack ;
> Roger Pau Monne ; Andrew Cooper
> ; Bjoern Doebel ; Konrad
> Rzeszutek Wilk ; Ross Lagerwall
>
> Subject: [PATCH v5 2/2] xen/x86: Livepatch: support
On 09/03/2022 16:51, Jan Beulich wrote:
> [CAUTION - EXTERNAL EMAIL] DO NOT reply, click links, or open attachments
> unless you have verified the sender and know the content is safe.
>
> On 09.03.2022 16:56, Jane Malalane wrote:
>> On 08/03/2022 14:41, Jan Beulich wrote:
>>> [CAUTION - EXTERNAL
On 09.03.2022 17:31, Roger Pau Monné wrote:
> On Wed, Mar 09, 2022 at 04:40:24PM +0100, Jan Beulich wrote:
>> On 09.03.2022 16:03, Roger Pau Monné wrote:
>>> On Mon, Feb 14, 2022 at 04:07:09PM +0100, Jan Beulich wrote:
On 01.02.2022 17:46, Roger Pau Monne wrote:
> ---
flight 168490 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/168490/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 168254
build-amd64-xsm
On 09/03/2022 10:22, Jan Beulich wrote:
> On 09.03.2022 10:30, Roger Pau Monné wrote:
>> On Tue, Mar 08, 2022 at 05:58:49PM +0100, Jan Beulich wrote:
>>> On 08.03.2022 17:41, Roger Pau Monné wrote:
On Tue, Mar 08, 2022 at 04:13:55PM +0100, Jan Beulich wrote:
> On 08.03.2022 15:46, Roger
Hi,
On 04/03/2022 17:46, Marco Solieri wrote:
From: Luca Miccio
Add three new bootargs allowing configuration of cache coloring support
for Xen:
I would prefer if documentation of each command line is part of the
patch introducing them. This would help understanding some of the
87 matches
Mail list logo
