flight 182626 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/182626/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-vhd 8 xen-boot fail REGR. vs. 182531
test-amd64-amd64-xl
Hi Jan,
> On Sep 1, 2023, at 15:26, Jan Beulich wrote:
>
> This using a GNU extension, it may not be exposed in general, just like
> is done on x86. External consumers need to make this type available up
> front (just like we expect {,u}int_t to be supplied) - unlike on x86
> the type is actuall
Hi Jan and Michal,
> On Sep 4, 2023, at 23:13, Jan Beulich wrote:
>
> On 04.09.2023 16:03, Michal Orzel wrote:
>> On 04/09/2023 15:28, Jan Beulich wrote:
>>> On 04.09.2023 11:14, Michal Orzel wrote:
--- a/xen/include/xen/bitops.h
+++ b/xen/include/xen/bitops.h
@@ -51,7 +51,7 @@ st
flight 182625 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/182625/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-vhd 8 xen-boot fail REGR. vs. 182531
test-amd64-amd64-xl
The functions referenced by this patch should have had a compatible
declaration visible prior to their definition. This is achieved by
including the arch-specific header in 'xen/arch/arm/ioreq.c'
Fixes: cb9953d2f2bc ("arm/ioreq: Introduce arch specific bits for IOREQ/DM
features")
Signed-off-by:
Hi Jan,
> On 4 Sep 2023, at 17:20, Jan Beulich wrote:
>
> On 04.09.2023 16:05, Bertrand Marquis wrote:
>>> On 4 Sep 2023, at 16:01, Jan Beulich wrote:
>>>
>>> On 04.09.2023 15:42, Bertrand Marquis wrote:
> On 1 Sep 2023, at 09:26, Jan Beulich wrote:
>
> This using a GNU extension
On 04.09.2023 16:05, Bertrand Marquis wrote:
>> On 4 Sep 2023, at 16:01, Jan Beulich wrote:
>>
>> On 04.09.2023 15:42, Bertrand Marquis wrote:
On 1 Sep 2023, at 09:26, Jan Beulich wrote:
This using a GNU extension, it may not be exposed in general, just like
>>>
>>> Nit: Missing "i
Hi Jens,
> On 4 Sep 2023, at 16:58, Jens Wiklander wrote:
>
> FFA_RXTX_MAP is currently limited to mapping only one 4k page for each
> RX and TX buffer. If a guest tries to map more than one page, an error
> is returned. Until this patch, we have been using FFA_RET_NOT_SUPPORTED.
> However, that
On 04.09.2023 16:03, Michal Orzel wrote:
> On 04/09/2023 15:28, Jan Beulich wrote:
>> On 04.09.2023 11:14, Michal Orzel wrote:
>>> --- a/xen/include/xen/bitops.h
>>> +++ b/xen/include/xen/bitops.h
>>> @@ -51,7 +51,7 @@ static inline int generic_ffs(int x)
>>> * fls: find last bit set.
>>> */
>>
FFA_RXTX_MAP is currently limited to mapping only one 4k page for each
RX and TX buffer. If a guest tries to map more than one page, an error
is returned. Until this patch, we have been using FFA_RET_NOT_SUPPORTED.
However, that error code is reserved in the FF-A specification to report
that the fu
Hi Bertrand,
On Mon, Sep 04, 2023 at 01:55:12PM +, Bertrand Marquis wrote:
> Hi Leo,
>
> > On 31 Aug 2023, at 13:01, Leo Yan wrote:
> >
> > On some platforms, the memory regions could be:
> >
> > (XEN) MODULE[0]: 0807f6df - 0807f6f3e000 Xen
> > (XEN) MODULE[1]: 0807f80540
Hi Jan,
> On 4 Sep 2023, at 16:01, Jan Beulich wrote:
>
> On 04.09.2023 15:42, Bertrand Marquis wrote:
>>> On 1 Sep 2023, at 09:26, Jan Beulich wrote:
>>>
>>> This using a GNU extension, it may not be exposed in general, just like
>>
>> Nit: Missing "is"
>
> I would guess you would want it a
On 04/09/2023 15:28, Jan Beulich wrote:
>
>
> On 04.09.2023 11:14, Michal Orzel wrote:
>> --- a/xen/include/xen/bitops.h
>> +++ b/xen/include/xen/bitops.h
>> @@ -51,7 +51,7 @@ static inline int generic_ffs(int x)
>> * fls: find last bit set.
>> */
>>
>> -static __inline__ int generic_fls(i
On 04.09.2023 15:42, Bertrand Marquis wrote:
>> On 1 Sep 2023, at 09:26, Jan Beulich wrote:
>>
>> This using a GNU extension, it may not be exposed in general, just like
>
> Nit: Missing "is"
I would guess you would want it added as the 2nd word of the sentence. If
not, please clarify where you
Hi Leo,
> On 31 Aug 2023, at 13:01, Leo Yan wrote:
>
> Xen maps the virtual memory space starting from L0 slot 4, so it's open
> coded for macros with the offset '4'.
>
> For more readable, add a new macro XEN_VM_MAPPING which defines the
> start slot for Xen virtual memory mapping, and all vir
On 31.08.2023 12:42, Roger Pau Monné wrote:
> On Fri, Oct 12, 2018 at 09:58:46AM -0600, Jan Beulich wrote:
>> First of all, hvm_intsrc_mce was not considered here at all, yet nothing
>> blocks #MC (other than an already in-progress #MC, but dealing with this
>> is not the purpose of this patch).
>>
Hi Leo,
> On 31 Aug 2023, at 13:01, Leo Yan wrote:
>
> On some platforms, the memory regions could be:
>
> (XEN) MODULE[0]: 0807f6df - 0807f6f3e000 Xen
> (XEN) MODULE[1]: 0807f8054000 - 0807f8056000 Device Tree
> (XEN) MODULE[2]: fa834000 - fc5de1d5 Ramdis
Hi Jan,
> On 1 Sep 2023, at 09:26, Jan Beulich wrote:
>
> This using a GNU extension, it may not be exposed in general, just like
Nit: Missing "is"
> is done on x86. External consumers need to make this type available up
> front (just like we expect {,u}int_t to be supplied) - unlike on x86
>
On 31.08.2023 12:57, Roger Pau Monné wrote:
> On Thu, Aug 31, 2023 at 12:42:58PM +0200, Roger Pau Monné wrote:
>> On Fri, Oct 12, 2018 at 09:58:46AM -0600, Jan Beulich wrote:
>>> First of all, hvm_intsrc_mce was not considered here at all, yet nothing
>>> blocks #MC (other than an already in-progre
Hi Oleksii,
> On 1 Sep 2023, at 18:02, Oleksii Kurochko wrote:
>
> Some headers are shared between individual architectures or are empty.
> To avoid duplication of these headers, asm-generic is introduced.
>
> With the following patch, an architecture uses generic headers
> mentioned in the fil
On 04.09.2023 11:14, Michal Orzel wrote:
> --- a/xen/include/xen/bitops.h
> +++ b/xen/include/xen/bitops.h
> @@ -51,7 +51,7 @@ static inline int generic_ffs(int x)
> * fls: find last bit set.
> */
>
> -static __inline__ int generic_fls(int x)
> +static __inline__ int generic_fls(unsigned int
Hey everyone,
Hope you've all had a good weekend!
I know that documentation is an important part of The Xen Project, and I
have received feedback from a number of users on this topic. Currently,
there are some barriers to entry and improvements that can be made.
In order to understand further, p
> On 28 Aug 2023, at 23:27, Stefano Stabellini wrote:
>
> +Nicola, Luca
>
> On Mon, 28 Aug 2023, Simone Ballarin wrote:
>> xen/arch/x86/usercopy.c includes itself, so it is not supposed to
>> comply with Directive 4.10:
>> "Precautions shall be taken in order to prevent the contents of a
>> he
> On 25 Aug 2023, at 22:56, Stefano Stabellini wrote:
>
> On Fri, 25 Aug 2023, Nicola Vetrini wrote:
>> On 25/08/2023 00:24, Stefano Stabellini wrote:
>>> Hi Luca,
>>>
>>> We are looking into adding ECLAIR support for xen-analysis so that we
>>> can use the SAF-n-safe tags also with ECLAIR.
>>
> On 25 Aug 2023, at 09:28, Jan Beulich wrote:
>
> On 25.08.2023 10:18, Michal Orzel wrote:
>> Hi Stefano,
>>
>> On 25/08/2023 00:24, Stefano Stabellini wrote:
>>>
>>>
>>> Hi Luca,
>>>
>>> We are looking into adding ECLAIR support for xen-analysis so that we
>>> can use the SAF-n-safe tags
> On 25 Aug 2023, at 09:18, Michal Orzel wrote:
>
> Hi Stefano,
>
> On 25/08/2023 00:24, Stefano Stabellini wrote:
>>
>>
>> Hi Luca,
>>
>> We are looking into adding ECLAIR support for xen-analysis so that we
>> can use the SAF-n-safe tags also with ECLAIR.
>>
>> One question that came up
flight 182624 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/182624/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-vhd 8 xen-boot fail REGR. vs. 182531
test-amd64-amd64-xl
Hi Michal,
> On 4 Sep 2023, at 11:14, Michal Orzel wrote:
>
> When running with SMMUv3 and UBSAN enabled, the following is printed:
>
> (XEN) UBSAN: Undefined behaviour in drivers/passthrough/arm/smmu-v3.c:297:12
> (XEN) left shift of 1 by 31 places cannot be represented in type 'int'
>
> This
On 01/09/2023 06:59, Vikram Garhwal wrote:
> Add rangesets for IRQs and IOMEMs. This was done to accommodate dynamic
> overlay
> node addition/removal operations. With overlay operations, new IRQs and IOMEMs
> are added in dt_host and routed. While removing overlay nodes, nodes are
> removed
>
On Mon, 2023-09-04 at 08:54 +0200, Jan Beulich wrote:
> On 01.09.2023 18:02, Oleksii Kurochko wrote:
> > asm/vm_event.h is common for ARM and RISC-V so it will be moved to
> > asm-generic dir.
> >
> > Original asm/vm_event.h from ARM was updated:
> > * use SPDX-License-Identifier.
> > * update c
On Mon, 2023-09-04 at 08:53 +0200, Jan Beulich wrote:
> On 01.09.2023 19:14, Oleksii Kurochko wrote:
> > The change which adds generic-y += vm_event.h to ARM's Kbuild was
> > lost
> > during creation of the patch. Should be added in the next patch
> > version
>
> Which I guess is an indication tha
flight 182623 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/182623/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-rtds 8 xen-boot fail in 182620 pass in 182623
test-armhf-armhf-libvirt-qcow2 1
On 01/09/2023 06:59, Vikram Garhwal wrote:
> Dynamic programming ops will modify the dt_host and there might be other
> functions which are browsing the dt_host at the same time. To avoid the race
> conditions, adding rwlock for browsing the dt_host during runtime. dt_host
> writer will be added
On 01/09/2023 06:59, Vikram Garhwal wrote:
> Add remove_device callback for removing the device entry from smmu-master
> using
> following steps:
> 1. Find if SMMU master exists for the device node.
> 2. Check if device is currently in use.
Just like in v10: you are not checking it. I asked you
On 01/09/2023 06:59, Vikram Garhwal wrote:
> Remove master device from the IOMMU. This will be helpful when removing the
> overlay nodes using dynamic programming during run time.
>
> Signed-off-by: Vikram Garhwal
>
> ---
> Changes from v10:
> Add comment regarding return values of iommu_
Hi,
On Mon, Sep 04, 2023 at 08:51:31AM +0200, Jan Beulich wrote:
> On 02.09.2023 18:21, Javi Merino wrote:
> > Closes #154
> >
> > Signed-off-by: Javi Merino
>
> The title isn't really in line with ...
>
> > --- a/tools/misc/xencov_split
> > +++ b/tools/misc/xencov_split
> > @@ -1,5 +1,7 @@
>
When running with SMMUv3 and UBSAN enabled, the following is printed:
(XEN) UBSAN: Undefined behaviour in drivers/passthrough/arm/smmu-v3.c:297:12
(XEN) left shift of 1 by 31 places cannot be represented in type 'int'
This refers to shift in Q_OVERFLOW_FLAG that is missing 'U' suffix.
While there
When running with SMMUv3 and UBSAN enabled on arm64, there are a lot of
warnings printed related to shifting into sign bit in generic_fls()
as it takes parameter of type int.
Example:
(XEN) UBSAN: Undefined behaviour in ./include/xen/bitops.h:69:11
(XEN) left shift of 134217728 by 4 places cannot
This series contains fixes for UBSAN findings reported when running
with SMMUv3 enabled.
Michal Orzel (2):
xen/arm: smmuv3: Add missing U for shifted constant
xen: Change parameter of generic_fls() to unsigned int
xen/drivers/passthrough/arm/smmu-v3.h | 4 ++--
xen/include/xen/bitops.h
On 04.09.2023 09:19, Nicola Vetrini wrote:
> On 04/09/2023 09:02, Jan Beulich wrote:
>> Further in the cover letter you say "Deviating variables needs more
>> care, and
>> is therefore postponed to another patch", yet then here you annotate a
>> couple
>> of variables as well. Could you clarify w
Some awk binary is used in many places during build,
make sure it is part of the image.
Signed-off-by: Olaf Hering
---
automation/build/suse/opensuse-leap.dockerfile | 1 +
automation/build/suse/opensuse-tumbleweed.dockerfile | 1 +
2 files changed, 2 insertions(+)
diff --git a/automation
On 04/09/2023 09:02, Jan Beulich wrote:
On 01.09.2023 18:34, Nicola Vetrini wrote:
As stated in 'docs/misra/rules.rst' the functions that are used only
by
asm modules do not need to conform to MISRA C:2012 Rule 8.4.
The deviations are carried out with a SAF comment.
Signed-off-by: Nicola Vetri
On 01.09.2023 18:34, Nicola Vetrini wrote:
> As stated in 'docs/misra/rules.rst' the functions that are used only by
> asm modules do not need to conform to MISRA C:2012 Rule 8.4.
> The deviations are carried out with a SAF comment.
>
> Signed-off-by: Nicola Vetrini
> ---
> Where the identifier f
43 matches
Mail list logo