On 11.04.2024 01:47, Stefano Stabellini wrote:
> The goal is to use only fixed-size integers in public headers, such as
> uint32_t and uint64_t.
>
> However, there are cases where the ABI changes depending on the
> architecture. In those cases, adding #ifdefs might be the clearest
> solution but i
On Wed, Apr 17, 2024 at 02:40:09PM +0200, Jan Beulich wrote:
> On 11.04.2024 04:41, Elliott Mitchell wrote:
> > On Thu, Mar 28, 2024 at 07:25:02AM +0100, Jan Beulich wrote:
> >> On 27.03.2024 18:27, Elliott Mitchell wrote:
> >>> On Mon, Mar 25, 2024 at 02:43:44PM -0700, Elliott Mitchell wrote:
> >>
On 2024-04-17 23:13, Stefano Stabellini wrote:
+Bugseng
On Wed, 17 Apr 2024, Julien Grall wrote:
Hi Stefano,
On 17/04/2024 20:10, Stefano Stabellini wrote:
> On Wed, 17 Apr 2024, Julien Grall wrote:
> > Hi Stefano,
> >
> > On 16/04/2024 20:27, Stefano Stabellini wrote:
> > > Also add two speci
On 11.04.2024 01:47, Stefano Stabellini wrote:
> Straightforward int -> int32_t and unsigned int -> uint32_t replacements
> in public headers. No ABI or semantic changes intended.
I understand there is a limited in scope goal here, but once doing type
adjustments I think it ought to at least be co
flight 185712 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/185712/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 185674
test-amd64-amd64-xl-qemut-win7-amd64
On 09.04.2024 13:45, Luca Fancellu wrote:
> --- a/xen/arch/x86/extable.c
> +++ b/xen/arch/x86/extable.c
> @@ -23,7 +23,8 @@ static inline unsigned long ex_cont(const struct
> exception_table_entry *x)
> return EX_FIELD(x, cont);
> }
>
> -static int init_or_livepatch cf_check cmp_ex(const
On 16.04.2024 11:15, Fouad Hilly wrote:
> Refactor xen-ucode tool by adding usage() to handle usage\help messages
> As we add more command options this will keep help\usage messages in common
> block
>
> [v2]
> 1- Improved message description.
> 2- Fixed formatting and indentation.
> 3- Error mes
On 10.04.2024 12:24, Edgar E. Iglesias wrote:
> On Wed, Apr 10, 2024 at 12:21 PM Andrew Cooper
> wrote:
>
>> On 10/04/2024 10:19 am, Edgar E. Iglesias wrote:
>>> From: "Edgar E. Iglesias"
>>>
>>> Use the generic xen/linkage.h macros when annotating symbols.
>>>
>>> Signed-off-by: Edgar E. Iglesi
On 09.04.2024 09:39, Oleksii wrote:
> On Mon, 2024-04-08 at 10:23 +0200, Jan Beulich wrote:
>> On 03.04.2024 12:20, Oleksii Kurochko wrote:
>>> +/*
>>> + * Only CONFIG_GENERIC_ATOMIC64=y was ported to Xen that is the
>>> reason why
>>> + * last argument of ATOMIC_FETCH_OP, ATOMIC_OP_RETURN isn't us
flight 185711 xen-4.17-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/185711/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 185284
test-amd64-amd64-xl-qemuu-win7-a
flight 185710 xen-4.16-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/185710/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 185283
test-amd64-amd64-xl-qemut-win7-a
Hi,
On 02/04/2024 22:19, Volodymyr Babchuk wrote:
Hi Michal,
Michal Orzel writes:
Hello,
On 29/03/2024 01:08, Volodymyr Babchuk wrote:
Generic Interface (GENI) is a newer interface for low speed interfaces
like UART, I2C or SPI. This patch adds the simple driver for the UART
instance of
flight 185726 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/185726/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 0afb8743493853e30171f6000de51242e22a1eb8
baseline version:
ovmf 6ced1e91eff13dae1bfba
Hi,
On 29/03/2024 00:08, Volodymyr Babchuk wrote:
Generic Interface (GENI) is a newer interface for low speed interfaces
like UART, I2C or SPI. This patch adds the simple driver for the UART
instance of GENI. Code is based on similar drivers in U-Boot and Linux
kernel.
If this is based on Linu
Hi Volodymyr,
On 29/03/2024 00:08, Volodymyr Babchuk wrote:
Qualcomm SA8155P is the automotive variant of SM8150 aka Snapdragon
855.
This patch adds very basic support for the platform. We need to handle
Qualcomm-specific SMC to workaround quirk in the QCOM SCM driver in
the Linux kernel. Basic
Hi,
On 02/04/2024 08:28, Michal Orzel wrote:
Hello,
On 29/03/2024 01:08, Volodymyr Babchuk wrote:
I encountered platform, namely Qualcomm SA8155P where SMMU-compatible
NIT: a commit msg should be written in imperative mood
IO-MMU advertises more context IQRs than there are context banks.
+Bugseng
On Wed, 17 Apr 2024, Julien Grall wrote:
> Hi Stefano,
>
> On 17/04/2024 20:10, Stefano Stabellini wrote:
> > On Wed, 17 Apr 2024, Julien Grall wrote:
> > > Hi Stefano,
> > >
> > > On 16/04/2024 20:27, Stefano Stabellini wrote:
> > > > Also add two specific project-wide deviations for R
Hi Stefano,
On 17/04/2024 20:10, Stefano Stabellini wrote:
On Wed, 17 Apr 2024, Julien Grall wrote:
Hi Stefano,
On 16/04/2024 20:27, Stefano Stabellini wrote:
Also add two specific project-wide deviations for R21.6 and R21.15.
In general, I am fine with add the two rules. However...
Sign
flight 185725 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/185725/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 6ced1e91eff13dae1bfba95734e2b34a73601db2
baseline version:
ovmf 61185f1d501512f35621d
MISRA C Rule 16.2 states:
"A switch label shall only be used when the most closely-enclosing
compound statement is the body of a switch statement".
Since complying with this rule of the x86 emulator would lead to
a lot of code duplication, it is deemed better to exempt those
files for this guideli
A respin of the last two patches from the previous series.
No changes other than the different SAF comment id because SAF-4-safe was
already taken.
Nicola Vetrini (2):
xen/domctl: address violations of MISRA C Rule 16.2
eclair_analysis: deviate x86 emulator for Rule 16.2
automation/eclair_an
Refactor the first clauses so that a violation of
MISRA C Rule 16.2 is resolved (a switch label should be immediately
enclosed in the compound statement of the switch).
Note that the switch clause ending with the pseudo
keyword "fallthrough" is an allowed exception to Rule 16.3.
Convert fallthroug
flight 185709 xen-4.15-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/185709/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 185282
test-amd64-amd64-xl-qemuu-win7-a
On Wed, 17 Apr 2024, Julien Grall wrote:
> Hi Stefano,
>
> On 16/04/2024 20:27, Stefano Stabellini wrote:
> > Also add two specific project-wide deviations for R21.6 and R21.15.
>
> In general, I am fine with add the two rules. However...
>
> >
> > Signed-off-by: Stefano Stabellini
> >
> > di
On Wed, 17 Apr 2024, Julien Grall wrote:
> Hi Michal,
>
> On 17/04/2024 13:14, Michal Orzel wrote:
> > Commit afab29d0882f ("public: s/int/int32_t") replaced int with int32_t
> > in XEN_GUEST_HANDLE() in memory.h but there is no guest handle defined
> > for it. This results in a build failure. Exa
On 17/04/2024 3:37 pm, Daniel P. Smith wrote:
> diff --git a/xen/common/gzip/gunzip.c b/xen/common/gzip/gunzip.c
> index 1b448d6e3655..8178a05a0190 100644
> --- a/xen/common/gzip/gunzip.c
> +++ b/xen/common/gzip/gunzip.c
> @@ -4,18 +4,25 @@
> #include
> #include
>
> -static unsigned char *__i
Hi Shawn,
On 12/04/2024 03:53, Shawn Anastasio wrote:
Hi Julien,
On 3/21/24 12:50 PM, Julien Grall wrote:
Hi Shawn,
On 14/03/2024 22:15, Shawn Anastasio wrote:
Move Arm's bootfdt.c to xen/common so that it can be used by other
device tree architectures like PPC and RISCV.
Suggested-by: Juli
On 17/04/2024 3:37 pm, Daniel P. Smith wrote:
> Signed-off-by: Daniel P. Smith
The change in type is fine, but does need discussing. Furthermore, ...
> diff --git a/xen/common/gzip/gunzip.c b/xen/common/gzip/gunzip.c
> index 8178a05a0190..bef324d3d166 100644
> --- a/xen/common/gzip/gunzip.c
> +
On 17/04/2024 3:37 pm, Daniel P. Smith wrote:
> All the other decompression routines use xmalloc_bytes(), thus there is no
> reason for gzip to be handling its own allocation of memory. In fact, there is
> a bug somewhere in the allocator as decompression started to break when adding
> additional a
On 17/04/2024 3:37 pm, Daniel P. Smith wrote:
> The "tracking" bits does not appear to be used, so dropping from the code.
>
> Signed-off-by: Daniel P. Smith
> ---
> xen/common/gzip/inflate.c | 6 --
> 1 file changed, 6 deletions(-)
>
> diff --git a/xen/common/gzip/inflate.c b/xen/common/gzip
On 17/04/2024 3:37 pm, Daniel P. Smith wrote:
> Dropping the define checks for PKZIP_BUG_WORKAROUND and NOMEMCPY define as
> they
> never are set.
>
> Signed-off-by: Daniel P. Smith
It looks like ARCH_HAS_DECOMP_WDOG is another one that can go.
There's only a single instance, in inflate(), whic
On 17.04.2024 17:05, Ross Lagerwall wrote:
> On Wed, Apr 17, 2024 at 3:15 PM Jan Beulich wrote:
>>
>> On 10.04.2024 11:41, Ross Lagerwall wrote:
>>> On Mon, Apr 8, 2024 at 11:25 AM Jan Beulich wrote:
On 28.03.2024 16:11, Ross Lagerwall wrote:
> * The image base address is set to 0 since
On Sun, Apr 07, 2024 at 10:36:33AM -0400, Jason Andryuk wrote:
> diff --git a/tools/libs/light/libxl_disk.c b/tools/libs/light/libxl_disk.c
> index fa7856f28c..819d34933b 100644
> --- a/tools/libs/light/libxl_disk.c
> +++ b/tools/libs/light/libxl_disk.c
> @@ -829,21 +829,122 @@ int libxl_device_dis
On 17/04/2024 16:05, Nicola Vetrini wrote:
On 2024-04-17 16:57, Julien Grall wrote:
Hi Nicola,
On 17/04/2024 15:51, Nicola Vetrini wrote:
The service STD.emptrecd is in the process of being removed in favour
of STD.anonstct.
I am guessing this is not a new feature and the current ECLAIR v
flight 185705 xen-4.18-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/185705/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvops 6 kernel-build fail in 185695 REGR. vs. 185285
Tests which ar
On Wed, Apr 17, 2024 at 3:15 PM Jan Beulich wrote:
>
> On 10.04.2024 11:41, Ross Lagerwall wrote:
> > On Mon, Apr 8, 2024 at 11:25 AM Jan Beulich wrote:
> >> On 28.03.2024 16:11, Ross Lagerwall wrote:
> >>> * The image base address is set to 0 since it must necessarily be below
> >>> 4 GiB and
On 2024-04-17 16:57, Julien Grall wrote:
Hi Nicola,
On 17/04/2024 15:51, Nicola Vetrini wrote:
The service STD.emptrecd is in the process of being removed in favour
of STD.anonstct.
I am guessing this is not a new feature and the current ECLAIR version
is supporting it?
Cheers,
Yes, it
Hi Stefano,
On 16/04/2024 20:27, Stefano Stabellini wrote:
Also add two specific project-wide deviations for R21.6 and R21.15.
In general, I am fine with add the two rules. However...
Signed-off-by: Stefano Stabellini
diff --git a/docs/misra/deviations.rst b/docs/misra/deviations.rst
inde
On 09.04.2024 23:49, Stefano Stabellini wrote:
> On Tue, 9 Apr 2024, Sergiy Kibrik wrote:
>> 05.04.24 13:57, Andrew Cooper:
>>> On 05/04/2024 11:30 am, Sergiy Kibrik wrote:
Introduce configuration variables to make it possible to selectively turn
on/off CPU microcode management code in th
Hi Nicola,
On 17/04/2024 15:51, Nicola Vetrini wrote:
The service STD.emptrecd is in the process of being removed in favour
of STD.anonstct.
I am guessing this is not a new feature and the current ECLAIR version
is supporting it?
Cheers,
No functional change.
Signed-off-by: Nicola Vetri
The service STD.emptrecd is in the process of being removed in favour
of STD.anonstct.
No functional change.
Signed-off-by: Nicola Vetrini
---
automation/eclair_analysis/ECLAIR/toolchain.ecl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/automation/eclair_analysis/ECLAI
On 16.04.2024 08:18, Sergiy Kibrik wrote:
> This series aims to continue what Xenia started a year ago:
>
> https://lore.kernel.org/xen-devel/20230213145751.1047236-1-burzalod...@gmail.com/
>
> Here's an attempt to provide a means to render the cpu virtualization
> technology support in Xen confi
Signed-off-by: Daniel P. Smith
---
xen/common/gzip/gunzip.c | 11 +++
xen/common/gzip/inflate.c | 12 +---
2 files changed, 12 insertions(+), 11 deletions(-)
diff --git a/xen/common/gzip/gunzip.c b/xen/common/gzip/gunzip.c
index 8178a05a0190..bef324d3d166 100644
--- a/xen/common
The "tracking" bits does not appear to be used, so dropping from the code.
Signed-off-by: Daniel P. Smith
---
xen/common/gzip/inflate.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/xen/common/gzip/inflate.c b/xen/common/gzip/inflate.c
index c18ce20210b0..15bc187c2bbe 100644
--- a/xen
Move the core state into struct gzip_data to allow a per decompression
instance.
Signed-off-by: Daniel P. Smith
---
xen/common/gzip/gunzip.c | 55 +++-
xen/common/gzip/inflate.c | 174 +++---
2 files changed, 120 insertions(+), 109 deletions(-)
diff --g
All the other decompression routines use xmalloc_bytes(), thus there is no
reason for gzip to be handling its own allocation of memory. In fact, there is
a bug somewhere in the allocator as decompression started to break when adding
additional allocations. Instead of troubleshooting the allocator,
This commit cleans up the comments and fixes the code alignment using Xen
coding style. This is done to make the code more legible before refactoring.
Signed-off-by: Daniel P. Smith
---
xen/common/gzip/gunzip.c | 10 +-
xen/common/gzip/inflate.c | 790 +++---
2
Dropping the define checks for PKZIP_BUG_WORKAROUND and NOMEMCPY define as they
never are set.
Signed-off-by: Daniel P. Smith
---
xen/common/gzip/inflate.c | 15 ---
1 file changed, 15 deletions(-)
diff --git a/xen/common/gzip/inflate.c b/xen/common/gzip/inflate.c
index 58f263d9e852
An issue ran into by hyperlaunch was the need to use the gzip decompressor
multiple times. The current implementation fails when reused due to tainting of
decompressor state from a previous usage. This series seeks to colocate the
gzip unit files under a single directory similar to the other decomp
On Wed, Apr 17, 2024 at 04:17:48PM +0200, Jan Beulich wrote:
> On 14.04.2024 02:32, Marek Marczykowski-Górecki wrote:
> > On Wed, Apr 03, 2024 at 09:10:40AM +0200, Jan Beulich wrote:
> >> On 27.03.2024 03:53, Marek Marczykowski-Górecki wrote:
> >>> The IOMMU driver checks if RMRR/IVMD are marked as
On 14.04.2024 02:32, Marek Marczykowski-Górecki wrote:
> On Wed, Apr 03, 2024 at 09:10:40AM +0200, Jan Beulich wrote:
>> On 27.03.2024 03:53, Marek Marczykowski-Górecki wrote:
>>> The IOMMU driver checks if RMRR/IVMD are marked as reserved in memory
>>> map. This should be true for addresses coming
Hi Michal,
On 17/04/2024 13:14, Michal Orzel wrote:
Commit afab29d0882f ("public: s/int/int32_t") replaced int with int32_t
in XEN_GUEST_HANDLE() in memory.h but there is no guest handle defined
for it. This results in a build failure. Example on Arm:
./include/public/arch-arm.h:205:41: error:
On 10.04.2024 11:41, Ross Lagerwall wrote:
> On Mon, Apr 8, 2024 at 11:25 AM Jan Beulich wrote:
>> On 28.03.2024 16:11, Ross Lagerwall wrote:
>>> * The image base address is set to 0 since it must necessarily be below
>>> 4 GiB and the loader will relocate it anyway.
>>
>> While technically okay
Currently, the CPUID leaf for SVM features (extd 0xa.edx) is manually
twiddled:
- hvm_max_policy takes host_policy and clamps it to supported
features (with some features unilaterally enabled because they're
always emulated
- hvm_default_policy is copied from there
- When recalculate_po
On 11.04.2024 14:03, Andrew Cooper wrote:
> On 09/04/2024 8:45 pm, Nicola Vetrini wrote:
>> On 2024-04-08 09:32, Jan Beulich wrote:
>>> On 05.04.2024 11:14, Nicola Vetrini wrote:
Remove unneded blank lines between switch clauses.
>>>
>>> "Unneeded" based on what? We're carefully trying to impr
On 08.04.2024 18:56, Jason Andryuk wrote:
> On 2024-04-08 03:00, Jan Beulich wrote:
>> On 04.04.2024 23:25, Jason Andryuk wrote:
>>> --- a/xen/arch/x86/hvm/dom0_build.c
>>> +++ b/xen/arch/x86/hvm/dom0_build.c
>>> @@ -537,6 +537,111 @@ static paddr_t __init find_memory(
>>> return INVALID_PADD
On 11.04.2024 16:39, Oleksii wrote:
> On Wed, 2024-04-03 at 13:53 +0200, Jan Beulich wrote:
>> On 03.04.2024 12:54, Oleksii wrote:
>>> On Wed, 2024-04-03 at 12:28 +0200, Jan Beulich wrote:
On 03.04.2024 12:19, Oleksii Kurochko wrote:
> This patch disables unnecessary configs for two cases:
On 12.04.2024 05:19, Shawn Anastasio wrote:
> On 3/25/24 10:39 AM, Jan Beulich wrote:
>> On 14.03.2024 23:15, Shawn Anastasio wrote:
>>> -static __init struct lvl2_pd *lvl2_pd_pool_alloc(void)
>>> -{
>>> -if ( initial_lvl2_lvl3_pd_pool_used >= INITIAL_LVL2_LVL3_PD_COUNT )
>>> -{
>>> -
On 10.04.2024 01:35, Shawn Anastasio wrote:
> On 3/25/24 10:24 AM, Jan Beulich wrote:
>> On 14.03.2024 23:15, Shawn Anastasio wrote:
>>> Required for bootfdt.c to build.
>>>
>>> Signed-off-by: Shawn Anastasio
>>
>> As a temporary workaround this may be okay, but was the alternative
>> considered t
flight 185718 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/185718/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm 6 xen-buildfail REGR. vs. 185684
build-amd64
Hi Michal,
> On 17 Apr 2024, at 13:14, Michal Orzel wrote:
>
> Commit afab29d0882f ("public: s/int/int32_t") replaced int with int32_t
> in XEN_GUEST_HANDLE() in memory.h but there is no guest handle defined
> for it. This results in a build failure. Example on Arm:
>
> ./include/public/arch-ar
On 11.04.2024 04:41, Elliott Mitchell wrote:
> On Thu, Mar 28, 2024 at 07:25:02AM +0100, Jan Beulich wrote:
>> On 27.03.2024 18:27, Elliott Mitchell wrote:
>>> On Mon, Mar 25, 2024 at 02:43:44PM -0700, Elliott Mitchell wrote:
On Mon, Mar 25, 2024 at 08:55:56AM +0100, Jan Beulich wrote:
>
>
On 17/04/2024 14:07, Oleksandr Tyshchenko wrote:
>
>
> From: Oleksandr Tyshchenko
>
> This is needed to have a possibility of assigning a specified number
> of shared peripheral interrupts (SPIs) to domain.
>
> Signed-off-by: Oleksandr Tyshchenko
> Signed-off-by: Stefano Stabellini
Review
On 17/04/2024 14:07, Oleksandr Tyshchenko wrote:
>
>
> From: Oleksandr Tyshchenko
>
> Introduce new option DOMU_VPL011[nr] that can be set to 0
> or 1 (default).
>
> Also align "console=ttyAMA0" Linux cmd arg setting with "vpl011" presense.
>
> Suggested-by: Michal Orzel
> Signed-off-by:
On 17/04/2024 14:07, Oleksandr Tyshchenko wrote:
>
>
> From: Oleksandr Tyshchenko
>
> Use DOMU_GRANT_VER to set "max_grant_version" dt property.
> Use DOMU_GRANT_FRAMES to set "max_grant_frames" dt property.
> Use DOMU_MAPTRACK_FRAMES to set "max_maptrack_frames" dt property.
>
> Signed-off
On 17/04/2024 14:07, Oleksandr Tyshchenko wrote:
>
>
> From: Oleksandr Tyshchenko
>
> We need some Xen services to be available within single dom0less DomU.
> Just using "enabled" will lead to Xen panic because of no Dom0.
>
> (XEN)
> (XEN) Panic on
On 17/04/2024 14:07, Oleksandr Tyshchenko wrote:
>
>
> From: Oleksandr Tyshchenko
>
> uImage is the Image that has a U-Boot wrapper, it doesn't contain
> "executable" string which subsequent "file" command is looking for
> when inspecting it.
>
> Below the proof:
>
> otyshchenko@EPUAKYIW03
Commit afab29d0882f ("public: s/int/int32_t") replaced int with int32_t
in XEN_GUEST_HANDLE() in memory.h but there is no guest handle defined
for it. This results in a build failure. Example on Arm:
./include/public/arch-arm.h:205:41: error: unknown type name
‘__guest_handle_64_int32_t’
205 |
Hi John,
Thanks for the patch!
On 17/04/2024 01:47, Stefano Stabellini wrote:
On Tue, 16 Apr 2024, Peng Fan wrote:
Subject: [PATCH] xen/arm: imx8qm: Re-license file to GPL-2.0-only
New contributions are recommended to be under GPL-2.0-only [1], since this
code piece originally came from the N
From: Oleksandr Tyshchenko
This is needed to have a possibility of assigning a specified number
of shared peripheral interrupts (SPIs) to domain.
Signed-off-by: Oleksandr Tyshchenko
Signed-off-by: Stefano Stabellini
---
README.md| 5 +
scripts/uboot-script-gen | 4
2
From: Oleksandr Tyshchenko
uImage is the Image that has a U-Boot wrapper, it doesn't contain
"executable" string which subsequent "file" command is looking for
when inspecting it.
Below the proof:
otyshchenko@EPUAKYIW03DD:~/work/xen_tests/input$ file -L binaries/uImage.gz
binaries/uImage.gz: u-
From: Oleksandr Tyshchenko
Use DOMU_GRANT_VER to set "max_grant_version" dt property.
Use DOMU_GRANT_FRAMES to set "max_grant_frames" dt property.
Use DOMU_MAPTRACK_FRAMES to set "max_maptrack_frames" dt property.
Signed-off-by: Oleksandr Tyshchenko
---
README.md| 10 ++
From: Oleksandr Tyshchenko
Introduce new option DOMU_VPL011[nr] that can be set to 0
or 1 (default).
Also align "console=ttyAMA0" Linux cmd arg setting with "vpl011" presense.
Suggested-by: Michal Orzel
Signed-off-by: Oleksandr Tyshchenko
---
README.md| 7 ++-
scripts/ubo
From: Oleksandr Tyshchenko
Hello all,
this is a collection of patches (#2-5) for improving the dom0less support
and a patch (#1) for dealing with uImage.
Oleksandr Tyshchenko (5):
uboot-script-gen: Update to deal with uImage which is not executable
uboot-script-gen: Extend DOMU_ENHANCED t
From: Oleksandr Tyshchenko
We need some Xen services to be available within single dom0less DomU.
Just using "enabled" will lead to Xen panic because of no Dom0.
(XEN)
(XEN) Panic on CPU 0:
(XEN) At the moment, Xenstore support requires dom0 to be present
flight 185715 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/185715/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm 6 xen-buildfail REGR. vs. 185684
build-amd64
This patch doesn't represent a strict lower bound for GCC and
GNU Binutils; rather, these versions are specifically employed by
the Xen RISC-V container and are anticipated to undergo continuous
testing. Older GCC and GNU Binutils would work,
but this is not a guarantee.
While it is feasible to ut
Return type was left 'int' because of the following compilation error:
./include/xen/kernel.h:18:21: error: comparison of distinct pointer types lacks
a cast [-Werror]
18 | (void) (&_x == &_y);\
| ^~
common/page_alloc.c:1843:34: note: i
Signed-off-by: Oleksii Kurochko
Reviewed-by: Jan Beulich
---
Changes in V5-V8:
- Nothing changed. Only rebase.
---
Changes in V4:
- drop stubs for irq_actor_none() and irq_actor_none() as common/irq.c is
compiled now.
- drop defintion of max_page in stubs.c as common/page_alloc.c is compiled
Signed-off-by: Oleksii Kurochko
Acked-by: Jan Beulich
---
Changes in V5-V8:
- Nothing changed. Only rebase.
---
Changes in V4:
---
- Change message -> subject in "Changes in V3"
- s/BUG/BUG_ON("...")
- Do proper rebase ( pfn_to_paddr() and paddr_to_pfn() aren't removed ).
---
Changes in V3:
The header was taken from Linux kernl 6.4.0-rc1.
Addionally, were updated:
* add emulation of {cmp}xchg for 1/2 byte types using 32-bit atomic
access.
* replace tabs with spaces
* replace __* variale with *__
* introduce generic version of xchg_* and cmpxchg_*.
* drop {cmp}xchg{release,relaxed,a
Signed-off-by: Oleksii Kurochko
---
Changes in V5-V8:
- Only rebase was done.
---
Changes in V4:
- New patch.
---
xen/arch/riscv/Makefile | 1 +
xen/arch/riscv/vm_event.c | 19 +++
2 files changed, 20 insertions(+)
create mode 100644 xen/arch/riscv/vm_event.c
diff --git a/
Signed-off-by: Oleksii Kurochko
---
Changes in V4-V8:
- Nothing changed. Only rebase.
---
Changes in V3:
- new patch.
---
xen/arch/riscv/include/asm/monitor.h | 26 ++
1 file changed, 26 insertions(+)
create mode 100644 xen/arch/riscv/include/asm/monitor.h
diff --git a
This patch series performs all of the additions necessary to drop the
build overrides for RISCV and enable the full Xen build. Except in cases
where compatibile implementations already exist (e.g. atomic.h and
bitops.h), the newly added definitions are simple.
The patch series is based on the foll
The definition of __read_mostly should be removed in:
https://lore.kernel.org/xen-devel/f25eb5c9-7c14-6e23-8535-2c66772b3...@suse.com/
The patch introduces it in arch-specific header to not
block enabling of full Xen build for RISC-V.
Signed-off-by: Oleksii Kurochko
---
- [PATCH] move __read_mos
Signed-off-by: Oleksii Kurochko
Acked-by: Jan Beulich
---
Changes in V7:
- Only rebase was done.
---
Changes in V6:
- update the commit in stubs.c around /* ... common/irq.c ... */
- add Acked-by: Jan Beulich
---
Changes in V5:
- drop unrelated changes
- assert_failed("unimplmented...") cha
Signed-off-by: Oleksii Kurochko
Acked-by: Jan Beulich
---
Changes in V8:
- Nothing changed only rebase.
---
Changes in V7:
- update argument type of maddr_to_virt() function: unsigned long -> paddr_t
- rename argument of PFN_ORDER(): pfn -> pg.
- add Acked-by: Jan Beulich
---
Changes in V6:
The mentioned macros exist only because of Linux compatible purpose.
The patch defines __ffs() in terms of Xen bitops and it is safe
to define in this way ( as __ffs() - 1 ) as considering that __ffs()
was defined as __builtin_ctzl(x), which has undefined behavior when x=0,
so it is assumed that s
The header taken form Linux 6.4.0-rc1 and is based on
arch/riscv/include/asm/mmio.h with the following changes:
- drop forcing of endianess for read*(), write*() functions as
no matter what CPU endianness, what endianness a particular device
(and hence its MMIO region(s)) is using is entirely i
Add minimal requied things to be able to build full Xen.
Signed-off-by: Oleksii Kurochko
Acked-by: Jan Beulich
---
Changes in V5-V8:
- Nothing changed. Only rebase.
---
Changes in V4:
- BUG() was changed to BUG_ON("unimplemented");
- Change "xen/bug.h" to "xen/lib.h" as BUG_ON is defined in x
Initially the patch was introduced by Bobby, who takes the header from
Linux kernel.
The following changes were done on top of Bobby's changes:
- atomic##prefix##_*xchg_*(atomic##prefix##_t *v, c_t n) were updated
to use__*xchg_generic()
- drop casts in write_atomic() as they are unnecessary
Taken from Linux-6.4.0-rc1
Xen's bitops.h consists of several Linux's headers:
* linux/arch/include/asm/bitops.h:
* The following function were removed as they aren't used in Xen:
* test_and_set_bit_lock
* clear_bit_unlock
* __clear_bit_unlock
* The following functions
The following generic functions were introduced:
* test_bit
* generic__test_and_set_bit
* generic__test_and_clear_bit
* generic__test_and_change_bit
Also, the patch introduces the following generics which are
used by the functions mentioned above:
* BITOP_BITS_PER_WORD
* BITOP_MASK
* BITOP_WORD
*
Disables unnecessary configs for two cases:
1. By utilizing EXTRA_FIXED_RANDCONFIG for randconfig builds (GitLab CI jobs).
2. By using tiny64_defconfig for non-randconfig builds.
Only configs which lead to compilation issues were disabled.
Remove lines related to disablement of configs which aren
Hi,
On 12/04/2024 07:41, Luca Fancellu wrote:
On 12 Apr 2024, at 07:16, Michal Orzel wrote:
Since commit 6cd046c501bc ("xen/arm: Enlarge identity map space to 10TB")
Xen can be loaded below 10 TiB. Update docs accordingly.
Take the opportunity to update stale links to Linux docs.
Signed-o
Hi Stefano,
> Other deviations:
> -
>
> diff --git a/docs/misra/rules.rst b/docs/misra/rules.rst
> index b7b447e152..00db02ad34 100644
> --- a/docs/misra/rules.rst
> +++ b/docs/misra/rules.rst
> @@ -652,12 +652,38 @@ maintainers if you want to suggest a change.
>declared
>
On Tue, Apr 16, 2024 at 04:52:51PM +0100, Andrew Cooper wrote:
> Misra Rule 21.16 doesn't like the use of memcmp() between a string literal and
> a UINT8 array. Rewrite using plain compares.
The commit message makes it look like it's a type mismatch issue
between the two elements being compared,
97 matches
Mail list logo
