flight 174168 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174168/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 174112
test-armhf-armhf-libvirt-qcow2 15
Hi Olaf,
On Thu, Oct 20, 2022 at 05:13:06PM +0200, Olaf Hering wrote:
> After reading the patch again, the newly added documentation states:
> "This option should be a path to a kernel image."
>
> I think it needs to be more specific: is it expecting an absolute path, or
> just the basename of
flight 174174 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174174/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-xl-seattle 8 xen-boot fail REGR. vs. 173462
Hi Bertrand,
> -Original Message-
> From: Bertrand Marquis
> Subject: Re: [PATCH v2 4/4] vpci: include xen/vmap.h to fix build on ARM
>
> Hi,
>
> > On 21 Oct 2022, at 15:40, Henry Wang wrote:
> >
> > (+ Arm maintainers)
> >
> > Hi Oleksandr,
> >
> >> -Original Message-
> >>
flight 174183 xen-4.15-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174183/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-xl-seattle 14 guest-start fail REGR. vs. 172547
On 10/21/22 18:31, Ayan Kumar Halder wrote:
Hi Ayan
Refer Arm IHI 0069H ID020922,
The upper 32 bits of GICR_TYPER represent the affinity
whereas the lower 32 bits represent the other bits (eg processor
number, etc).
MPIDR_AFFINITY_LEVEL() returns a 32 bit number on aarch32. Thus, this
is
Hi Stefano,
On 21/10/2022 20:36, Stefano Stabellini wrote:
For the NULL scheduler, it is clearly important to many users so it
would be valuable to move it to "supported, non security supported" and
enabling it by default in the build. I don't recall if we still have any
known outstanding
On 20/10/2022 12:01, Roger Pau Monné wrote:
> Hello,
>
> As part of some follow up improvements to my VIRT_SPEC_CTRL series we
> have been discussing what the usage of SSBD should be for the
> hypervisor itself. There's currently a `spec-ctrl=ssbd` option [0],
> that has an out of date
The pull request you sent on Fri, 21 Oct 2022 11:31:19 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for-linus-6.1-rc2-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1d61754caa8c69f566504e63c8b3f3a2df0954c8
Thank you!
--
Deet-doot-dot, I
On Wed, 19 Oct 2022, Michal Orzel wrote:
> At the moment, we define lots of test jobs in test.yaml, that make use
> of the same configuration sections like variables, tags, artifacts.
> Introduce templates (hidden jobs whose names start with a dot) to
> reduce the overhead and simplify the file
On 10/21/22 18:31, Ayan Kumar Halder wrote:
Hi Ayan
Refer https://elixir.bootlin.com/linux/v6.1-rc1/source/arch/arm64/ \
include/asm/cputype.h#L14 , these macros are specific for arm64.
When one computes MPIDR_LEVEL_SHIFT(3), it crosses the width of a 32
bit register.
Refer
On Fri, 21 Oct 2022, Leo Yan wrote:
> Hi Stefano and all,
>
> On Mon, Oct 17, 2022 at 04:50:05PM -0700, Stefano Stabellini wrote:
>
> [...]
>
> > > We can see DomU sends notification with timestamp (raw counter) is
> > > 4989078592 and Dom0 receives the interrupt with timestamp 4989092169.
> >
flight 174152 xen-4.13-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174152/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-xl-xsm 14 guest-start fail REGR. vs. 172549
On Fri, 21 Oct 2022, Oleksandr Tyshchenko wrote:
> From: Oleksandr Tyshchenko
>
> Use the same "xen-grant-dma" device concept for the PCI devices
> behind device-tree based PCI Host controller, but with one modification.
> Unlike for platform devices, we cannot use generic IOMMU bindings
>
On Fri, 21 Oct 2022, Andrew Cooper wrote:
> On 21/10/2022 17:53, Michal Orzel wrote:
> > Null scheduler is not enabled on non-debug Xen builds so the current
> > test can lead to a failure on such jobs. We still want to test that we
> > can assign the cpupool to a domU with a different scheduler
On Fri, 21 Oct 2022, Michal Orzel wrote:
> All the build jobs exist in two flavors: debug and non-debug, where the
> former sets 'debug' variable to 'y' and the latter to 'n'. This variable
> is only being recognized by the toolstack, because Xen requires
> enabling/disabling debug build via e.g.
On 20/10/2022 11:27, Roger Pau Monne wrote:
> CONFIG_HAS_PCI is not defined for the tools build, and as a result the
> vpci harness would never get build. Fix this by building it
> unconditionally, there's nothing arch specific in it.
>
> Reported-by: Andrew Cooper
> Signed-off-by: Roger Pau
Hi Carlo,
This patch seems to be missing the tools maintainers/reviewers. I have
added them now.
I am not sure what you are to generate the CCs. If you are not aware, we
have a script that will add the correct maintainers/reviewers for each
patch. The script is called
Hi,
On 26/08/2022 13:51, Carlo Nonato wrote:
#endif /* !__ASM_ARM_COLORING_H__ */
diff --git a/xen/arch/arm/include/asm/domain.h
b/xen/arch/arm/include/asm/domain.h
index 26a8348eed..291f7c375d 100644
--- a/xen/arch/arm/include/asm/domain.h
+++ b/xen/arch/arm/include/asm/domain.h
@@ -58,6
Hi Carlo,
On 26/08/2022 13:51, Carlo Nonato wrote:
This commit adds array pointers to domains as well as to the hypercall
and configuration structure employed in domain creation. The latter is used
both by the toolstack and by Xen itself to pass configuration data to the
domain creation
flight 174140 xen-4.16-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174140/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-xl-seattle 14 guest-start fail REGR. vs. 172623
On 26/09/2022 07:39, Wei Chen wrote:
On 2022/8/26 20:51, Carlo Nonato wrote:
This commit adds array pointers to domains as well as to the hypercall
and configuration structure employed in domain creation. The latter is
used
both by the toolstack and by Xen itself to pass configuration
From: Oleksandr Tyshchenko
Use the same "xen-grant-dma" device concept for the PCI devices
behind device-tree based PCI Host controller, but with one modification.
Unlike for platform devices, we cannot use generic IOMMU bindings
(iommus property), as we need to support more flexible
On 21/10/2022 17:53, Michal Orzel wrote:
> Null scheduler is not enabled on non-debug Xen builds so the current
> test can lead to a failure on such jobs. We still want to test that we
> can assign the cpupool to a domU with a different scheduler than default
> one (credit2). Switch to credit as
Hi Carlo,
On 26/08/2022 13:51, Carlo Nonato wrote:
This commit adds the cache coloring support initialization, Kconfig options,
command line parameters and the initial documentation.
The initialization consists of an auto probing of the cache layout
necessary to retrieve the LLC way size which
Null scheduler is not enabled on non-debug Xen builds so the current
test can lead to a failure on such jobs. We still want to test that we
can assign the cpupool to a domU with a different scheduler than default
one (credit2). Switch to credit as it is enabled by default.
Fixes: 36e3f4158778
On 12/09/2022 14:54, Carlo Nonato wrote:
Hi Julien,
Hi Carlo,
On Sat, Sep 10, 2022 at 4:01 PM Julien Grall wrote: > Do you
have any suggestions? Is it ok to add the print to this very patch
explaining why I added that (since it would edit the clean revert)?
I would consider to the call
flight 174165 xen-unstable real [real]
flight 174205 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/174165/
http://logs.test-lab.xenproject.org/osstest/logs/174205/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
On 21/10/2022 16:32, Michal Orzel wrote:
>
>
> Hi Andrew,
>
> On 21/10/2022 15:31, Andrew Cooper wrote:
>>
>>
>> On 21/10/2022 14:22, Michal Orzel wrote:
>>> All the build jobs exist in two flavors: debug and non-debug, where the
>>> former sets 'debug' variable to 'y' and the latter to 'n'.
branch xen-4.16-testing
xenbranch xen-4.16-testing
job test-armhf-armhf-xl-multivcpu
testid guest-start
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemuu
flight 174155 qemu-mainline real [real]
flight 174206 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/174155/
http://logs.test-lab.xenproject.org/osstest/logs/174206/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
flight 174201 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174201/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
"unsigned long long" is defined as 64 bits on AArch64 and AArch32
Thus, one should this instead of "unsigned long" which is 32 bits
on AArch32.
Also use 'PRIu64' instead of 'lx' to print uint64_t.
Signed-off-by: Ayan Kumar Halder
---
xen/arch/arm/gic-v3-its.c | 20
Refer ARM DDI 0487G.b ID072021,
D13.2.86 -
ID_PFR1_EL1, AArch32 Processor Feature Register 1
GIC, bits[31:28] == 0b0001 for GIC3.0 on Aarch32
One can now enable GICv3 on AArch32 systems.
Signed-off-by: Ayan Kumar Halder
---
xen/arch/arm/Kconfig | 2 +-
Refer "Arm IHI 0069H ID020922",
12.7.1 - Interrupt Controller Hyp Active Priorities Group0 Registers 0-3
12.7.2 - Interrupt Controller Hyp Active Priorities Group1 Registers 0-3
Signed-off-by: Ayan Kumar Halder
---
xen/arch/arm/include/asm/arm32/sysregs.h | 12
1 file changed, 12
Defined readq_relaxed()/writeq_relaxed() to read and write 64 bit regs.
This in turn calls readl_relaxed()/writel_relaxed() twice for the lower
and upper 32 bits.
Signed-off-by: Ayan Kumar Halder
---
xen/arch/arm/include/asm/arm32/io.h | 4
1 file changed, 4 insertions(+)
diff --git
Refer "Arm IHI 0069H ID020922"
12.5.23 ICC_SGI1R, Interrupt Controller Software Generated Interrupt
Group 1 Register
12.5.12 ICC_HSRE, Interrupt Controller Hyp System Register Enable register
12.7.10 ICH_VTR, Interrupt Controller VGIC Type Register
12.7.5 ICH_HCR, Interrupt Controller Hyp Control
Refer "Arm IHI 0069H ID020922", 12.4.6, Interrupt Controller List Registers
AArch64 System register ICH_LR_EL2 bits [31:0] are architecturally
mapped to AArch32 System register ICH_LR[31:0].
AArch64 System register ICH_LR_EL2 bits [63:32] are architecturally
mapped to AArch32 System register
'unsigned long long' is defined as 64 bit across both aarch32 and aarch64.
So, use 'ULL' for 64 bit word instead of UL which is 32 bits for aarch32.
GICR_PENDBASER and GICR_PROPBASER both are 64 bit registers.
Signed-off-by: Ayan Kumar Halder
---
xen/arch/arm/include/asm/gic_v3_defs.h | 16
Refer Arm IHI 0069H ID020922,
The upper 32 bits of GICR_TYPER represent the affinity
whereas the lower 32 bits represent the other bits (eg processor
number, etc).
MPIDR_AFFINITY_LEVEL() returns a 32 bit number on aarch32. Thus, this
is appended to return GICR_TYPER register.
Signed-off-by: Ayan
Refer Arm IHI 0069H ID020922, 12.5.23, ICC_SGI1R is a 64 bit register on
Aarch32 systems. Thus, the prototype needs to change to reflect this.
Signed-off-by: Ayan Kumar Halder
---
xen/arch/arm/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/arm/vgic-v3.c
In some situations (eg GICR_TYPER), the hypervior may need to emulate
64bit registers in aarch32 mode. In such situations, the hypervisor may
need to read/modify the lower or upper 32 bits of the 64 bit register.
In aarch32, 64 bit is represented by unsigned long long. Thus, we need
to change the
Hi All,
Please find the following patches to enable GICv3 for AArch32.
This is a pre-requisite to support Xen on Cortex-R52 (AArch32-v8R system)
Let me know your thoughts.
Ayan Kumar Halder (12):
Arm: GICv3: Sysreg emulation is applicable for Aarch64 only
Arm: GICv3: Move the macros to
Refer ARM DDI 0487G.b ID072021, EC==0b011000 is supported for Aarch64 state
only. This is when MSR, MRS, System instruction execution in AArch64 state
is trapped, that is not reported using EC 0b00, 0b01 or 0b000111.
Signed-off-by: Ayan Kumar Halder
---
xen/arch/arm/vgic-v3.c | 4
Refer https://elixir.bootlin.com/linux/v6.1-rc1/source/arch/arm64/ \
include/asm/cputype.h#L14 , these macros are specific for arm64.
When one computes MPIDR_LEVEL_SHIFT(3), it crosses the width of a 32
bit register.
Refer https://elixir.bootlin.com/linux/v6.1-rc1/source/arch/arm/include/ \
Hi,
> On 21 Oct 2022, at 15:40, Henry Wang wrote:
>
> (+ Arm maintainers)
>
> Hi Oleksandr,
>
>> -Original Message-
>> From: Oleksandr
>> Subject: Re: [PATCH v2 4/4] vpci: include xen/vmap.h to fix build on ARM
>> Hello all.
>> On 19.07.22 13:40, Jan Beulich wrote:
>>> On 19.07.2022
Today all timers are migrated to cpu 0 when the system is being
suspended. They are not migrated back after resuming the system again.
This results (at least) to problems with the credit scheduler, as the
timer isn't handled on the cpu it was expected to occur.
Add migrating the scheduling
(+ Arm maintainers)
Hi Oleksandr,
> -Original Message-
> From: Oleksandr
> Subject: Re: [PATCH v2 4/4] vpci: include xen/vmap.h to fix build on ARM
> Hello all.
> On 19.07.22 13:40, Jan Beulich wrote:
> > On 19.07.2022 12:32, Volodymyr Babchuk wrote:
> >> Jan Beulich writes:
> >>
> >>>
Hello all.
On 19.07.22 13:40, Jan Beulich wrote:
On 19.07.2022 12:32, Volodymyr Babchuk wrote:
Jan Beulich writes:
On 18.07.2022 23:15, Volodymyr Babchuk wrote:
Patch b4f211606011 ("vpci/msix: fix PBA accesses") introduced call to
iounmap(), but not added corresponding include.
Fixes:
Hi Andrew,
On 21/10/2022 15:31, Andrew Cooper wrote:
>
>
> On 21/10/2022 14:22, Michal Orzel wrote:
>> All the build jobs exist in two flavors: debug and non-debug, where the
>> former sets 'debug' variable to 'y' and the latter to 'n'. This variable
>> is only being recognized by the
Hi Michal,
> -Original Message-
> From: Michal Orzel
> Subject: [for-4.17] automation: Build Xen according to the type of the job
>
> All the build jobs exist in two flavors: debug and non-debug, where the
> former sets 'debug' variable to 'y' and the latter to 'n'. This variable
> is
On 21/10/2022 14:22, Michal Orzel wrote:
> All the build jobs exist in two flavors: debug and non-debug, where the
> former sets 'debug' variable to 'y' and the latter to 'n'. This variable
> is only being recognized by the toolstack, because Xen requires
> enabling/disabling debug build via e.g.
All the build jobs exist in two flavors: debug and non-debug, where the
former sets 'debug' variable to 'y' and the latter to 'n'. This variable
is only being recognized by the toolstack, because Xen requires
enabling/disabling debug build via e.g. menuconfig/config file.
As a corollary, we end up
On 21/10/22 13:31, Markus Armbruster wrote:
Laurent Vivier writes:
On 10/21/22 12:35, Markus Armbruster wrote:
Philippe Mathieu-Daudé writes:
On 21/10/22 11:09, Laurent Vivier wrote:
Use QIOChannel, QIOChannelSocket and QIONetListener.
This allows net/stream to use all the available
flight 174134 xen-4.14-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174134/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-credit2 broken in 173725
test-arm64-arm64-xl-vhd
flight 174192 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174192/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
flight 174136 qemu-upstream-4.16-testing real [real]
flight 174191 qemu-upstream-4.16-testing real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/174136/
http://logs.test-lab.xenproject.org/osstest/logs/174191/
Failures :-/ but no regressions.
Tests which are failing
Laurent Vivier writes:
> Copied from socket netdev file and modified to use SocketAddress
> to be able to introduce new features like unix socket.
>
> index eb38e5dc40bc..396c1d11e1e2 100644
> --- a/qemu-options.hx
> +++ b/qemu-options.hx
> @@ -2772,6 +2772,18 @@ DEF("netdev", HAS_ARG,
Laurent Vivier writes:
> On 10/21/22 12:35, Markus Armbruster wrote:
>> Philippe Mathieu-Daudé writes:
>>
>>> On 21/10/22 11:09, Laurent Vivier wrote:
Use QIOChannel, QIOChannelSocket and QIONetListener.
This allows net/stream to use all the available parameters provided by
On 21/10/22 11:09, Laurent Vivier wrote:
Signed-off-by: Laurent Vivier
Reviewed-by: Stefano Brivio
Reviewed-by: David Gibson
Acked-by: Michael S. Tsirkin
Acked-by: Markus Armbruster (QAPI schema)
---
net/dgram.c | 55 -
qapi/net.json
On 21/10/2022 11:50, Juergen Gross wrote:
> When the system is coming up after having been suspended,
> restore_vcpu_affinity() is called for each domain in order to adjust
> the vcpu's affinity settings in case a cpu didn't come to live again.
>
> The way restore_vcpu_affinity() is doing that is
Stefano Brivio writes:
> [Cc: Laine, full quote]
>
> On Fri, 21 Oct 2022 11:12:20 +0200
> Markus Armbruster wrote:
>
>> Cc: Stefano Brivio
>>
>> Laurent Vivier writes:
>>
>> > On 10/21/22 07:48, Markus Armbruster wrote:
>> >> Laurent Vivier writes:
>> >>
>> >>> The netdev reports
When the system is coming up after having been suspended,
restore_vcpu_affinity() is called for each domain in order to adjust
the vcpu's affinity settings in case a cpu didn't come to live again.
The way restore_vcpu_affinity() is doing that is wrong, because the
specific scheduler isn't being
On Fri, Oct 21, 2022 at 08:58:06AM +0200, Juergen Gross wrote:
> When the system is coming up after having been suspended,
> restore_vcpu_affinity() is called for each domain in order to adjust
> the vcpu's affinity settings in case a cpu didn't come to live again.
>
> The way
Hi Stefano and all,
On Mon, Oct 17, 2022 at 04:50:05PM -0700, Stefano Stabellini wrote:
[...]
> > We can see DomU sends notification with timestamp (raw counter) is
> > 4989078592 and Dom0 receives the interrupt with timestamp 4989092169.
> > Since Dom0 and DomU use the same time counter and
On 10/21/22 12:35, Markus Armbruster wrote:
Philippe Mathieu-Daudé writes:
On 21/10/22 11:09, Laurent Vivier wrote:
Use QIOChannel, QIOChannelSocket and QIONetListener.
This allows net/stream to use all the available parameters provided by
SocketAddress.
Signed-off-by: Laurent Vivier
On 21.10.22 12:37, Jan Beulich wrote:
On 21.10.2022 08:58, Juergen Gross wrote:
--- a/xen/common/sched/core.c
+++ b/xen/common/sched/core.c
@@ -1196,76 +1196,6 @@ static void sched_reset_affinity_broken(const struct
sched_unit *unit)
v->affinity_broken = false;
}
My pre-push
Instead of directly falling back to the idle unit in case the top
unit from the run queue happened to be not runnable, consult the run
queue again.
Suggested-by: Dario Faggioli
Signed-off-by: Juergen Gross
---
xen/common/sched/rt.c | 17 +++--
1 file changed, 11 insertions(+), 6
On 21.10.2022 08:58, Juergen Gross wrote:
> --- a/xen/common/sched/core.c
> +++ b/xen/common/sched/core.c
> @@ -1196,76 +1196,6 @@ static void sched_reset_affinity_broken(const struct
> sched_unit *unit)
> v->affinity_broken = false;
> }
My pre-push build test failed because the
Philippe Mathieu-Daudé writes:
> On 21/10/22 11:09, Laurent Vivier wrote:
>> Use QIOChannel, QIOChannelSocket and QIONetListener.
>> This allows net/stream to use all the available parameters provided by
>> SocketAddress.
>> Signed-off-by: Laurent Vivier
>> Acked-by: Michael S. Tsirkin
>> ---
Hi
On Fri, Oct 21, 2022 at 2:03 PM Laurent Vivier wrote:
> Rename SocketAddress_to_str() to socket_uri() and move it to
> util/qemu-sockets.c close to socket_parse().
>
> socket_uri() generates a string from a SocketAddress while
> socket_parse() generates a SocketAddress from a string.
>
Tbh,
On 21/10/22 11:09, Laurent Vivier wrote:
Rename SocketAddress_to_str() to socket_uri() and move it to
util/qemu-sockets.c close to socket_parse().
socket_uri() generates a string from a SocketAddress while
socket_parse() generates a SocketAddress from a string.
Signed-off-by: Laurent Vivier
On 21/10/2022 02:42, Henry Wang wrote:
Hi Julien and Xenia,
Hi Henry,
-Original Message-
From: Julien Grall
; Henry Wang
Subject: Re: [PATCH v2] xen/arm: p2m: fix pa_range_info for 52-bit pa range
(+ Henry)
Hi Xenia,
On 19/10/2022 15:49, Xenia Ragiadakou wrote:
Currently,
On 21.10.22 11:37, Dario Faggioli wrote:
Ok, and now, something not really related to the bug being fixed here,
but about the code that is being touched:
On Fri, 2022-10-21 at 08:10 +0200, Juergen Gross wrote:
diff --git a/xen/common/sched/rt.c b/xen/common/sched/rt.c
index
On 20/10/2022 19:56, Julien Grall wrote:
On 20/10/2022 19:53, Stewart Hildebrand wrote:
On 10/20/22 14:19, Julien Grall wrote:
Hi Stewart,
Hi Julien,
I nearly missed this one because it was threaded under v1. In the
future, would you be able to send new version in a separate thread?
On 21/10/22 11:09, Laurent Vivier wrote:
Use QIOChannel, QIOChannelSocket and QIONetListener.
This allows net/stream to use all the available parameters provided by
SocketAddress.
Signed-off-by: Laurent Vivier
Acked-by: Michael S. Tsirkin
---
net/stream.c| 492
On Fri, 2022-10-07 at 13:17 +0200, Juergen Gross wrote:
> On 07.10.22 12:32, Mykyta Poturai wrote:
> >
> > Signed-off-by: Juergen Gross
>
> I can't remember having written this patch. The one I remember was
> for
> x86.
>
> > Reviewed-by: Dario Faggioli
>
> I doubt that, reasoning see above.
[Cc: Laine, full quote]
On Fri, 21 Oct 2022 11:12:20 +0200
Markus Armbruster wrote:
> Cc: Stefano Brivio
>
> Laurent Vivier writes:
>
> > On 10/21/22 07:48, Markus Armbruster wrote:
> >> Laurent Vivier writes:
> >>
> >>> The netdev reports NETDEV_STREAM_CONNECTED event when the backend
Laurent Vivier writes:
> On 10/21/22 11:12, Markus Armbruster wrote:
>> Cc: Stefano Brivio
>>
>> Laurent Vivier writes:
>>
>>> On 10/21/22 07:48, Markus Armbruster wrote:
Laurent Vivier writes:
> The netdev reports NETDEV_STREAM_CONNECTED event when the backend
> is
Ok, and now, something not really related to the bug being fixed here,
but about the code that is being touched:
On Fri, 2022-10-21 at 08:10 +0200, Juergen Gross wrote:
> diff --git a/xen/common/sched/rt.c b/xen/common/sched/rt.c
> index d6de25531b..960a8033e2 100644
> --- a/xen/common/sched/rt.c
On 10/21/22 11:12, Markus Armbruster wrote:
Cc: Stefano Brivio
Laurent Vivier writes:
On 10/21/22 07:48, Markus Armbruster wrote:
Laurent Vivier writes:
The netdev reports NETDEV_STREAM_CONNECTED event when the backend
is connected, and NETDEV_STREAM_DISCONNECTED when it is disconnected.
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-6.1-rc2-tag
xen: branch for v6.1-rc2
It contains just 2 fixes for the new "virtio with grants" feature.
Thanks.
Juergen
drivers/xen/grant-dma-ops.c | 27
On Fri, 2022-10-21 at 08:10 +0200, Juergen Gross wrote:
> When a domain gets paused the unit runnable state can change to "not
> runnable" without the scheduling lock being involved. This means that
> a specific scheduler isn't involved in this change of runnable state.
>
> In the RTDS scheduler
Hi,
We got the following report in Debian after an update from 5.10.140 to
the current 5.10.149. Full quoting below (from
https://bugs.debian.org/1022126). Does this ring some bell about known
regressions?
On Thu, Oct 20, 2022 at 05:21:03PM +0200, Adi Kriegisch wrote:
> Package:
Hi Juergen,
> -Original Message-
> From: Juergen Gross
> Subject: [PATCH-for-4.17] xen/sched: fix restore_vcpu_affinity() by removing
> it
>
> When the system is coming up after having been suspended,
> restore_vcpu_affinity() is called for each domain in order to adjust
> the vcpu's
On Fri, 2022-10-21 at 09:06 +0200, Juergen Gross wrote:
> On 21.10.22 08:58, Juergen Gross wrote:
> > When the system is coming up after having been suspended,
> > restore_vcpu_affinity() is called for each domain in order to
> > adjust
> > the vcpu's affinity settings in case a cpu didn't come to
Cc: Stefano Brivio
Laurent Vivier writes:
> On 10/21/22 07:48, Markus Armbruster wrote:
>> Laurent Vivier writes:
>>
>>> The netdev reports NETDEV_STREAM_CONNECTED event when the backend
>>> is connected, and NETDEV_STREAM_DISCONNECTED when it is disconnected.
>>
>> Use cases?
>
> This is
On 10/21/22 08:50, Jason Wang wrote:
On Fri, Oct 21, 2022 at 2:46 PM Markus Armbruster wrote:
Jason Wang writes:
I've queued this version and will send pull requests shortly.
Any future comment we can do patches on top.
Please give Laurent and me a few hours to try to improve PATCH 17's
flight 174119 xen-4.15-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174119/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-xl-seattle 14 guest-start fail REGR. vs. 172547
On 21.10.22 10:06, Andrew Cooper wrote:
On 20/10/2022 12:39, Borislav Petkov wrote:
On Thu, Oct 20, 2022 at 01:36:19PM +0200, Juergen Gross wrote:
xen_enable_sysenter() and xen_enable_syscall() can be simplified a lot.
Signed-off-by: Juergen Gross
---
arch/x86/xen/setup.c | 23
On 10/21/22 07:48, Markus Armbruster wrote:
Laurent Vivier writes:
The netdev reports NETDEV_STREAM_CONNECTED event when the backend
is connected, and NETDEV_STREAM_DISCONNECTED when it is disconnected.
Use cases?
This is asked by Stefano Brivio to allow libvirt to detect if connection to
On 20/10/2022 12:39, Borislav Petkov wrote:
> On Thu, Oct 20, 2022 at 01:36:19PM +0200, Juergen Gross wrote:
>> xen_enable_sysenter() and xen_enable_syscall() can be simplified a lot.
>>
>> Signed-off-by: Juergen Gross
>> ---
>> arch/x86/xen/setup.c | 23 ++-
>> 1 file
> On 21 Oct 2022, at 08:50, Christian Lindig
> wrote:
>
>
>
>> On 20 Oct 2022, at 17:54, Edwin Török wrote:
>>
>> During live update we will load the /tool/xenstored path from the previous
>> binary,
>> and then try to mkdir /tool again which will fail with EEXIST.
>> Check for existence
During live update we will load the /tool/xenstored path from the previous
binary,
and then try to mkdir /tool again which will fail with EEXIST.
Check for existence of the path before creating it.
The write call to /tool/xenstored should not need any changes
(and we do want to overwrite any
> On 20 Oct 2022, at 17:54, Edwin Török wrote:
>
> During live update we will load the /tool/xenstored path from the previous
> binary,
> and then try to mkdir /tool again which will fail with EEXIST.
> Check for existence of the path before creating it.
>
> The write call to /tool/xenstored
On 20 Oct 2022, at 17:56, Edwin Torok
mailto:edvin.to...@citrix.com>> wrote:
Further testing has revealed another bug, patch here:
https://lore.kernel.org/xen-devel/12d90632bf881e96e0b6c256df193f00df187dc1.1666284745.git.edvin.to...@citrix.com/T/#u
For convenience the commit is also available
On 21.10.22 08:58, Juergen Gross wrote:
When the system is coming up after having been suspended,
restore_vcpu_affinity() is called for each domain in order to adjust
the vcpu's affinity settings in case a cpu didn't come to live again.
The way restore_vcpu_affinity() is doing that is wrong,
When the system is coming up after having been suspended,
restore_vcpu_affinity() is called for each domain in order to adjust
the vcpu's affinity settings in case a cpu didn't come to live again.
The way restore_vcpu_affinity() is doing that is wrong, because the
specific scheduler isn't being
On Fri, Oct 21, 2022 at 2:46 PM Markus Armbruster wrote:
>
> Jason Wang writes:
>
> > I've queued this version and will send pull requests shortly.
> >
> > Any future comment we can do patches on top.
>
> Please give Laurent and me a few hours to try to improve PATCH 17's
> commit message.
On Thu, Oct 20, 2022 at 10:22:17AM -0400, Boris Ostrovsky wrote:
>
> On 10/20/22 9:34 AM, Juergen Gross wrote:
> > On 20.10.22 15:16, Jan Beulich wrote:
> > > On 20.10.2022 13:37, Juergen Gross wrote:
> > > > Commit 8714f7bcd3c2 ("xen/pv: add fault recovery control to pmu msr
> > > > accesses")
1 - 100 of 106 matches
Mail list logo
