Re: [PATCH] hvmloader: indicate firmware tables as ACPI NVS in e820

2020-08-28 Thread Igor Druzhinin
On 28/08/2020 08:51, Jan Beulich wrote: > On 28.08.2020 02:13, Igor Druzhinin wrote: >> Guest kernel does need to know in some cases where the tables are located >> to treat these regions properly. One example is kexec process where >> the first kernel needs to pass firmware region locations to the

Re: [PATCH] hvmloader: indicate firmware tables as ACPI NVS in e820

2020-08-28 Thread Jan Beulich
On 28.08.2020 16:45, Igor Druzhinin wrote: > On 28/08/2020 08:51, Jan Beulich wrote: >> On 28.08.2020 02:13, Igor Druzhinin wrote: >>> Guest kernel does need to know in some cases where the tables are located >>> to treat these regions properly. One example is kexec process where >>> the first kern

Re: [PATCH] hvmloader: indicate firmware tables as ACPI NVS in e820

2020-08-28 Thread Jan Beulich
On 28.08.2020 02:13, Igor Druzhinin wrote: > Guest kernel does need to know in some cases where the tables are located > to treat these regions properly. One example is kexec process where > the first kernel needs to pass firmware region locations to the second > kernel which is now a requirement a

[PATCH] hvmloader: indicate firmware tables as ACPI NVS in e820

2020-08-27 Thread Igor Druzhinin
Guest kernel does need to know in some cases where the tables are located to treat these regions properly. One example is kexec process where the first kernel needs to pass firmware region locations to the second kernel which is now a requirement after 02a3e3cdb7f12 ("x86/boot: Parse SRAT table and