Hi Oleksii,
Please see below.
On 02/06/2025 19:37, Oleksii Kurochko wrote:
> Hello everyone,
>
> This email only tracks big items for xen.git tree. Please reply for
> items you
> would like to see in 4.21 so that people have an idea what is going on
> and
> prioritise accordingly.
>
> You're we
Hi Oleksii,
Please see below.
On 02/06/2025 19:37, Oleksii Kurochko wrote:
> Hello everyone,
>
> This email only tracks big items for xen.git tree. Please reply for
> items you
> would like to see in 4.21 so that people have an idea what is going on
> and
> prioritise accordingly.
>
> You're we
On Fri, Mar 21, 2025 at 5:31 AM Juergen Gross wrote:
>
> In order to support kexec any memory used during copying the new
> kernel to its final destination must not overlap with the destination
> area.
>
> In order to achieve that add a new interface allowing to mark all
> allocatable memory below
On Fri, Mar 21, 2025 at 5:30 AM Juergen Gross wrote:
>
> Build the parameters for the new kernel, consisting of the
> hvm_start_info struct, the memory map and the command line.
>
> Signed-off-by: Juergen Gross
> @@ -212,4 +213,61 @@ void kexec_set_param_loc(const char *cmdline)
> +
> +/* T
On Fri, Mar 21, 2025 at 5:31 AM Juergen Gross wrote:
>
> Rename set_readonly() to change_readonly() and add a parameter
> specifying whether it should set the kernel to readonly or to writable.
> At the same time move the boundary setting from the only caller into
> the function itself, avoiding t
On Fri, Mar 21, 2025 at 5:30 AM Juergen Gross wrote:
>
> In order to allow writing the new kernel, make the readonly area
> covering current kernel text writable again.
>
> Signed-off-by: Juergen Gross
Reviewed-by: Jason Andryuk
On Fri, Mar 21, 2025 at 5:32 AM Juergen Gross wrote:
>
> Add a kexec_call() macro which will provide the capability to register
> a function for being called when doing a kexec() call. The called
> functions will be called with a boolean parameter "undo" indicating
> whether a previous call needs
On Fri, Mar 21, 2025 at 5:30 AM Juergen Gross wrote:
>
> With all kexec preparations done, activate the new kernel.
>
> Signed-off-by: Juergen Gross
> ---
> kexec.c | 17 +++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
> diff --git a/kexec.c b/kexec.c
> index 2db876e8..85b
On Fri, Mar 21, 2025 at 5:25 AM Juergen Gross wrote:
>
> Add the code and data definitions of the final kexec stage.
>
> Put the code and related data into a dedicated section in order to be
> able to copy it to another location. For this reason there must be no
> absolute relocations being used i
On Fri, Mar 21, 2025 at 5:25 AM Juergen Gross wrote:
>
> Add a new config option CONFIG_KEXEC for support of kexec-ing into a
> new mini-os kernel. Add a related kexec.c source and a kexec.h header.
>
> For now allow CONFIG_KEXEC to be set only for PVH variant of mini-os.
>
> Signed-off-by: Juerge
On Fri, Mar 21, 2025 at 5:25 AM Juergen Gross wrote:
>
> Analyze the properties of the new kernel to be loaded by kexec. The
> data needed is:
>
> - upper boundary in final location
> - copy and memory clear operations
> - entry point and entry parameter
>
> Signed-off-by: Juergen Gross
> +
> +s
On Fri, Mar 21, 2025 at 5:25 AM Juergen Gross wrote:
>
> Finalize the location and the size of the parameters for the new
> kernel. This is needed in order to avoid allocating new memory in the
> area occupied by the new kernel and parameters.
>
> Signed-off-by: Juergen Gross
Reviewed-by: Jason
On Fri, Mar 21, 2025 at 5:30 AM Juergen Gross wrote:
>
> Copying the new kexec kernel must not overwrite any pages still needed
> during this process. Those are especially the GDT, IDT and page tables.
>
> Move those to new allocated pages and update any related pointers.
>
> In case the kexec pro
13 matches
Mail list logo
