> On 29 Nov 2022, at 23:51, Stefano Stabellini wrote:
>
> On Mon, 28 Nov 2022, Luca Fancellu wrote:
>> Currently the script convert_misra_doc.py is using a loop through
>> range(1,22) to enumerate rules that needs to be skipped, however
>> range function does not include the stop counter in th
On Tue, Nov 29, 2022 at 02:12:10PM -0800, Stefano Stabellini wrote:
> On Tue, 29 Nov 2022, Roger Pau Monne wrote:
> > The hvc machinery registers both a console and a tty device based on
> > the hv ops provided by the specific implementation. Those two
> > interfaces however have different locks,
On 30.11.2022 10:26, Roger Pau Monné wrote:
> On Tue, Nov 29, 2022 at 02:12:10PM -0800, Stefano Stabellini wrote:
>> On Tue, 29 Nov 2022, Roger Pau Monne wrote:
>>> The hvc machinery registers both a console and a tty device based on
>>> the hv ops provided by the specific implementation. Those tw
On Wed, Nov 30, 2022 at 10:34:41AM +0100, Jan Beulich wrote:
> On 30.11.2022 10:26, Roger Pau Monné wrote:
> > On Tue, Nov 29, 2022 at 02:12:10PM -0800, Stefano Stabellini wrote:
> >> On Tue, 29 Nov 2022, Roger Pau Monne wrote:
> >>> The hvc machinery registers both a console and a tty device based
flight 174993 qemu-mainline real [real]
flight 174997 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/174993/
http://logs.test-lab.xenproject.org/osstest/logs/174997/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-am
On 30/11/2022 07:52, Jan Beulich wrote:On 29.11.2022 21:56, Andrew
Cooper wrote:
>> On 29/11/2022 14:55, Jan Beulich wrote:
>>> By defining the constant to zero when !SHADOW_PAGING we give compilers
>>> the chance to eliminate a little more dead code elsewhere in the tree.
>>> Plus, as a minor bene
flight 174994 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174994/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 12 windows-install fail in 174984 pass in
174994
test-armhf-armhf-libvirt
On 30/11/2022 07:09, Jan Beulich wrote:
On 29.11.2022 19:18, Ayan Kumar Halder wrote:
On 29/11/2022 15:52, Julien Grall wrote:
On 29/11/2022 16:23, Ayan Kumar Halder wrote:
On 29/11/2022 14:52, Julien Grall wrote:
On 29/11/2022 14:57, Ayan Kumar Halder wrote:
--- a/xen/common/page_alloc.c
Hi,
I am porting Xen Hypervisor on raspberry pi4. I could port xen minimal
image as host & wayland based GUI image as guest. Now I am trying to bring
up guest Display (using vncviewer) which is not coming up, even I could see
xen-fbfront driver on guest and Debugged
xen-fbfront.c
Xenbusprobe_bac
Hi Stefano,
> I think the revert of the cppcheck integration in xen/Makefile and
> xen/tools/merge_cppcheck_reports.py could be a separate patch. There is
> no need to make sure cppcheck support in the xen Makefile is
> "bisectable". That patch could have my acked-by already.
Ok I will split thes
On 30.11.2022 12:27, Ayan Kumar Halder wrote:
> Looking at "min(flsl(mfn + 1) - 1 + PAGE_SHIFT, PADDR_BITS);", I do not
> understand the reason for "... -1" (ie subtracting by 1).
>
> Do you know the reason ?
That's because fls() and flsl() and friends return 1-based bit indexes
(with 0 being re
Add containers suitable to run yocto kirkstone build based on ubuntu
22.04. It contains all packages required by Yocto and a checkout of the
layers required to build Xen with Yocto.
Add a generic docker image template to be used to automatically generate
docker files for different configurations:
Add make clean support to remove the containers from the local docker
registry.
make clean- must be called to remove an image:
make clean-yocto/kirkstone-qemuarm: remove yocto kirkstone for qemuarm
image
Signed-off-by: Bertrand Marquis
---
Changes in v5:
- remove cleaning of all images using make
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 introducing a container template from which container
files can be generated for all combinations we want to support (qemu
arm, arm64 and x86 tar
From: Michal Orzel
Populate test jobs for Yocto based tests using the provided containers.
Due to the size restrictions, it is currently not possible to split the
build and run tasks, therefore everything is done in a single step.
Test jobs for the supported Yocto targets are generic to avoid th
On 30/11/2022 12:01, Jan Beulich wrote:
On 30.11.2022 12:27, Ayan Kumar Halder wrote:
Looking at "min(flsl(mfn + 1) - 1 + PAGE_SHIFT, PADDR_BITS);", I do not
understand the reason for "... -1" (ie subtracting by 1).
Do you know the reason ?
That's because fls() and flsl() and friends return
flight 174995 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174995/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 174960
test-armhf-armhf-libvirt-raw 15 saveresto
Hi Bertrand,
On 30/11/2022 13:15, Bertrand Marquis wrote:
>
>
> From: Michal Orzel
>
> Populate test jobs for Yocto based tests using the provided containers.
> Due to the size restrictions, it is currently not possible to split the
> build and run tasks, therefore everything is done in a sing
Hi Bertrand,
On 30/11/2022 13:15, Bertrand Marquis wrote:
>
>
> Add make clean support to remove the containers from the local docker
> registry.
> make clean- must be called to remove an image:
> make clean-yocto/kirkstone-qemuarm: remove yocto kirkstone for qemuarm
> image
>
> Signed-off-by:
On Wed, 30 Nov 2022 08:09:53 +0100
Jan Beulich wrote:
Hi Ayan,
> On 29.11.2022 19:18, Ayan Kumar Halder wrote:
> > On 29/11/2022 15:52, Julien Grall wrote:
> >> On 29/11/2022 16:23, Ayan Kumar Halder wrote:
> >>> On 29/11/2022 14:52, Julien Grall wrote:
> On 29/11/2022 14:57, Ayan Kum
Hi Bertrand,
I will try to build and run the yocto containers for a test.
In the meantime I just spotted one thing.
On 30/11/2022 13:15, Bertrand Marquis wrote:
>
>
> Add containers suitable to run yocto kirkstone build based on ubuntu
> 22.04. It contains all packages required by Yocto and a c
On 28/11/2022 12:26, Jan Beulich wrote:
On 28.11.2022 12:06, Roger Pau Monné wrote:
On Mon, Nov 28, 2022 at 09:21:47AM +0100, Jan Beulich wrote:
On 26.11.2022 23:19, Julien Grall wrote:
On 25/11/2022 14:15, Per Bilse wrote:
This patch modifies ioreq_broadcast() to allow partial success.
The
On 11/30/22 02:52, Jan Beulich wrote:
On 29.11.2022 21:56, Andrew Cooper wrote:
On 29/11/2022 14:55, Jan Beulich wrote:
By defining the constant to zero when !SHADOW_PAGING we give compilers
the chance to eliminate a little more dead code elsewhere in the tree.
Plus, as a minor benefit, the gen
Hi Michal,
> On 30 Nov 2022, at 13:27, Michal Orzel wrote:
>
> Hi Bertrand,
>
> I will try to build and run the yocto containers for a test.
> In the meantime I just spotted one thing.
I will wait until tomorrow for a v6 in case you find issues.
>
> On 30/11/2022 13:15, Bertrand Marquis wrot
Hi Michal,
> On 30 Nov 2022, at 13:02, Michal Orzel wrote:
>
> Hi Bertrand,
>
> On 30/11/2022 13:15, Bertrand Marquis wrote:
>>
>>
>> From: Michal Orzel
>>
>> Populate test jobs for Yocto based tests using the provided containers.
>> Due to the size restrictions, it is currently not possibl
The hvc machinery registers both a console and a tty device based on
the hv ops provided by the specific implementation. Those two
interfaces however have different locks, and there's no single locks
that's shared between the tty and the console implementations, hence
the driver needs to protect i
Hi Bertrand,
On 30/11/2022 16:07, Bertrand Marquis wrote:
>
>
> Hi Michal,
>
>> On 30 Nov 2022, at 13:02, Michal Orzel wrote:
>>
>> Hi Bertrand,
>>
>> On 30/11/2022 13:15, Bertrand Marquis wrote:
>>>
>>>
>>> From: Michal Orzel
>>>
>>> Populate test jobs for Yocto based tests using the provide
Hi Michal
> On 30 Nov 2022, at 15:23, Michal Orzel wrote:
>
> Hi Bertrand,
>
> On 30/11/2022 16:07, Bertrand Marquis wrote:
>>
>>
>> Hi Michal,
>>
>>> On 30 Nov 2022, at 13:02, Michal Orzel wrote:
>>>
>>> Hi Bertrand,
>>>
>>> On 30/11/2022 13:15, Bertrand Marquis wrote:
F
On 30/11/2022 13:13, Andre Przywara wrote:
On Wed, 30 Nov 2022 08:09:53 +0100
Jan Beulich wrote:
Hi Ayan,
Hi Andre,
On 29.11.2022 19:18, Ayan Kumar Halder wrote:
On 29/11/2022 15:52, Julien Grall wrote:
On 29/11/2022 16:23, Ayan Kumar Halder wrote:
On 29/11/2022 14:52, Julien Grall wro
On Wed, Nov 30, 2022 at 12:15:08PM +, Bertrand Marquis wrote:
> --- a/automation/build/Makefile
> +++ b/automation/build/Makefile
> @@ -28,3 +28,13 @@ all: $(CONTAINERS)
> clean:
> rm -f yocto/*.dockerfiles
>
> +define CLEAN_RULE
> +.PHONY: clean-$(1)
> +clean-$(1):
> +ifneq ($$(shell
On Tue, Nov 29, 2022 at 09:43:53AM -0800, Dave Hansen wrote:
> On 11/21/22 02:21, Roger Pau Monne wrote:
> > When running as a Xen dom0 the number of CPUs available to Linux can
> > be different from the number of CPUs present on the system, but in
> > order to properly fetch processor performance
Hi Anthony,
> On 30 Nov 2022, at 15:48, Anthony PERARD wrote:
>
> On Wed, Nov 30, 2022 at 12:15:08PM +, Bertrand Marquis wrote:
>> --- a/automation/build/Makefile
>> +++ b/automation/build/Makefile
>> @@ -28,3 +28,13 @@ all: $(CONTAINERS)
>> clean:
>> rm -f yocto/*.dockerfiles
>>
>> +d
On Wed, 30 Nov 2022 15:39:56 +
Ayan Kumar Halder wrote:
Hi Ayan,
> On 30/11/2022 13:13, Andre Przywara wrote:
> > On Wed, 30 Nov 2022 08:09:53 +0100
> > Jan Beulich wrote:
> >
> > Hi Ayan,
> Hi Andre,
> >
> >> On 29.11.2022 19:18, Ayan Kumar Halder wrote:
> >>> On 29/11/2022 15:52, Ju
On Wed, Nov 30, 2022 at 12:15:07PM +, Bertrand Marquis wrote:
> diff --git a/automation/build/Makefile b/automation/build/Makefile
> index a4b2b85178cf..72a5335baec1 100644
> --- a/automation/build/Makefile
> +++ b/automation/build/Makefile
> @@ -1,13 +1,18 @@
>
> # the base of where these c
The currently lockless access to the xen console list in
vtermno_to_xencons() is incorrect, as additions and removals from the
list can happen anytime, and as such the traversal of the list to get
the private console data for a given termno needs to happen with the
lock held. Note users that modif
Hi Anthony,
> On 30 Nov 2022, at 16:25, Anthony PERARD wrote:
>
> On Wed, Nov 30, 2022 at 12:15:07PM +, Bertrand Marquis wrote:
>> diff --git a/automation/build/Makefile b/automation/build/Makefile
>> index a4b2b85178cf..72a5335baec1 100644
>> --- a/automation/build/Makefile
>> +++ b/automat
On 11/30/22 07:53, Roger Pau Monné wrote:
> On Tue, Nov 29, 2022 at 09:43:53AM -0800, Dave Hansen wrote:
>> On 11/21/22 02:21, Roger Pau Monne wrote:
>>> When running as a Xen dom0 the number of CPUs available to Linux can
>>> be different from the number of CPUs present on the system, but in
>>> o
Xenstored always needs to bind the DOM_EXC VIRQ.
Instead of doing it shortly after the call to Event.init(), do it in the
init() call itself. This removes the need for the field to be a mutable
option.
It will also simplify a future change to restore both parts from the live
update record, rathe
This file has some style problems so severe that they interfere with the
readability of the subsequent bugfix patches.
Fix these issues ahead of time, to make the subsequent changes more readable.
No functional change.
Signed-off-by: Andrew Cooper
---
CC: Christian Lindig
CC: David Scott
CC:
This will make the logic clearer when we plumb local_port through these
functions.
While changing this, simplify the construct in Domains.create0 to separate the
remote port handling from the interface.
Signed-off-by: Andrew Cooper
---
CC: Christian Lindig
CC: David Scott
CC: Edwin Torok
CC:
Inter-domain event channels are always a pair of local and remote ports.
Right now the handling is asymmetric, caused by the fact that the evtchn is
bound after the associated Domain object is constructed.
First, move binding of the event channel into the Domain.make() constructor.
This means the
Generally speaking, the event channel local/remote port is fixed for the
lifetime of the associated domain object. The exception to this is a
secondary XS_INTRODUCE (defined to re-bind to a new event channel) which pokes
around at the domain object's internal state.
We need to refactor the evtchn
From: Edwin Török
Closing the evtchn handle will unbind and free all local ports. The new
xenstored would need to rebind all evtchns, which is work that we don't want
or need to be doing during the critical handover period.
However, it turns out that the Windows PV drivers also rebind their loc
Patch 6 is already acked and queued for 4.18, but testing has identified it
was incomplete. Specifically, the DOM_EXC virq needs handling across live
update, otherwise domain shutdown events go awry.
Therefore, this v2 series is presented with 5 patches of refactoring, leading
up to the virq corr
> On 30 Nov 2022, at 16:54, Andrew Cooper wrote:
>
> This file has some style problems so severe that they interfere with the
> readability of the subsequent bugfix patches.
>
> Fix these issues ahead of time, to make the subsequent changes more readable.
>
> No functional change.
>
> Signed
> On 30 Nov 2022, at 16:54, Andrew Cooper wrote:
>
> Generally speaking, the event channel local/remote port is fixed for the
> lifetime of the associated domain object. The exception to this is a
> secondary XS_INTRODUCE (defined to re-bind to a new event channel) which pokes
> around at the
> On 30 Nov 2022, at 16:54, Andrew Cooper wrote:
>
> This will make the logic clearer when we plumb local_port through these
> functions.
>
> While changing this, simplify the construct in Domains.create0 to separate the
> remote port handling from the interface.
>
> Signed-off-by: Andrew Coo
> On 30 Nov 2022, at 16:54, Andrew Cooper wrote:
>
> Xenstored always needs to bind the DOM_EXC VIRQ.
>
> Instead of doing it shortly after the call to Event.init(), do it in the
> init() call itself. This removes the need for the field to be a mutable
> option.
>
> It will also simplify a f
> On 30 Nov 2022, at 16:54, Andrew Cooper wrote:
>
> Inter-domain event channels are always a pair of local and remote ports.
> Right now the handling is asymmetric, caused by the fact that the evtchn is
> bound after the associated Domain object is constructed.
>
> First, move binding of the
Not to be confused which hvm_get_param, which also exists and has a
different, more error-prone interface.
This one always returns a 64-bit value, and that is retained in the
OCaml binding as well, returning 'int64' (and not int, or nativeint
which might have a different size).
The integer here i
Add a .clang-format configuration that tries to match CODING_STYLE where
possible.
I was not able to express the special casing of braces after 'do'
though, this can only be controlled generally for all control
statements.
It is imperfect, but should be better than the existing bindings, which
do
Add an .editorconfig to make it easier to keep patches compatible with
Xen's coding style, and to reemphasize what Xen's coding style is.
I thought that Xen demands tabs rather than spaces (which is more
difficult with OCaml because indentation tools use spaces,
and the use of tabs requires changi
xs_wire.h fails to compile without this, and a slight rearrangement of
header includes (e.g. by clang-format) could cause the file to fail to
compile.
Be more robust and include the needed header file.
---
tools/ocaml/libs/xb/xenbus_stubs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tool
Add bindings to xc_evtchn_status and hvm_param_get, useful for xenopsd
and for recovery from failed live updates.
.editorconfig helps me format the source code with the desired Xen
coding style (now that the reindent patch has switched it to spaces as
desired by the Xen project).
If you don't have
There is no API or ioctl to query event channel status, it is only
present in xenctrl.h
The C union is mapped to an OCaml variant exposing just the value from the
correct union tag.
Querying event channel status is useful when analyzing Windows VMs that
may have reset and changed the xenstore eve
flight 174996 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174996/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-examine 8 reboot fail REGR. vs. 173462
test-arm64-arm64-xl
On Mon, Nov 28, 2022 at 8:44 AM Marek Marczykowski-Górecki
wrote:
>
> On Mon, Nov 21, 2022 at 05:16:37PM +0100, Marek Marczykowski-Górecki wrote:
> > On Mon, Nov 21, 2022 at 10:41:34AM -0500, Jason Andryuk wrote:
> > > On Sat, Nov 19, 2022 at 11:33 AM Marek Marczykowski-Górecki
> > > wrote:
> > >
On Wed, 30 Nov 2022, Luca Fancellu wrote:
> Hi Stefano,
>
> > I think the revert of the cppcheck integration in xen/Makefile and
> > xen/tools/merge_cppcheck_reports.py could be a separate patch. There is
> > no need to make sure cppcheck support in the xen Makefile is
> > "bisectable". That patch
On Wed, 30 Nov 2022, Luca Fancellu wrote:
> > On 29 Nov 2022, at 23:51, Stefano Stabellini wrote:
> >
> > On Mon, 28 Nov 2022, Luca Fancellu wrote:
> >> Currently the script convert_misra_doc.py is using a loop through
> >> range(1,22) to enumerate rules that needs to be skipped, however
> >> ran
+Vipul
Hi Dega,
Vipul recently found a similar issue. He is using "vfb" in the xl config
file, the guest is created but he is getting a black screen.
We checked the xenstore output and frontend and backend seem to be
properly initialized and connected. I am not sure how to proceed if not
by add
On Wed, 30 Nov 2022, Bertrand Marquis wrote:
> Add containers suitable to run yocto kirkstone build based on ubuntu
> 22.04. It contains all packages required by Yocto and a checkout of the
> layers required to build Xen with Yocto.
>
> Add a generic docker image template to be used to automatical
On Wed, 30 Nov 2022, Roger Pau Monne wrote:
> The hvc machinery registers both a console and a tty device based on
> the hv ops provided by the specific implementation. Those two
> interfaces however have different locks, and there's no single locks
> that's shared between the tty and the console
On Wed, 30 Nov 2022, Roger Pau Monne wrote:
> The currently lockless access to the xen console list in
> vtermno_to_xencons() is incorrect, as additions and removals from the
> list can happen anytime, and as such the traversal of the list to get
> the private console data for a given termno needs
flight 174998 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174998/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-examine 8 reboot fail REGR. vs. 173462
test-arm64-arm64-xl
The build of the qemux86-64 container still fails, logs attached.
I tested the full gitlab-ci pipeline for qemuarm and qemuarm64 and they
both succeeded.
On Wed, 30 Nov 2022, Bertrand Marquis wrote:
> This patch series is a first attempt to check if we could use Yocto in
> gitlab ci to build and r
On Tue, 29 Nov 2022 06:17:02 + Lin Liu wrote:
> A NAPI is setup for each network sring to poll data to kernel
> The sring with source host is destroyed before live migration and
> new sring with target host is setup after live migration.
> The NAPI for the old sring is not deleted until setup n
flight 175001 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175001/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf beb0f8d483dfbec2fd3a2db425e0c1871b0d29eb
baseline version:
ovmf dd3ba82d31a6d3cc4564d
flight 174999 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174999/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-libvirt-raw 8 xen-boot fail in 174994 pass in 174999
test-amd64-amd64-libvirt-qemuu-d
68 matches
Mail list logo
