On 18.12.2024 08:15, Jürgen Groß wrote:
> On 17.12.24 17:12, Jan Beulich wrote:
>> On 17.12.2024 16:55, Jürgen Groß wrote:
>>> On 17.12.24 16:19, Jan Beulich wrote:
On 17.12.2024 15:22, Juergen Gross wrote:
> Add a bitmap with one bit per possible domid indicating the respective
> doma
On 2024/12/14 4:07, Richard Henderson wrote:
Signed-off-by: Richard Henderson
Reviewed-by: Akihiko Odaki
On 18.12.2024 18:08, Andrew Cooper wrote:
> @@ -2952,11 +2954,11 @@ static const char *guest_x86_mode_to_str(int mode)
> {
> switch ( mode )
> {
> -case 0: return "Real";
> -case 1: return "v86";
> -case 2: return "16bit";
> -case 4: return "32bit";
> -case 8: re
On 18/12/2024 17:26, Daniel P. Smith wrote:
>
>
> Hey Michal,
>
> On 12/18/24 06:04, Michal Orzel wrote:
>> Hi Daniel,
>>
>> On 18/12/2024 02:17, Daniel P. Smith wrote:
>>>
>>>
On 17/12/2024 11:47, Sergiy Kibrik wrote:
> Allow to build ARM configuration with support for initializing
On 19.12.2024 00:34, Ariel Otilibili wrote:
> The if-statement tests `res` is non-zero; meaning the case zero is never
> reached.
>
> Coverity-ID: 1055253
> Fixes: e2b1ebf4de ("x86: Support booting a bzImage format domain 0 kernel.")
> Signed-off-by: Ariel Otilibili
I certainly agree with the c
On 18/12/2024 15:58, Andrei Cherechesu wrote:
>
>
> Hi Michal,
>
> Thank you for the review.
>
> On 18/12/2024 16:26, Michal Orzel wrote:
>>
>> On 18/12/2024 11:11, Andrei Cherechesu (OSS) wrote:
>>>
>>> From: Andrei Cherechesu
>>>
>>> Introduce the SCMI-SMC layer to have some basic degree
On 18.12.2024 19:54, Andrew Cooper wrote:
> Decompressing the kernel is necessary to inspect the ELF notes, but the
> dombuilder will gunzip() secondary modules too. Specifically gunzip(), no
> other decompression algorithms.
>
> This may have been necessary in the dim and distant past, but it is
On 18.12.2024 15:25, Alessandro Zucchelli wrote:
> Rule 11.8 states as following: "A cast shall not remove any `const' or
> `volatile' qualification from the type pointed to by a pointer".
>
> Function `__hvm_copy' in `xen/arch/x86/hvm/hvm.c' is a double-use
> function, where the parameter needs t
On 2024-12-19 09:49, Jan Beulich wrote:
On 18.12.2024 15:25, Alessandro Zucchelli wrote:
Rule 11.8 states as following: "A cast shall not remove any `const' or
`volatile' qualification from the type pointed to by a pointer".
Function `__hvm_copy' in `xen/arch/x86/hvm/hvm.c' is a double-use
func
On 19.12.2024 09:58, Nicola Vetrini wrote:
> On 2024-12-19 09:49, Jan Beulich wrote:
>> On 18.12.2024 15:25, Alessandro Zucchelli wrote:
>>> Rule 11.8 states as following: "A cast shall not remove any `const' or
>>> `volatile' qualification from the type pointed to by a pointer".
>>>
>>> Function `
On 17/12/24 16:13, Philippe Mathieu-Daudé wrote:
Philippe Mathieu-Daudé (3):
hw/xen: Remove unnecessary 'exec/cpu-common.h' header
system/numa: Remove unnecessary 'exec/cpu-common.h' header
system/accel-ops: Remove unnecessary 'exec/cpu-common.h' header
Series queued.
Hi Andrew,
On 12/18/24 6:49 AM, Andrew Cooper wrote:
> Credit2 has no buisness including asm/cpufeature.h or asm/processor.h.
>
> This was caused by a bad original abstraction, and an even less wise attempt
> to fix the build on my behalf. It is also the sole reason why PPC and RISC-V
> need cpu
On 12/18/24 7:54 PM, Andrew Cooper wrote:
Decompressing the kernel is necessary to inspect the ELF notes, but the
dombuilder will gunzip() secondary modules too. Specifically gunzip(), no
other decompression algorithms.
This may have been necessary in the dim and distant past, but it is broken
On 04.12.2024 11:20, Oleksii Kurochko wrote:
> This email only tracks big items for xen.git tree. Please reply for items you
> would like to see in 4.20 so that people have an idea what is going on and
> prioritise accordingly.
>
> You're welcome to provide description and use cases of the feature
Hello,
Le 18/12/2024 à 18:08, Andrew Cooper a écrit :
> From: Teddy Astie
>
> In many places of x86 HVM code, constants integer are used to indicate in
> what mode is
> running the CPU (real, vm86, 16-bits, 32-bits, 64-bits). However, these
> constants are
> are written directly as integer whic
On 19/12/2024 11:13 am, Sergiy Kibrik wrote:
> It should be CONFIG_ARCH_VCPU_IOREQ_COMPLETION (as in Kconfig) and not
> misspelled CONFIG_VCPU_ARCH_IOREQ_COMPLETION.
> Bug introduced by:
>
> 979cfdd3e5 ioreq: do not build arch_vcpu_ioreq_completion() for non-VMX
> configurations
>
> Signed-off-by:
Le 19/12/2024 à 12:35, Andrew Cooper a écrit :
> On 19/12/2024 10:46 am, Teddy Astie wrote:
>> Hello,
>>
>> Le 18/12/2024 à 18:08, Andrew Cooper a écrit :
>>> From: Teddy Astie
>>>
>>> In many places of x86 HVM code, constants integer are used to indicate in
>>> what mode is
>>> running the CPU (
On 12/11/24 11:21, Daniel P. Smith wrote:
On 12/2/24 07:02, Jan Beulich wrote:
On 23.11.2024 19:20, Daniel P. Smith wrote:
--- a/xen/arch/x86/domain_builder/fdt.h
+++ b/xen/arch/x86/domain_builder/fdt.h
@@ -27,6 +27,24 @@ static inline int __init fdt_cell_as_u64(const
fdt32_t *cell, uint64_t *
All,
we're pleased to announce the release of another bug fixing Xen version.
Xen 4.18.4 is available from its git repository
http://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=refs/heads/stable-4.18
(tag RELEASE-4.18.4) or from the XenProject download page
https://xenproject.org/resources/dow
> commit 7b89ea44dbcb965b6b67c8de5092ea2b95d4c6f9
> Author: James Dingwall
> Date: Tue Nov 5 11:16:20 2024 +
>
> libxl: drop setting XEN_QEMU_CONSOLE_LIMIT in the environment (XSA-180 /
> CVE-2014-3672)
>
> The corresponding code in the Xen qemu repository was not applied from
On 19.12.2024 16:37, Jan Beulich wrote:
> Xen 4.18.4 is available from its git repository
> http://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=refs/heads/stable-4.18
> (tag RELEASE-4.18.4) or from the XenProject download page
> https://xenproject.org/resources/downloads/.
>
> We recommend all u
Hi,
It crashes on boot like below, most of the times. But sometimes (rarely)
it manages to stay alive. Below I'm pasting few of the crashes that look
distinctly different, if you follow the links, you can find more of
them. IMHO it looks like some memory corruption bug somewhere. I tested
also Lin
From: Michal Orzel
Add requirements for dom0less domain creation.
Signed-off-by: Michal Orzel
Signed-off-by: Ayan Kumar Halder
---
Changes from -
v1 - 1. As the dom0less domain creation requirements specifies the dt properties
for creating domains, it has been moved to product requirements. P
From: Stefano Stabellini
It can be beneficial for some dom0less systems to further reduce Xen footprint
and disable some hypercalls handling code, which may not to be used & required
in such systems. Each hypercall has a separate option to keep configuration
flexible.
Options to disable hypercal
Except setting CONFIG_QEMU_PLATFORM=y in tiny64_defconfig,
CONFIG_QEMU_PLATFORM should be fixed for RISC-V's randconfig job.
Otherwise, an expected compilation error for RISC-V's randconfig job
will occur since clean_and_invalidate_dcache_va_range() and
clean_dcache_va_range() are currently impleme
On 17.12.2024 17:32, Oleksii Kurochko wrote:
> Make all upper bounds (end addresses) for areas inclusive to align
> with the corresponding definitions.
>
> For the Direct map region, the upper bound was calculated incorrectly
> in efadb18dd58aba ("xen/riscv: add VM space layout"). It should be
> 0
On Thursday, December 19, 2024 09:32 CET, Jan Beulich wrote:
> On 19.12.2024 00:34, Ariel Otilibili wrote:
> > The if-statement tests `res` is non-zero; meaning the case zero is never
> > reached.
> >
> > Coverity-ID: 1055253
> > Fixes: e2b1ebf4de ("x86: Support booting a bzImage format domain
On 12/18/24 1:49 PM, Andrew Cooper wrote:
Credit2 has no buisness including asm/cpufeature.h or asm/processor.h.
This was caused by a bad original abstraction, and an even less wise attempt
to fix the build on my behalf. It is also the sole reason why PPC and RISC-V
need cpufeature.h header.
W
On 17.12.2024 17:32, Oleksii Kurochko wrote:
> Implement following cache operations:
> - clean_and_invalidate_dcache_va_range()
> - clean_dcache_va_range()
> - invalidate_icache()
>
> The first two functions may require support for the CMO (Cache Management
> Operations) extension and/or hardware-
On Wed, Dec 18, 2024 at 06:58:25PM +0100, Roger Pau Monné wrote:
> On Tue, Oct 08, 2024 at 11:32:23PM +0200, Marek Marczykowski-Górecki wrote:
> > Linux 6.12-rc2 fails to decompress with the current 128MiB, contrary to
> > the code comment. It results in a failure like this:
> >
> > domainbuild
It should be CONFIG_ARCH_VCPU_IOREQ_COMPLETION (as in Kconfig) and not
misspelled CONFIG_VCPU_ARCH_IOREQ_COMPLETION.
Bug introduced by:
979cfdd3e5 ioreq: do not build arch_vcpu_ioreq_completion() for non-VMX
configurations
Signed-off-by: Sergiy Kibrik
---
xen/arch/x86/hvm/ioreq.c | 2 +-
xen/i
This is a follow up from a discussion in Xen:
The if-statement tests `res` is non-zero; meaning the case zero is never
reached.
Link: https://lore.kernel.org/all/7587b503-b2ca-4476-8dc9-e9683d4ca...@suse.com/
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Suggested-by: Jan Beulich
Signed-off-by: Arie
Hello,
This patch removes a dead code in lib/inflate.c; it follows from a discussion
in Xen.
The dead code is tracked by Coverity-ID 1055253 in Xen, was triggered by a file
taken unmodified from Linux.
Thank you,
Link: https://lore.kernel.org/all/7587b503-b2ca-4476-8dc9-e9683d4ca...@suse.com/
On Thursday, December 19, 2024 10:10 CET, "Ariel Otilibili-Anieli"
wrote:
> On Thursday, December 19, 2024 09:32 CET, Jan Beulich
> wrote:
>
> > On 19.12.2024 00:34, Ariel Otilibili wrote:
> > > The if-statement tests `res` is non-zero; meaning the case zero is never
> > > reached.
> > >
>
On 19/12/2024 12:23, Andrei Cherechesu (OSS) wrote:
>
>
> From: Andrei Cherechesu
>
> Introduce the SCMI-SMC layer to have some basic degree of
> awareness about SCMI calls that are based on the ARM System
> Control and Management Interface (SCMI) specification (DEN0056E).
>
> The SCMI spec
Hi Arnd,
On Wed, Sep 25, 2024 at 03:58:38PM +, Arnd Bergmann wrote:
> On Wed, Sep 25, 2024, at 15:01, Ard Biesheuvel wrote:
> > From: Ard Biesheuvel
> >
> > Bump the minimum GCC version to 8.1 to gain unconditional support for
> > referring to the per-task stack cookie using a symbol rather t
On Thu, Dec 19, 2024, at 12:53, Mark Rutland wrote:
> On Wed, Sep 25, 2024 at 03:58:38PM +, Arnd Bergmann wrote:
>> On Wed, Sep 25, 2024, at 15:01, Ard Biesheuvel wrote:
>> > From: Ard Biesheuvel
>>
>> We obviously need to go through all the other version checks
>> to see what else can be cle
Hi Michal,
On 19/12/2024 10:35, Michal Orzel wrote:
>
> On 18/12/2024 15:58, Andrei Cherechesu wrote:
>>
>> Hi Michal,
>>
>> Thank you for the review.
>>
>> On 18/12/2024 16:26, Michal Orzel wrote:
>>> On 18/12/2024 11:11, Andrei Cherechesu (OSS) wrote:
From: Andrei Cherechesu
Intr
From: Andrei Cherechesu
Describe the layer which enables SCMI over SMC calls forwarding
to EL3 FW if issued by the Hardware domain. If the SCMI firmware
node is not found in the Host DT during initialization, it fails
silently as it's not mandatory.
The SCMI SMCs trapping at EL2 now lets hwdom p
From: Andrei Cherechesu
Platforms based on NXP S32G3 processors use the NXP LINFlexD
UART driver for console by default, and rely on Dom0 having
access to SCMI services for system-level resources from
firmware at EL3.
Signed-off-by: Andrei Cherechesu
Reviewed-by: Bertrand Marquis
---
xen/arch
From: Andrei Cherechesu
Targeting: Xen 4.20
This v4 version of this patch series finishes the work left to support NXP
S32G3 Processors [0], part of the NXP S32CC Family. The LINFlexD UART support
patches have been merged in v2. Platforms using S32G3 Processors are not
affected by the TLBI by VA
From: Andrei Cherechesu
Add myself as maintainer for NXP S32G3 SoCs Family,
and the S32 Linux Team as relevant reviewers list.
Signed-off-by: Andrei Cherechesu
Acked-by: Bertrand Marquis
Acked-by: Michal Orzel
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAIN
From: Andrei Cherechesu
Introduce the SCMI-SMC layer to have some basic degree of
awareness about SCMI calls that are based on the ARM System
Control and Management Interface (SCMI) specification (DEN0056E).
The SCMI specification includes various protocols for managing
system-level resources, s
From: Andrei Cherechesu
Change the handling of SiP SMC calls to be more generic,
instead of directly relying on the `platform_smc()` callback
implementation.
Try to handle the SiP SMC first through the `platform_smc()`
callback (if implemented). Otherwise, try to handle it as SCMI
message.
Sign
From: Andrei Cherechesu
Signed-off-by: Andrei Cherechesu
Reviewed-by: Bertrand Marquis
Acked-by: Oleksii Kurochko
---
CHANGELOG.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 15f681459f..bda43b1efb 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1
On 19/12/2024 10:46 am, Teddy Astie wrote:
> Hello,
>
> Le 18/12/2024 à 18:08, Andrew Cooper a écrit :
>> From: Teddy Astie
>>
>> In many places of x86 HVM code, constants integer are used to indicate in
>> what mode is
>> running the CPU (real, vm86, 16-bits, 32-bits, 64-bits). However, these
>
From: Petr Beneš
This patch introduces a new XENMEM_access_r_pw permission. Functionally, it is
similar to XENMEM_access_r, but for processors with
TERTIARY_EXEC_EPT_PAGING_WRITE support (Intel 12th Gen/Alder Lake and later),
it also permits the CPU to write to the page during guest page-table
From: Petr Beneš
This patch introduces a new XENMEM_access_r_pw permission. Functionally, it is
similar to XENMEM_access_r, but for processors with
TERTIARY_EXEC_EPT_PAGING_WRITE support (Intel 12th Gen/Alder Lake and later),
it also permits the CPU to write to the page during guest page-table
From: Petr Beneš
The EPT Paging-write feature (when enabled by the
TERTIARY_EXEC_EPT_PAGING_WRITE bit) uses bit 58 of the EPT entry to indicate
that guest paging may update the page, even if the W access is not set.
This patch is a preparation for the EPT Paging-write feature.
---
xen/arch/x8
Same fix than commit 826a9eb072 (tools: Fix regex syntax warnings with Python
3.12).
It clears out the warning:
```
$ xen/scripts/xen-analysis.py
xen/scripts/xen_analysis/cppcheck_analysis.py:94: SyntaxWarning: invalid escape
sequence '\*'
comment_line_starts = re.match('^[ \t]*/\*.*$', line)
Hello,
This patch clears out this warning:
```
$ xen/scripts/xen-analysis.py
xen/scripts/xen_analysis/cppcheck_analysis.py:94: SyntaxWarning: invalid escape
sequence '\*'
comment_line_starts = re.match('^[ \t]*/\*.*$', line)
```
It is the same fix than commit 826a9eb072 (tools: Fix regex synt
CCing Luca Fancellu.
On Thursday, December 19, 2024 19:10 CET, Ariel Otilibili
wrote:
> Same fix than commit 826a9eb072 (tools: Fix regex syntax warnings with Python
> 3.12).
>
> It clears out the warning:
>
> ```
> $ xen/scripts/xen-analysis.py
> xen/scripts/xen_analysis/cppcheck_analysis.p
From: Petr Beneš
This patch introduces a new XENMEM_access_r_pw permission. Functionally, it is
similar to XENMEM_access_r, but for processors with
TERTIARY_EXEC_EPT_PAGING_WRITE support (Intel 12th Gen/Alder Lake and later),
it also permits the CPU to write to the page during guest page-table
From: Petr Beneš
Changes since v1:
- Added signed-off-by tags
This patch introduces a new XENMEM_access_r_pw permission. Functionally, it is
similar to XENMEM_access_r, but for processors with
TERTIARY_EXEC_EPT_PAGING_WRITE support (Intel 12th Gen/Alder Lake and later),
it also permits the CP
From: Petr Beneš
The EPT Paging-write feature (when enabled by the
TERTIARY_EXEC_EPT_PAGING_WRITE bit) uses bit 58 of the EPT entry to indicate
that guest paging may update the page, even if the W access is not set.
This patch is a preparation for the EPT Paging-write feature.
Signed-off-by:
Sending again with an expanded description. RFC to have a discussion
about the approach.
With hyperlaunch, a domU can start before its console ring is connected
by xenconsoled. With nothing emptying the ring, it can quickly fill
during boot. In domU_write_console(), __write_console returns 0 wh
Hello,
This patch removes a dead code in lib/inflate.c; it follows from a discussion
in Xen.
The dead code is tracked by Coverity-ID 1055253 in Xen, was triggered by a file
taken unmodified from Linux.
Thank you,
Link: https://lore.kernel.org/all/7587b503-b2ca-4476-8dc9-e9683d4ca...@suse.com/
-
This is a follow up from a discussion in Xen:
The if-statement tests `res` is non-zero; meaning the case zero is never
reached.
Link: https://lore.kernel.org/all/7587b503-b2ca-4476-8dc9-e9683d4ca...@suse.com/
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Suggested-by: Jan Beulich
Signed-off-by: Arie
On Thu, Dec 19, 2024 at 11:45:01PM +0100, Ariel Otilibili wrote:
> This is a follow up from a discussion in Xen:
>
> The if-statement tests `res` is non-zero; meaning the case zero is never
> reached.
>
> Link:
> https://lore.kernel.org/all/7587b503-b2ca-4476-8dc9-e9683d4ca...@suse.com/
> Fixes
On 19/12/2024 6:16 pm, Petr Beneš wrote:
> From: Petr Beneš
>
> This patch introduces a new XENMEM_access_r_pw permission. Functionally, it
> is similar to XENMEM_access_r, but for processors with
> TERTIARY_EXEC_EPT_PAGING_WRITE support (Intel 12th Gen/Alder Lake and later),
> it also permits
> > diff --git a/xen/arch/x86/mm/p2m-ept.c b/xen/arch/x86/mm/p2m-ept.c
> > index 21728397f9..5ad78ae4b5 100644
> > --- a/xen/arch/x86/mm/p2m-ept.c
> > +++ b/xen/arch/x86/mm/p2m-ept.c
> > @@ -176,6 +176,10 @@ static void ept_p2m_type_to_flags(const struct
> > p2m_domain *p2m,
> > break
On 20/12/2024 12:27 am, Sedat Dilek wrote:
> On Fri, Dec 20, 2024 at 12:26 AM Andrew Cooper
> wrote:
>> On 19/12/2024 11:10 pm, Sedat Dilek wrote:
>>> On Thu, Dec 19, 2024 at 6:07 PM Sedat Dilek wrote:
On Thu, Dec 19, 2024 at 5:44 PM Andrew Cooper
wrote:
> On 19/12/2024 4:14 pm, S
On Thu, Dec 19, 2024 at 05:14:52PM +0100, Marek Marczykowski-Górecki wrote:
> Hi,
>
> It crashes on boot like below, most of the times. But sometimes (rarely)
> it manages to stay alive. Below I'm pasting few of the crashes that look
> distinctly different, if you follow the links, you can find mo
On Friday, December 20, 2024 00:13 CET, Andrew Morton
wrote:
>
> The patch titled
> Subject: lib/inflate.c: remove dead code
> has been added to the -mm mm-nonmm-unstable branch. Its filename is
> lib-remove-dead-code.patch
>
> This patch will shortly appear at
>
> https://git
On Thu, Dec 19, 2024 at 1:17 PM Petr Beneš wrote:
>
> From: Petr Beneš
>
> This patch introduces a new XENMEM_access_r_pw permission. Functionally, it
> is similar to XENMEM_access_r, but for processors with
> TERTIARY_EXEC_EPT_PAGING_WRITE support (Intel 12th Gen/Alder Lake and later),
> it a
On 19/12/2024 12:23, Andrei Cherechesu (OSS) wrote:
>
>
> From: Andrei Cherechesu
>
> Targeting: Xen 4.20
> This v4 version of this patch series finishes the work left to support NXP
> S32G3 Processors [0], part of the NXP S32CC Family. The LINFlexD UART support
> patches have been merged in
On 17/12/2024 18:06, Carlo Nonato wrote:
>
>
> Shared caches in multi-core CPU architectures represent a problem for
> predictability of memory access latency. This jeopardizes applicability
> of many Arm platform in real-time critical and mixed-criticality
> scenarios. We introduce support fo
67 matches
Mail list logo
