flight 173462 linux-linus real [real]
flight 173467 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/173462/
http://logs.test-lab.xenproject.org/osstest/logs/173467/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-
flight 173461 linux-5.4 real [real]
flight 173465 linux-5.4 real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/173461/
http://logs.test-lab.xenproject.org/osstest/logs/173465/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armh
flight 173463 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173463/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 406ad0582a3df7af498ec4f0adee1a95ceeae64f
baseline version:
ovmf 5ff7d712d489a4fba4e8b
flight 173459 xen-unstable real [real]
flight 173464 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/173459/
http://logs.test-lab.xenproject.org/osstest/logs/173464/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-arm6
Hi Andrew and Jason,
> -Original Message-
> From: Andrew Cooper
> Subject: Re: [PATCH] argo: Remove reachable ASSERT_UNREACHABLE
>
> On 07/10/2022 20:31, Jason Andryuk wrote:
> > I observed this ASSERT_UNREACHABLE in partner_rings_remove
> consistently
> > trip. It was in OpenXT with th
From: Stefano Stabellini
Add SPDX license information to all the *.c files under arch/arm.
Signed-off-by: Stefano Stabellini
---
Changes in v3:
- change xen/arch/arm/domain_page.c to GPL-2.0-or-later
Changes in v2:
- use /* */
- actually check use the right license
- remove stale copyright inf
From: Stefano Stabellini
Add the individual licenses under a new top-level directory named
"LICENSES". Each license file includes its related SPDX tags.
Signed-off-by: Stefano Stabellini
---
LICENSES/BSD-2-Clause | 32 +++
LICENSES/BSD-3-Clause | 36 +++
LICENSES/BSD-3-Clause-Cle
From: Stefano Stabellini
Remove the extra copy of the GPL license and license copyright headers
from CONTRIBUTING and the top-level COPYING.
Mention of the LICENSES/ directory and also mention the SPDX tag.
SPDX support is still in progress and COPYING files in subdirectories
still need to be u
From: Stefano Stabellini
Signed-off-by: Stefano Stabellini
---
CODING_STYLE | 10 ++
1 file changed, 10 insertions(+)
diff --git a/CODING_STYLE b/CODING_STYLE
index 3386ee1d90..5faf274b3a 100644
--- a/CODING_STYLE
+++ b/CODING_STYLE
@@ -14,6 +14,16 @@ explicitly (e.g. tools/libxl/CODIN
Hi all,
This small series introduces SPDX tags to Xen:
1) add a mention to SPDX in CODING_STYLE
2) add a LICENSES directory with licenses and SPDX tags
3) adds the SPDX single-line comment to arch/arm/*.c
Note that arch/arm/*.c is just a start. Also, to make the changes as
mechanical as possible
On Wed, 24 Aug 2022, Bertrand Marquis wrote:
> This patch series is a first attempt to check if we could use Yocto in
> gitlab ci to build and run xen on qemu for arm, arm64 and x86.
>
> The first patch is making sure build-yocto.sh is not catched by
> gitignore.
>
> The second patch is creating
On Fri, 7 Oct 2022, Colin Ian King wrote:
> There is a spelling mistake in a Kconfig description. Fix it.
>
> Signed-off-by: Colin Ian King
Acked-by: Stefano Stabellini
> ---
> drivers/xen/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/xen/Kconfig b
There is a spelling mistake in a Kconfig description. Fix it.
Signed-off-by: Colin Ian King
---
drivers/xen/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig
index a65bd92121a5..d5d7c402b651 100644
--- a/drivers/xen/Kconfig
+++
On Fri, 7 Oct 2022, Michal Orzel wrote:
> Hi Stefano,
>
> On 07/10/2022 00:34, Stefano Stabellini wrote:
> >
> >
> > +xen-devel
> >
> > On Thu, 6 Oct 2022, Michal Orzel wrote:
> >> At the moment, ImageBuilder assumes that all addresses/sizes are
> >> 32-bit max. It sets #{address,size}-cells to
On Fri, 7 Oct 2022, Juergen Gross wrote:
> On 06.10.22 19:48, Oleksandr Tyshchenko wrote:
> > From: Oleksandr Tyshchenko
> >
> > Use the same "xen-grant-dma" device concept (based on generic IOMMU
> > device-tree bindings) for the PCI devices behind device-tree based
> > PCI Host controller.
> >
Hi Dega,
For Xen on Raspberry PI 4, that should work out of the box now and there
are a few users on xen-devel that got it to work successfully recently.
One of the documents that describes how to get Xen to run on RPi4 in
details is the following, although it is 2 years old now:
https://xenprojec
On 10/7/22 20:35, Oleksandr Tyshchenko wrote:
Hi Oleksandr
On 10/6/22 15:09, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
Although XEN_PAGE_SIZE is equal to PAGE_SIZE (4KB) for now, it
would
be more correct to use Xen specific #define-s as XEN_PAGE_SIZE can
be changed at some poi
On 07/10/2022 20:31, Jason Andryuk wrote:
> I observed this ASSERT_UNREACHABLE in partner_rings_remove consistently
> trip. It was in OpenXT with the viptables patch applied.
>
> dom10 shuts down.
> dom7 is REJECTED sending to dom10.
> dom7 shuts down and this ASSERT trips for dom10.
>
> The argo_
On 26/08/2021 11:15, Jan Beulich wrote:
> Returning back truncated frame numbers is unhelpful: Quite likely
> they're not owned by the domain (if it's PV), or we may misguide the
> guest into writing grant entries into a page that it actually uses for
> other purposes.
> Signed-off-by: Jan Beulich
On 26/08/2021 11:14, Jan Beulich wrote:
> The contents of the output arrays are undefined in both cases anyway
> when the operation itself gets marked as failed. There's no value in
> trying to continue after a guest memory access failure.
>
> Signed-off-by: Jan Beulich
Not really Acked-by: Andre
I observed this ASSERT_UNREACHABLE in partner_rings_remove consistently
trip. It was in OpenXT with the viptables patch applied.
dom10 shuts down.
dom7 is REJECTED sending to dom10.
dom7 shuts down and this ASSERT trips for dom10.
The argo_send_info has a domid, but there is no refcount taken on
flight 173456 linux-linus real [real]
flight 173460 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/173456/
http://logs.test-lab.xenproject.org/osstest/logs/173460/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-
On 26/08/2021 11:14, Jan Beulich wrote:
> Unlike for GNTTABOP_setup_table native and compat frame lists are arrays
"GNTTABOP_setup_table, native"
But I think it would also be clearer to follow with
"frame lists for GNTTABOP_get_status_frames are of".
> of the same type (uint64_t). Hence there's
On 07/10/2022 14:49, Jan Beulich wrote:
> On 26.08.2021 12:06, Jan Beulich wrote:
>> The first four patches can be attributed to the former, the last four
>> patches to the latter. The middle patch had been submitted standalone
>> before, has a suitable Reviewed-by tag, but also has an objection by
On 07.10.22 19:16, Oleksandr wrote:
Hello Xenia
>
> On 07.10.22 18:50, Xenia Ragiadakou wrote:
>
>
> Hello Xenia
>
>>
>> On 10/7/22 16:43, Oleksandr Tyshchenko wrote:
>>>
>>> On 07.10.22 10:15, Xenia Ragiadakou wrote:
On 10/7/22 00:13, Oleksandr Tyshchenko wrote:
Hi Oleksandr
On Fri, Oct 07, 2022 at 07:17:41AM +0200, Juergen Gross wrote:
> On 03.10.22 00:20, M. Vefa Bicakci wrote:
> > Hi all,
> >
> > First of all, sorry for the delay!
> >
> > These patches continue the code review for the following patches:
> >
> > https://lore.kernel.org/xen-devel/20220912040002.
flight 173454 linux-5.4 real [real]
flight 173458 linux-5.4 real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/173454/
http://logs.test-lab.xenproject.org/osstest/logs/173458/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armh
flight 173457 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173457/
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 07.10.22 18:50, Xenia Ragiadakou wrote:
Hello Xenia
>
> On 10/7/22 16:43, Oleksandr Tyshchenko wrote:
>>
>> On 07.10.22 10:15, Xenia Ragiadakou wrote:
>>>
>>> On 10/7/22 00:13, Oleksandr Tyshchenko wrote:
>>>
>>> Hi Oleksandr
>>
>>
>> Hello Xenia
>>
>>
>>>
On 06.10.22 20:59, Xenia
On 10/7/22 10:00 AM, Oleksandr Tyshchenko wrote:
On 07.10.22 09:41, Juergen Gross wrote:
Hello Juergen
Use an x86-specific virtio_check_mem_acc_cb() for Xen in order to setup
the correct DMA ops.
Signed-off-by: Juergen Gross
---
V2:
- add missing PV check in xen_virtio_mem_acc() (Oleksandr
On 10/7/22 16:43, Oleksandr Tyshchenko wrote:
On 07.10.22 10:15, Xenia Ragiadakou wrote:
On 10/7/22 00:13, Oleksandr Tyshchenko wrote:
Hi Oleksandr
Hello Xenia
On 06.10.22 20:59, Xenia Ragiadakou wrote:
Hello Xenia
On 10/6/22 15:09, Oleksandr Tyshchenko wrote:
From: Oleksandr
On 07.10.22 15:27, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
Passed to xen_grant_dma_map_page() offset in the page
can be > PAGE_SIZE even if the guest uses the same page granularity
as Xen (4KB).
Before current patch, if such case happened we ended up providing
grants for the who
On 10/7/2022 8:02 AM, Chuck Zmudzinski wrote:
> On 10/6/2022 9:38 AM, Liberalia Tempus, S.L. wrote:
> > Thank you very much for your answers.
> >
> > Finally, after trying some of the solutions proposed by Chuck, I have
> > made the decision to delete the UEFI partition and move it to a normal
>
On 07.10.22 09:41, Juergen Gross wrote:
Hello Juergen
> Use an x86-specific virtio_check_mem_acc_cb() for Xen in order to setup
> the correct DMA ops.
>
> Signed-off-by: Juergen Gross
> ---
> V2:
> - add missing PV check in xen_virtio_mem_acc() (Oleksandr Tyshchenko)
> - add xen_virtio_restrict
On 26.08.2021 12:06, Jan Beulich wrote:
> The first four patches can be attributed to the former, the last four
> patches to the latter. The middle patch had been submitted standalone
> before, has a suitable Reviewed-by tag, but also has an objection by
> Andrew pending, which unfortunately has le
On 07.10.22 10:15, Xenia Ragiadakou wrote:
>
> On 10/7/22 00:13, Oleksandr Tyshchenko wrote:
>
> Hi Oleksandr
Hello Xenia
>
>>
>> On 06.10.22 20:59, Xenia Ragiadakou wrote:
>>
>> Hello Xenia
>>
>>>
>>> On 10/6/22 15:09, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
Alt
From: Oleksandr Tyshchenko
Passed to xen_grant_dma_map_page() offset in the page
can be > PAGE_SIZE even if the guest uses the same page granularity
as Xen (4KB).
Before current patch, if such case happened we ended up providing
grants for the whole region in xen_grant_dma_map_page() which
was r
Hi Jan,
On 07/10/2022 12:06, Jan Beulich wrote:
On 07.10.2022 11:13, Julien Grall wrote:
From: Julien Grall
Signed-off-by: Julien Grall
---
README | 16
SUPPORT.md | 2 +-
xen/Makefile | 2 +-
3 files changed, 10 insertions(+), 10 deletions(-)
I assume CHANG
Hi Jan,
On 07/10/2022 12:02, Jan Beulich wrote:
On 07.10.2022 11:13, Julien Grall wrote:
--- a/docs/process/release-technician-checklist.txt
+++ b/docs/process/release-technician-checklist.txt
@@ -49,6 +49,7 @@ t=RELEASE-$r
* consider bumping sonames of shlibs
* change xen-unstable READM
This is a series from Mirela Simonovic. Ported to 4.16 and with
added changes suggested here
https://lore.kernel.org/all/CAKPH-NjmaZENb8gT=+fobraycrf01_--6gura2ck9di5wiu...@mail.gmail.com
This series contains support for suspend to RAM (in the following text just
'suspend') for Xen on arm64. The
Hello all,
The xenbits disk is getting somewhat full. If everyone could take a minute or
two to take a look in your own home directory and space on /people/, and delete
anything you don’t need, that would be helpful.
`du -k -x | sort -n -r -k 1` is my normal rune for this sort of thing, if it
This commit proposes a new mechanism to query the RUNSTATE_running counter for
a given vcpu from a dom0 userspace application. This commit proposes to expose
that counter by using the acquire_resource interface. The current mechanism
relies on the XEN_DOMCTL_getvcpuinfo and holds a single global do
Add a demonstration tool that uses the stats_table resource to
query vcpus' RUNSTATE_running counter for a DomU.
Signed-off-by: Matias Ezequiel Vara Larsen
---
Changes in v2:
- use period instead of frec
- rely on version to ensure reading is coherent
Changes in v1:
- change the name of the too
Hello all,
The purpose of this RFC is to get feedback about a new acquire resource that
exposes vcpu statistics for a given domain. The current mechanism to get those
statistics is by querying the hypervisor. This mechanism relies on a hypercall
and holds the domctl spinlock during its execution.
flight 173452 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173452/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-qemut-debianhvm-i386-xsm 7 xen-install fail pass in 173436
test-amd64-amd64-libvirt-xsm 20
On 10/6/2022 9:38 AM, Liberalia Tempus, S.L. wrote:
> Thank you very much for your answers.
>
> Finally, after trying some of the solutions proposed by Chuck, I have
> made the decision to delete the UEFI partition and move it to a normal
> MBR system.
Did you know you can keep the GPT partition
flight 173453 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173453/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 173438
test-armhf-armhf-libvirt-qcow2 15 saveres
On 07.10.22 12:32, Mykyta Poturai wrote:
From: Juergen Gross
Instead of freeing percpu areas during suspend and allocating them
again when resuming keep them. Only free an area in case a cpu didn't
come up again when resuming.
It should be noted that there is a potential change in behaviour as
On 07.10.2022 11:13, Julien Grall wrote:
> From: Julien Grall
>
> Signed-off-by: Julien Grall
> ---
> README | 16
> SUPPORT.md | 2 +-
> xen/Makefile | 2 +-
> 3 files changed, 10 insertions(+), 10 deletions(-)
I assume CHANGELOG.md is then going to be updated only
On 07.10.2022 11:13, Julien Grall wrote:
> --- a/docs/process/release-technician-checklist.txt
> +++ b/docs/process/release-technician-checklist.txt
> @@ -49,6 +49,7 @@ t=RELEASE-$r
> * consider bumping sonames of shlibs
>
> * change xen-unstable README (should say "Xen 4.5" in releases and on
Hi Mykyta,
I couldn't find any cover letter for this series in neither my inbox nor
xen-devel. Can you provide one explain the goal of this series (you seem
to have a mix of domain suspend and host suspend)? If it is also based
on an existing series, then it would be nice to mention it (this w
From: Oleksandr Andrushchenko
percpu.c: In function 'cpu_percpu_callback':
percpu.c:61:7: error: this 'if' clause does not guard...
[-Werror=misleading-indentation]
if ( system_state != SYS_STATE_resume )
^~
percpu.c:63:9: note: ...this statement, but the latter is misleadingly ind
From: Mirela Simonovic
The context of CPU general purpose and system control registers
has to be saved on suspend and restored on resume. This is
implemented in hyp_suspend and before the return from hyp_resume
function. The hyp_suspend is invoked just before the PSCI system
suspend call is issue
From: Mirela Simonovic
The resume of Dom0 should always follow Xen's resume. This is
done by unblocking the first vCPU of Dom0.
Signed-off-by: Mirela Simonovic
Signed-off-by: Saeed Nowshadi
---
xen/arch/arm/suspend.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/xen/arch/arm/suspend.
From: Juergen Gross
Instead of freeing percpu areas during suspend and allocating them
again when resuming keep them. Only free an area in case a cpu didn't
come up again when resuming.
It should be noted that there is a potential change in behaviour as
the percpu areas are no longer zeroed out
From: Mirela Simonovic
Timer interrupts have to be disabled while the system is in suspend.
Otherwise, a timer interrupt would fire and wake-up the system.
Suspending the timer interrupts consists of disabling physical EL1
and EL2 timers. The resume consists only of raising timer softirq,
which w
Migrating timers during suspend causes Dom0 to freeze after resume.
Signed-off-by: Mykyta Poturai
---
xen/common/timer.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/xen/common/timer.c b/xen/common/timer.c
index 1bb265ceea..52d4f72a76 100644
--- a/xen/common/timer.c
+++
From: Mirela Simonovic
The MMU needs to be enabled in the resume flow before the context
can be restored (we need to be able to access the context data by
virtual address in order to restore it). The configuration of system
registers prior to branching to the routine that sets up the page
tables
From: Mirela Simonovic
PSCI system suspend function shall be invoked to finalize Xen suspend
procedure. Resume entry point, which needs to be passed via 1st argument
of PSCI system suspend call to the EL3, is hyp_resume. For now, hyp_resume
is just a placeholder that will be implemented in assemb
From: Mirela Simonovic
This is done using generic console_suspend/resume functions that cause
uart driver specific suspend/resume handlers to be called for each
initialized port (if the port has suspend/resume driver handlers
implemented).
Signed-off-by: Mirela Simonovic
Signed-off-by: Saeed No
From: Mirela Simonovic
The rcu_barrier() has to be added to ensure that the per cpu area is
freed before a non-boot CPU tries to initialize it (_free_percpu_area()
has to be called before the init_percpu_area()). This scenario occurs
when non-boot CPUs are hot-unplugged on suspend and hotplugged
From: Mirela Simonovic
The implementation consists of:
-Adding PSCI system suspend call as new PSCI function
-Trapping PSCI system_suspend HVC
-Implementing PSCI system suspend call (virtual interface that allows
guests to suspend themselves)
The PSCI system suspend should be called by a guest
From: Mirela Simonovic
GIC state is saved on system suspend by calling gic_suspend
(this function does not change current state of the GIC but only
saves the values of configuration registers).
The state of GIC has to be restored by calling gic_resume, but only
if the gic_suspend has succeeded. I
From: Mirela Simonovic
Freeze and thaw of domains is reused as implemented for x86. In
addition, system_state variable is updated to represent the actual
state of the system.
Signed-off-by: Mirela Simonovic
Signed-off-by: Saeed Nowshadi
---
xen/arch/arm/suspend.c | 8
1 file changed,
From: Mirela Simonovic
Non-boot CPUs have to be disabled on suspend and enabled on resume
(hotplug-based mechanism). Disabling non-boot CPUs will lead to PSCI
CPU_OFF to be called by each non-boot CPU. Depending on the underlying
platform capabilities, this may lead to the physical powering down
From: Mirela Simonovic
System suspend may lead to a state where GIC would be powered down.
Therefore, Xen should save/restore the context of GIC on suspend/resume.
Note that the context consists of states of registers which are
controlled by the hypervisor. Other GIC registers which are accessibl
From: Mirela Simonovic
These functions will be reused by suspend/resume support for ARM.
Signed-off-by: Mirela Simonovic
Signed-off-by: Saeed Nowshadi
---
xen/common/domain.c | 29 +
xen/include/xen/sched.h | 3 +++
2 files changed, 32 insertions(+)
diff --gi
From: Mirela Simonovic
When Dom0 finalizes its suspend procedure the suspend of Xen is
triggered by calling system_suspend(). Dom0 finalizes the suspend from
its boot core (VCPU#0), which could be mapped to any physical CPU,
i.e. the system_suspend() function could be executed by any physical
CPU
From: Mirela Simonovic
While a domain is suspended its watchdogs must be paused. Otherwise,
if the domain stays in the suspend state for a longer period of time
compared to the watchdog period, the domain would be shutdown on resume.
Proper solution to this problem is to stop (suspend) the watchd
This change is needed to properly implement the suspend/resume actions
for the watchdog timers. To be able to restart watchdog timer after
suspend we need to remember their frequency somewhere. To not bloat the
struct timer a new struct watchdog_timer is introduced, containing the
original timer an
Hi Julien,
> -Original Message-
> From: Julien Grall
> Subject: Re: [PATCH 3/3] Update Xen version to 4.17-rc
> On 07/10/2022 10:51, Henry Wang wrote:
> > Hi Julien,
>
> Hi Henry,
>
> >> -Original Message-
> >> From: Julien Grall
> >> Subject: [PATCH 3/3] Update Xen version to
On 07/10/2022 10:51, Henry Wang wrote:
Hi Julien,
Hi Henry,
-Original Message-
From: Julien Grall
Subject: [PATCH 3/3] Update Xen version to 4.17-rc
From: Julien Grall
Signed-off-by: Julien Grall
I am not very sure, but I think the name should be 4.17-rc1 since
we will likel
Hi Julien,
> -Original Message-
> From: Julien Grall
> Subject: [PATCH 3/3] Update Xen version to 4.17-rc
>
> From: Julien Grall
>
> Signed-off-by: Julien Grall
I am not very sure, but I think the name should be 4.17-rc1 since
we will likely to have rc2 to rc4 according to the previo
Hi Julien,
> -Original Message-
> From: Julien Grall
> Subject: [PATCH 2/3] Config.mk pin QEMU_UPSTREAM_REVISION (prep for
> Xen 4.17 RC1)
>
> From: Julien Grall
>
> Signed-off-by: Julien Grall
Release-acked-by: Henry Wang
Kind regards,
Henry
On 07.10.22 11:13, Julien Grall wrote:
From: Julien Grall
Signed-off-by: Julien Grall
Reviewed-by: Juergen Gross
Juergen
OpenPGP_0xB0DE9DD628BF132F.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
Hi Julien,
> -Original Message-
> From: Julien Grall
> Subject: [PATCH 1/3] process/release-technician-checklist: Explain how the
> banner in README is generated
>
> From: Julien Grall
>
> Signed-off-by: Julien Grall
Release-acked-by: Henry Wang
Kind regards,
Henry
From: Julien Grall
Signed-off-by: Julien Grall
---
Config.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Config.mk b/Config.mk
index 69af1e60d4cc..e0ce59346896 100644
--- a/Config.mk
+++ b/Config.mk
@@ -229,7 +229,7 @@ SEABIOS_UPSTREAM_URL ?= git://xenbits.xen.org/seabio
From: Julien Grall
Signed-off-by: Julien Grall
---
docs/process/release-technician-checklist.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/docs/process/release-technician-checklist.txt
b/docs/process/release-technician-checklist.txt
index 7515da202c92..914f31959ab0 100644
--- a/docs/
From: Julien Grall
Signed-off-by: Julien Grall
---
README | 16
SUPPORT.md | 2 +-
xen/Makefile | 2 +-
3 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/README b/README
index 89a1d0b43c4c..2fdca8861bef 100644
--- a/README
+++ b/README
@@ -1,11 +1,11 @@
From: Julien Grall
Hi all,
This small series is to get the tree ready for cutting the first
4.17 release candidate.
I haven't prepared any RC in the past. So I mainly followed the
guideline in docs/process/release-technician-checklist.txt. Please
let me know if I missed anything.
Cheers,
Juli
flight 173451 linux-linus real [real]
flight 173455 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/173451/
http://logs.test-lab.xenproject.org/osstest/logs/173455/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-
Hi Stefano,
On 07/10/2022 00:34, Stefano Stabellini wrote:
>
>
> +xen-devel
>
> On Thu, 6 Oct 2022, Michal Orzel wrote:
>> At the moment, ImageBuilder assumes that all addresses/sizes are
>> 32-bit max. It sets #{address,size}-cells to 0x2 and puts 0x0 as the
>> value for the first cell. Becaus
On 10/7/22 00:13, Oleksandr Tyshchenko wrote:
Hi Oleksandr
On 06.10.22 20:59, Xenia Ragiadakou wrote:
Hello Xenia
On 10/6/22 15:09, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
Although XEN_PAGE_SIZE is equal to PAGE_SIZE (4KB) for now, it would
be more correct to use Xen sp
83 matches
Mail list logo
