On 27.09.2023 03:05, Stefano Stabellini wrote:
> --- a/docs/misra/rules.rst
> +++ b/docs/misra/rules.rst
> @@ -373,6 +373,11 @@ maintainers if you want to suggest a change.
> - A cast shall not remove any const or volatile qualification from the
> type pointed to by a pointer
> -
>
>
On 27.09.2023 02:29, Stefano Stabellini wrote:
> From: Stefano Stabellini
>
> The feature is not commonly used, and we don't have hardware to test it,
> not in OSSTest, not in Gitlab, and not even ad-hoc manually by community
> members. We could use QEMU to test it, but even that it is known not
On 27.09.2023 00:37, Shawn Anastasio wrote:
> --- a/xen/common/page_alloc.c
> +++ b/xen/common/page_alloc.c
> @@ -1211,6 +1211,14 @@ static unsigned int node_to_scrub(bool get_node)
> } while ( !cpumask_empty(&node_to_cpumask(node)) &&
>(node != local_node) );
>
> +
On 26.09.2023 21:49, Andrew Cooper wrote:
> On 25/09/2023 11:42 pm, Shawn Anastasio wrote:
>> Since ppc64le is still undergoing early bringup, disable the randconfig
>> CI build which was causing spurious CI failures.
>>
>> Signed-off-by: Shawn Anastasio
>> Reported-by: Jan Beulich
>> ---
>> aut
On 26.09.2023 20:35, Shawn Anastasio wrote:
> On 9/26/23 12:43 PM, Shawn Anastasio wrote:
>> On 9/26/23 2:19 AM, Jan Beulich wrote:
>>> On 26.09.2023 01:12, Stefano Stabellini wrote:
On Mon, 25 Sep 2023, Shawn Anastasio wrote:
> Change automation build script to call the make defconfig tar
flight 183186 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/183186/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf be971fc302cbef8f47e2612eda114135f21205e6
baseline version:
ovmf bf0bdacdd6f6cdd2e9ac5
> >> +EVENT_TYPE_PRIV_SWEXC 5 // INT1 #define EVENT_TYPE_SWEXC 6
> >> +// INTO, INT3
> >
> > nit: This turned into INTO (Oh) rather than INT0( zero) in v11
>
> Yes, v11 corrected a bug in v10.
>
> The INTO instruction is "INT on Overflow". No zero involved.
>
> INT3 is thusly named bec
flight 183181 linux-linus real [real]
flight 183187 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/183181/
http://logs.test-lab.xenproject.org/osstest/logs/183187/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Mon, Sep 25, 2023 at 04:05:37PM +, Xen Security wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Xen Security Advisory CVE-2023-20588 / XSA-439
>
> x86/AMD: Divide speculative information leak
>
> ISSU
From: Stefano Stabellini
Following up from the MISRA C group discussion, add Rule 11.9 to
docs/misra/rules.rst.
Signed-off-by: Stefano Stabellini
---
Rule 13.1 also discussed but it is already in docs/misra/rules.rst
---
docs/misra/rules.rst | 5 +
1 file changed, 5 insertions(+)
diff --g
On Tue, 26 Sep 2023, Henry Wang wrote:
> Hi Jan,
>
> > On Sep 26, 2023, at 16:01, Jan Beulich wrote:
> >
> > On 26.09.2023 09:58, Henry Wang wrote:
> >>> On Sep 26, 2023, at 15:46, Jan Beulich wrote:
> >>> Furthermore may I ask that you keep an eye on the physical CPU hotplug
> >>> situation? I
From: Stefano Stabellini
The feature is not commonly used, and we don't have hardware to test it,
not in OSSTest, not in Gitlab, and not even ad-hoc manually by community
members. We could use QEMU to test it, but even that it is known not to
work.
Also take the opportunity to rename the feature
Hi committers,
We will be tagging the 4.18 RC1 on Fri Sep 29, 2023. In order to have enough
time
for OSSTest to do the sync between staging and master, if there is any patch to
be
committed, please commit them by the morning of Thu Sep 28, 2023, EU time and
avoid committing to the staging until
flight 183184 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/183184/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf bf0bdacdd6f6cdd2e9ac5db14b6daf19a5a5bd57
baseline version:
ovmf 39f3c26e8c40e092baeb0
On Tue, 26 Sep 2023, Shawn Anastasio wrote:
> Change automation build script to call the make defconfig target before
> setting CONFIG_DEBUG and extra options. This fixes issues on Power where
> the build fails without using the ppc64_defconfig.
>
> Reported-by: Jan Beulich
> Signed-off-by: Shawn
Hi,
> On Sep 27, 2023, at 06:37, Shawn Anastasio
> wrote:
>
> When building for Power with CONFIG_DEBUG unset, a compiler error gets
> raised inside page_alloc.c's node_to_scrub function:
>
> common/page_alloc.c: In function 'node_to_scrub.part.0':
> common/page_alloc.c:1217:29: error: array s
Hi Shawn,
> On Sep 27, 2023, at 06:37, Shawn Anastasio
> wrote:
>
> Change automation build script to call the make defconfig target before
> setting CONFIG_DEBUG and extra options. This fixes issues on Power where
> the build fails without using the ppc64_defconfig.
>
> Reported-by: Jan Beuli
On Tue, Nov 22, 2022 at 05:12:59PM +, Anthony PERARD wrote:
> On Mon, Nov 14, 2022 at 08:20:10PM +0100, Marek Marczykowski-Górecki wrote:
> > diff --git a/hw/xen/xen_pt.c b/hw/xen/xen_pt.c
> > index 0ec7e52183..269bd26109 100644
> > --- a/hw/xen/xen_pt.c
> > +++ b/hw/xen/xen_pt.c
> > @@ -255,6
flight 183175 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/183175/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-livepatch 7 xen-install fail in 183169 pass in 183175
test-armhf-armhf-xl-credit1 14
Change automation build script to call the make defconfig target before
setting CONFIG_DEBUG and extra options. This fixes issues on Power where
the build fails without using the ppc64_defconfig.
Reported-by: Jan Beulich
Signed-off-by: Shawn Anastasio
---
v3: Drop unnecessary sed.
v2: No change
When building for Power with CONFIG_DEBUG unset, a compiler error gets
raised inside page_alloc.c's node_to_scrub function:
common/page_alloc.c: In function 'node_to_scrub.part.0':
common/page_alloc.c:1217:29: error: array subscript 1 is above array
bounds of 'long unsigned int[1]' [-W
Hello all,
This series contains a few minor fixes to the CI config and one
additional patch to common/ that resolve ppc64-specific CI failures
that Jan discovered.
Thanks,
Shawn Anastasio (2):
automation: Change build script to use arch defconfig
xen/common: Add NUMA node id bounds check to
On 9/26/23 3:54 PM, Andrew Cooper wrote:
> On 26/09/2023 7:54 pm, Shawn Anastasio wrote:
>> When building for Power with CONFIG_DEBUG unset, a compiler error gets
>> raised inside page_alloc.c's node_to_scrub function:
>>
>> common/page_alloc.c: In function 'node_to_scrub.part.0':
>> common/page_al
On 9/26/23 2:56 PM, Andrew Cooper wrote:
> On 26/09/2023 7:54 pm, Shawn Anastasio wrote:
>> diff --git a/automation/scripts/build b/automation/scripts/build
>> index b4edcf010e..19dd9e8270 100755
>> --- a/automation/scripts/build
>> +++ b/automation/scripts/build
>> @@ -22,7 +22,12 @@ if [[ "${RAND
On Tue, 26 Sep 2023, Andrew Cooper wrote:
> On 26/09/2023 7:54 pm, Shawn Anastasio wrote:
> > diff --git a/automation/scripts/build b/automation/scripts/build
> > index b4edcf010e..19dd9e8270 100755
> > --- a/automation/scripts/build
> > +++ b/automation/scripts/build
> > @@ -22,7 +22,12 @@ if [[ "
On Tue, 26 Sep 2023, Shawn Anastasio wrote:
> When building for Power with CONFIG_DEBUG unset, a compiler error gets
> raised inside page_alloc.c's node_to_scrub function:
>
> common/page_alloc.c: In function 'node_to_scrub.part.0':
> common/page_alloc.c:1217:29: error: array subscript 1 is above
On 26/09/2023 7:54 pm, Shawn Anastasio wrote:
> When building for Power with CONFIG_DEBUG unset, a compiler error gets
> raised inside page_alloc.c's node_to_scrub function:
>
> common/page_alloc.c: In function 'node_to_scrub.part.0':
> common/page_alloc.c:1217:29: error: array subscript 1 is above
On 26/09/2023 7:54 pm, Shawn Anastasio wrote:
> diff --git a/automation/scripts/build b/automation/scripts/build
> index b4edcf010e..19dd9e8270 100755
> --- a/automation/scripts/build
> +++ b/automation/scripts/build
> @@ -22,7 +22,12 @@ if [[ "${RANDCONFIG}" == "y" ]]; then
> # RANDCONFIG imp
On 25/09/2023 11:42 pm, Shawn Anastasio wrote:
> Since ppc64le is still undergoing early bringup, disable the randconfig
> CI build which was causing spurious CI failures.
>
> Signed-off-by: Shawn Anastasio
> Reported-by: Jan Beulich
> ---
> automation/gitlab-ci/build.yaml | 18 -
When building for Power with CONFIG_DEBUG unset, a compiler error gets
raised inside page_alloc.c's node_to_scrub function:
common/page_alloc.c: In function 'node_to_scrub.part.0':
common/page_alloc.c:1217:29: error: array subscript 1 is above array
bounds of 'long unsigned int[1]' [-W
Change automation build script to call the make defconfig target before
setting CONFIG_DEBUG and extra options. This fixes issues on Power where
the build fails without using the ppc64_defconfig.
Reported-by: Jan Beulich
Signed-off-by: Shawn Anastasio
---
v2: No changes.
automation/scripts/bui
Hello all,
This series contains a few minor fixes to the CI config and one
additional patch to common/ that resolve ppc64-specific CI failures
that Jan discovered.
Thanks,
Shawn Anastasio (2):
automation: Change build script to use arch defconfig
xen/common: Add NUMA node id bounds check to
flight 183173 linux-5.4 real [real]
flight 183182 linux-5.4 real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/183173/
http://logs.test-lab.xenproject.org/osstest/logs/183182/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
t
On 9/26/23 12:43 PM, Shawn Anastasio wrote:
> On 9/26/23 2:19 AM, Jan Beulich wrote:
>> On 26.09.2023 01:12, Stefano Stabellini wrote:
>>> On Mon, 25 Sep 2023, Shawn Anastasio wrote:
Change automation build script to call the make defconfig target before
setting CONFIG_DEBUG and extra opt
On 9/26/23 2:32 AM, Jan Beulich wrote:
> On 26.09.2023 00:42, Shawn Anastasio wrote:
>> When building for Power with CONFIG_DEBUG unset, a compiler error gets
>> raised inside page_alloc.c's node_to_scrub function, likely due to the
>> increased optimization level:
>>
>> common/page_alloc.c: In fun
On 9/26/23 2:19 AM, Jan Beulich wrote:
> On 26.09.2023 01:12, Stefano Stabellini wrote:
>> On Mon, 25 Sep 2023, Shawn Anastasio wrote:
>>> Change automation build script to call the make defconfig target before
>>> setting CONFIG_DEBUG and extra options. This fixes issues on Power where
>>> the bui
flight 183179 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/183179/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
On Tue, Sep 26, 2023 at 11:27:48AM -0400, Stewart Hildebrand wrote:
> On 9/26/23 04:07, Roger Pau Monné wrote:
> > On Mon, Sep 25, 2023 at 05:49:00PM -0400, Stewart Hildebrand wrote:
> >> On 9/22/23 04:44, Roger Pau Monné wrote:
> >>> On Tue, Aug 29, 2023 at 11:19:47PM +, Volodymyr Babchuk wrot
On 9/26/23 04:07, Roger Pau Monné wrote:
> On Mon, Sep 25, 2023 at 05:49:00PM -0400, Stewart Hildebrand wrote:
>> On 9/22/23 04:44, Roger Pau Monné wrote:
>>> On Tue, Aug 29, 2023 at 11:19:47PM +, Volodymyr Babchuk wrote:
From: Stewart Hildebrand
Skip mapping the BAR if it is no
flight 183176 xen-unstable-smoke real [real]
flight 183177 xen-unstable-smoke real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/183176/
http://logs.test-lab.xenproject.org/osstest/logs/183177/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which co
flight 183172 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/183172/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 183126
test-armhf-armhf-libvirt-qcow2 15 saveres
Hi Luca,
On Tue, Sep 26, 2023 at 10:10:57AM +, Luca Fancellu wrote:
[...]
> >> I might be wrong, but reading the specifications seems that “status” is
> >> not a property
> >> of the child nodes of /reserved-memory, so I’m not sure Xen should do
> >> something about it.
> >
> > Please take
Hi Michal,
On Tue, Sep 26, 2023 at 10:36:04AM +0200, Michal Orzel wrote:
[...]
> > Essentially, this issue is caused by the Xen hypervisor which misses to
> > handle the status for the memory nodes (for both the normal memory nodes
> > and the reserved memory nodes) and transfers them to the Lin
> On 26 Sep 2023, at 11:04, Michal Orzel wrote:
>
> Hi Luca,
>
> On 26/09/2023 11:52, Luca Fancellu wrote:
>>
>>
>>> On 26 Sep 2023, at 06:33, Leo Yan wrote:
>>>
>>> During the Linux kernel booting, an error is reported by the Xen
>>> hypervisor:
>>>
>>> (XEN) arch/arm/p2m.c:2202: d0v0: F
Hi Luca,
On 26/09/2023 11:52, Luca Fancellu wrote:
>
>
>> On 26 Sep 2023, at 06:33, Leo Yan wrote:
>>
>> During the Linux kernel booting, an error is reported by the Xen
>> hypervisor:
>>
>> (XEN) arch/arm/p2m.c:2202: d0v0: Failing to acquire the MFN 0x1a02dc
>>
>> The kernel attempts to use a
flight 183174 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/183174/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 39f3c26e8c40e092baeb0ec4d0396498506e0a9e
baseline version:
ovmf c70d91442889078eb94e0
> On 26 Sep 2023, at 06:33, Leo Yan wrote:
>
> During the Linux kernel booting, an error is reported by the Xen
> hypervisor:
>
> (XEN) arch/arm/p2m.c:2202: d0v0: Failing to acquire the MFN 0x1a02dc
>
> The kernel attempts to use an invalid memory frame number, which can be
> converted to: 0
On 26/09/2023 9:10 am, Nikolay Borisov wrote:
> On 23.09.23 г. 12:41 ч., Xin Li wrote:
>> diff --git a/arch/x86/include/asm/trapnr.h
>> b/arch/x86/include/asm/trapnr.h
>> index f5d2325aa0b7..8d1154cdf787 100644
>> --- a/arch/x86/include/asm/trapnr.h
>> +++ b/arch/x86/include/asm/trapnr.h
>> @@ -2,6
flight 183169 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/183169/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-arndale 8 xen-boot fail in 183161 pass in 183169
test-amd64-i386-livepatch 7
Hello,
On 26/09/2023 07:33, Leo Yan wrote:
>
>
> During the Linux kernel booting, an error is reported by the Xen
> hypervisor:
>
> (XEN) arch/arm/p2m.c:2202: d0v0: Failing to acquire the MFN 0x1a02dc
>
> The kernel attempts to use an invalid memory frame number, which can be
> converted to:
On 23.09.23 г. 12:41 ч., Xin Li wrote:
Intel VT-x classifies events into eight different types, which is
inherited by FRED for event identification. As such, event type
becomes a common x86 concept, and should be defined in a common x86
header.
Add event type macros to , and use it in .
Sugg
Hi Jan,
> On Sep 26, 2023, at 16:01, Jan Beulich wrote:
>
> On 26.09.2023 09:58, Henry Wang wrote:
>>> On Sep 26, 2023, at 15:46, Jan Beulich wrote:
>>> Furthermore may I ask that you keep an eye on the physical CPU hotplug
>>> situation? It continues to be documented as fully supported, and as
On Mon, Sep 25, 2023 at 05:49:00PM -0400, Stewart Hildebrand wrote:
> On 9/22/23 04:44, Roger Pau Monné wrote:
> > On Tue, Aug 29, 2023 at 11:19:47PM +, Volodymyr Babchuk wrote:
> >> From: Stewart Hildebrand
> >>
> >> Skip mapping the BAR if it is not in a valid range.
> >>
> >> Signed-off-by:
On 26.09.2023 09:58, Henry Wang wrote:
>> On Sep 26, 2023, at 15:46, Jan Beulich wrote:
>> Furthermore may I ask that you keep an eye on the physical CPU hotplug
>> situation? It continues to be documented as fully supported, and as long as
>> that's the case 47342d8f490c (" x86/ACPI: Ignore entri
Hi Jan,
> On Sep 26, 2023, at 15:46, Jan Beulich wrote:
>
> On 25.09.2023 09:24, Jan Beulich wrote:
>> On 25.09.2023 03:25, Henry Wang wrote:
>>> Hi everyone,
>>>
>>> This is the reminder that we are currently in code freeze. The hard code
>>> freeze date will be in two weeks, i.e. Fri Oct 6, 2
On 25.09.2023 12:53, andrew.coop...@citrix.com wrote:
> On 25/09/2023 10:11 am, Nicola Vetrini wrote:
>> diff --git a/xen/include/xen/vga.h b/xen/include/xen/vga.h
>> index f72b63d446b1..9b2c47971d0c 100644
>> --- a/xen/include/xen/vga.h
>> +++ b/xen/include/xen/vga.h
>> @@ -13,6 +13,12 @@
>>
>>
Hi Julien,
On Wed, Sep 20, 2023 at 11:36:24AM +0100, Julien Grall wrote:
[...]
> > Host dt:
> > memory@4000 {
> > reg = <0x00 0x4000 0x01 0x00>;
> > device_type = "memory";
> > };
> >
> > reserved-memory {
> > #size-cells = <0x02>;
> > #address-cells = <0x02>;
> >
On 25.09.2023 09:24, Jan Beulich wrote:
> On 25.09.2023 03:25, Henry Wang wrote:
>> Hi everyone,
>>
>> This is the reminder that we are currently in code freeze. The hard code
>> freeze date will be in two weeks, i.e. Fri Oct 6, 2023.
>>
>> The planned date for 4.18 rc1 is this Friday, i.e. Sep 29,
On 26.09.2023 09:32, Jan Beulich wrote:
> On 26.09.2023 00:42, Shawn Anastasio wrote:
>> When building for Power with CONFIG_DEBUG unset,
Hmm, depending on what gcc versions are used in CI, the above may be the
reason why ...
>> a compiler error gets
>> raised inside page_alloc.c's node_to_scrub
On 26.09.2023 00:42, Shawn Anastasio wrote:
> When building for Power with CONFIG_DEBUG unset, a compiler error gets
> raised inside page_alloc.c's node_to_scrub function, likely due to the
> increased optimization level:
>
> common/page_alloc.c: In function 'node_to_scrub.part.0':
> common/page_a
On 26.09.2023 01:12, Stefano Stabellini wrote:
> On Mon, 25 Sep 2023, Shawn Anastasio wrote:
>> Change automation build script to call the make defconfig target before
>> setting CONFIG_DEBUG and extra options. This fixes issues on Power where
>> the build fails without using the ppc64_defconfig.
>
On 26.09.23 09:16, Viresh Kumar wrote:
On 29-08-23, 17:59, Viresh Kumar wrote:
Hello,
Now that irqfd support (backend to guest interrupt) is already merged, this
series solves the other part of the problem, i.e. ioeventfd (guest to backend
interrupt).
More details inside the commits.
Can som
On 29-08-23, 17:59, Viresh Kumar wrote:
> Hello,
>
> Now that irqfd support (backend to guest interrupt) is already merged, this
> series solves the other part of the problem, i.e. ioeventfd (guest to backend
> interrupt).
>
> More details inside the commits.
Can someone help review this please
63 matches
Mail list logo
