On Tue, Jan 23, 2024 at 11:44:03AM +0100, Jan Beulich wrote:
> On 22.01.2024 21:53, Elliott Mitchell wrote:
>
> > I find the present handling of MCE in Xen an odd choice. Having Xen do
> > most of the handling of MCE events is a behavior matching a traditional
> > stand-alone hypervisor. Yet
On Sun, 14 Jan 2024, Mykyta Poturai wrote:
> Add the second version of inject_msi DM op, which allows to specify
> the source_id of an MSI interrupt. This is needed for correct MSI
> injection on ARM.
>
> It would not be safe to include the source_id in the original inject_msi
> in the pad field,
On Tue, Jan 23, 2024 at 08:55:44AM +0100, Jan Beulich wrote:
> On 23.01.2024 01:27, Kees Cook wrote:
> > --- a/drivers/net/xen-netback/hash.c
> > +++ b/drivers/net/xen-netback/hash.c
> > @@ -345,7 +345,7 @@ u32 xenvif_set_hash_mapping(struct xenvif *vif, u32
> > gref, u32 len,
> >
From: Peng Fan
xen_invalidate_map_cache_entry is not expected to run in a
coroutine. Without this, there is crash:
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
threadid=) at pthread_kill.c:78
at /usr/src/debug/glibc/2.38+git-r0/sysdeps/posix/raise.c:26
On Sun, 14 Jan 2024, Mykyta Poturai wrote:
> Add the vgic_its_trigger_msi() function to the vgic interface. This
> function allows to inject MSIs from the Hypervisor to the guest.
> Which is useful for userspace PCI backend drivers.
>
> Signed-off-by: Mykyta Poturai
> ---
>
flight 184438 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/184438/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf d97f3a1d80fc4880da9726d9a5d7504d3c31da70
baseline version:
ovmf
flight 184440 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/184440/
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
flight 184432 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/184432/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 184427
test-amd64-amd64-xl-qemut-win7-amd64
Always run microcode_update_helper() on the BSP, so the the updated Raw CPU
policy doesn't get non-BSP topology details included.
Have calculate_raw_cpu_policy() clear the instantanious XSTATE sizes. The
value XCR0 | MSR_XSS had when we scanned the policy isn't terribly interesting
to report.
On Tue, 23 Jan 2024, Jan Beulich wrote:
> On 22.01.2024 23:47, Stefano Stabellini wrote:
> > On Mon, 22 Jan 2024, Jan Beulich wrote:
> >> What definitely needs clarifying is what "review" is: Are R-b tags
> >> counted, or is it the number of replies sent commenting on patches?
> >
> > Yes, I
On Sat, Jan 20, 2024 at 8:33 PM Patrick Plenefisch
wrote:
>
>
> On Fri, Jan 19, 2024 at 6:06 AM Roger Pau Monné
> wrote:
>
>> On Fri, Jan 19, 2024 at 02:44:35AM -0500, Patrick Plenefisch wrote:
>> > On Thu, Jan 18, 2024 at 7:41 AM Roger Pau Monné
>> > wrote:
>> >
>> > >
>> > > From that
Hi Jan, Andrew,
I managed to get back to read the mailing list and noticed this patch.
Is it still relevant and needs to be reviewed?
Are there any outstanding disagreements between maintainers on the
approach to take here? Or should I just go ahead and review it?
On Tue, 9 Jan 2024, Jan
flight 184442 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/184442/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 7f72c2829fa29d2b4451c9a60e904df4c6a5df6c
baseline version:
ovmf
flight 184441 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/184441/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 417ebe6d1d6052b6cf023332da07558363d7fd08
baseline version:
ovmf
On Wed, 24 Jan 2024, Peng Fan (OSS) wrote:
> From: Peng Fan
>
> xen_invalidate_map_cache_entry is not expected to run in a
> coroutine. Without this, there is crash:
>
> signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
> threadid=) at pthread_kill.c:78
> at
On Tue, 16 Jan 2024, Peng Fan (OSS) wrote:
> From: Peng Fan
>
> xen_invalidate_map_cache_entry is not expected to run in a
> coroutine. Without this, there is crash:
>
> signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
> threadid=) at pthread_kill.c:78
> at
flight 18 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/18/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 1063665fa5466ece0814a3e764ee3382656956a1
baseline version:
ovmf
On 1/23/24 09:29, Jan Beulich wrote:
> On 15.01.2024 20:43, Stewart Hildebrand wrote:
>> @@ -1043,11 +1043,11 @@ static int __pci_enable_msix(struct pci_dev *pdev,
>> struct msi_info *msi,
>> {
>> struct msi_desc *old_desc;
>>
>> -ASSERT(pcidevs_locked());
>> -
>> if ( !pdev ||
On 23.01.2024 23:52, Elliott Mitchell wrote:
> On Tue, Jan 23, 2024 at 11:44:03AM +0100, Jan Beulich wrote:
>> On 22.01.2024 21:53, Elliott Mitchell wrote:
>>
>>> I find the present handling of MCE in Xen an odd choice. Having Xen do
>>> most of the handling of MCE events is a behavior matching a
On 1/23/24 10:07, Roger Pau Monné wrote:
> On Tue, Jan 23, 2024 at 03:32:12PM +0100, Jan Beulich wrote:
>> On 15.01.2024 20:43, Stewart Hildebrand wrote:
>>> @@ -2888,6 +2888,8 @@ int allocate_and_map_msi_pirq(struct domain *d, int
>>> index, int *pirq_p,
>>> {
>>> int irq, pirq, ret;
>>>
On 24.01.2024 02:34, Stefano Stabellini wrote:
> I managed to get back to read the mailing list and noticed this patch.
>
> Is it still relevant and needs to be reviewed?
>
> Are there any outstanding disagreements between maintainers on the
> approach to take here? Or should I just go ahead
On Mon, 2024-01-22 at 17:27 +0100, Jan Beulich wrote:
> On 22.12.2023 16:12, Oleksii Kurochko wrote:
> > --- /dev/null
> > +++ b/xen/arch/riscv/include/asm/cmpxchg.h
> > @@ -0,0 +1,496 @@
> > +/* SPDX-License-Identifier: GPL-2.0-only */
> > +/* Copyright (C) 2014 Regents of the University of
On 22.01.2024 20:09, Jason Andryuk wrote:
> When HWP is active, the cpufreq P-state information is not updated. In
> that case, return -ENODEV instead of bogus, incomplete info. The xenpm
> command already supports skipping results when -ENODEV is returned, so
> it is re-used when -EOPNOTSUPP
On 22.01.2024 19:17, Andrew Cooper wrote:
> handle_ist_exception isn't part of the NMI handler, just like handle_exception
> isn't part of #PF.
>
> Fixes: b3a9037550df ("x86: annotate entry points with type and size")
> Signed-off-by: Andrew Cooper
Reviewed-by: Jan Beulich
It's a matter of
On Tue, Jan 23, 2024 at 08:53:15AM +0100, Jan Beulich wrote:
> On 22.01.2024 18:27, Roger Pau Monné wrote:
> > On Mon, Jan 22, 2024 at 12:21:47PM +0100, Jan Beulich wrote:
> >> On 22.01.2024 12:02, Roger Pau Monne wrote:
> >>> --- a/xen/arch/x86/xen.lds.S
> >>> +++ b/xen/arch/x86/xen.lds.S
> >>>
On 2024/1/23 07:37, Bjorn Helgaas wrote:
> On Fri, Jan 05, 2024 at 02:22:17PM +0800, Jiqian Chen wrote:
>> There is a need for some scenarios to use gsi sysfs.
>> For example, when xen passthrough a device to dumU, it will
>> use gsi to map pirq, but currently userspace can't get gsi
>> number.
>>
Hi,
will try to explain some of the messages here after but I am not sure of the
reason
of the crash so I will just set some pointers...
> On 22 Jan 2024, at 11:46, George Dunlap wrote:
>
> On Fri, Jan 19, 2024 at 8:32 PM Elliott Mitchell wrote:
>>
>> On Sun, Jan 14, 2024 at 10:54:24PM
On 22.01.2024 19:17, Andrew Cooper wrote:
> It is bad form to have inter-function fallthrough. It only functions right
> now because alignment padding bytes are NOPs.
But that's a requirement anyway in executable sections.
> --- a/xen/arch/x86/x86_64/compat/entry.S
> +++
On 22.01.2024 19:17, Andrew Cooper wrote:
> Each of these symbols are local to their main function. By not having them
> globally visible, livepatch's binary diffing logic can reason about the
> functions properly.
I'm not happy with this, and not only because of the way you're putting
things:
On 23.01.2024 10:32, Roger Pau Monné wrote:
> On Tue, Jan 23, 2024 at 08:53:15AM +0100, Jan Beulich wrote:
>> On 22.01.2024 18:27, Roger Pau Monné wrote:
>>> On Mon, Jan 22, 2024 at 12:21:47PM +0100, Jan Beulich wrote:
I'm further curious why .text.__x86_indirect_thunk_* is left past the
On 23.01.2024 13:24, Oleksii wrote:
> On Tue, 2024-01-23 at 11:30 +0100, Jan Beulich wrote:
>> On 23.01.2024 11:21, Oleksii wrote:
>>> On Mon, 2024-01-22 at 17:56 +0100, Jan Beulich wrote:
On 22.12.2023 16:12, Oleksii Kurochko wrote:
> --- /dev/null
> +++
On 23.01.2024 13:34, Oleksii wrote:
> On Tue, 2024-01-23 at 12:14 +0100, Jan Beulich wrote:
>> On 22.12.2023 16:13, Oleksii Kurochko wrote:
>>> --- a/xen/common/Kconfig
>>> +++ b/xen/common/Kconfig
>>> @@ -47,6 +47,9 @@ config ARCH_MAP_DOMAIN_PAGE
>>> config GENERIC_BUG_FRAME
>>> bool
>>>
On Tue, Jan 23, 2024 at 10:22:10AM +0100, Jan Beulich wrote:
> On 22.01.2024 19:17, Andrew Cooper wrote:
> > It is bad form to have inter-function fallthrough. It only functions right
> > now because alignment padding bytes are NOPs.
>
> But that's a requirement anyway in executable sections.
On Tue, Jan 23, 2024 at 03:26:26PM +0100, Jan Beulich wrote:
> On 15.01.2024 20:43, Stewart Hildebrand wrote:
> > --- a/xen/arch/x86/hvm/vmsi.c
> > +++ b/xen/arch/x86/hvm/vmsi.c
> > @@ -468,7 +468,7 @@ int msixtbl_pt_register(struct domain *d, struct pirq
> > *pirq, uint64_t gtable)
> >
On 22.12.2023 16:13, Oleksii Kurochko wrote:
> --- a/xen/arch/riscv/early_printk.c
> +++ b/xen/arch/riscv/early_printk.c
> @@ -40,171 +40,3 @@ void early_printk(const char *str)
> str++;
> }
> }
> -
> -/*
> - * The following #if 1 ... #endif should be removed after printk
> - * and
On 23.01.2024 13:18, Oleksii wrote:
> On Tue, 2024-01-23 at 11:28 +0100, Jan Beulich wrote:
>> On 23.01.2024 11:15, Oleksii wrote:
>>> On Mon, 2024-01-22 at 17:27 +0100, Jan Beulich wrote:
On 22.12.2023 16:12, Oleksii Kurochko wrote:
> +static inline unsigned long __xchg(volatile void
On 23.01.2024 14:37, Roger Pau Monné wrote:
> On Tue, Jan 23, 2024 at 10:22:10AM +0100, Jan Beulich wrote:
>> On 22.01.2024 19:17, Andrew Cooper wrote:
>>> It is bad form to have inter-function fallthrough. It only functions right
>>> now because alignment padding bytes are NOPs.
>>
>> But that's
On 15.01.2024 20:43, Stewart Hildebrand wrote:
> --- a/xen/arch/x86/hvm/vmsi.c
> +++ b/xen/arch/x86/hvm/vmsi.c
> @@ -468,7 +468,7 @@ int msixtbl_pt_register(struct domain *d, struct pirq
> *pirq, uint64_t gtable)
> struct msixtbl_entry *entry, *new_entry;
> int r = -EINVAL;
>
> -
On 15.01.2024 20:43, Stewart Hildebrand wrote:
> @@ -1043,11 +1043,11 @@ static int __pci_enable_msix(struct pci_dev *pdev,
> struct msi_info *msi,
> {
> struct msi_desc *old_desc;
>
> -ASSERT(pcidevs_locked());
> -
> if ( !pdev || !pdev->msix )
> return -ENODEV;
>
> +
flight 184433 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/184433/
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
On 09.01.2024 22:51, Stewart Hildebrand wrote:
> From: Oleksandr Andrushchenko
>
> When a PCI device gets assigned/de-assigned we need to
> initialize/de-initialize vPCI state for the device.
>
> Also, rename vpci_add_handlers() to vpci_assign_device() and
> vpci_remove_device() to
On Tue, 2024-01-23 at 12:22 +0100, Jan Beulich wrote:
> On 22.12.2023 16:13, Oleksii Kurochko wrote:
> > Signed-off-by: Oleksii Kurochko
> > ---
> > Changes in V3:
> > - new patch
> > ---
> > README | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/README b/README
> > index
On 15.01.2024 20:43, Stewart Hildebrand wrote:
> @@ -2888,6 +2888,8 @@ int allocate_and_map_msi_pirq(struct domain *d, int
> index, int *pirq_p,
> {
> int irq, pirq, ret;
>
> +ASSERT(pcidevs_locked() || rw_is_locked(>pci_lock));
If either lock is sufficient to hold here, ...
> ---
On Tue, Jan 23, 2024 at 03:32:12PM +0100, Jan Beulich wrote:
> On 15.01.2024 20:43, Stewart Hildebrand wrote:
> > @@ -2888,6 +2888,8 @@ int allocate_and_map_msi_pirq(struct domain *d, int
> > index, int *pirq_p,
> > {
> > int irq, pirq, ret;
> >
> > +ASSERT(pcidevs_locked() ||
On 22.01.2024 21:53, Elliott Mitchell wrote:
> I've been mentioning this on a regular basis, but the state of MCE
> handling with Xen seems poor.
I certainly agree here.
> I find the present handling of MCE in Xen an odd choice. Having Xen do
> most of the handling of MCE events is a behavior
On 22.12.2023 16:13, Oleksii Kurochko wrote:
> --- a/xen/arch/riscv/include/asm/fence.h
> +++ b/xen/arch/riscv/include/asm/fence.h
> @@ -1,4 +1,4 @@
> -/* SPDX-License-Identifier: GPL-2.0-or-later */
> +/* SPDX-License-Identifier: GPL-2.0-only */
> #ifndef _ASM_RISCV_FENCE_H
> #define
On 22.12.2023 16:13, Oleksii Kurochko wrote:
> +static inline void arch_move_irqs(struct vcpu *v)
> +{
> +BUG();
> +}
As I think you said you're doing the conversion already - with this
becoming the "canonical" BUG_ON("unimplemented"):
Acked-by: Jan Beulich
Jan
On 22.12.2023 16:13, Oleksii Kurochko wrote:
> Also, the patch adds some helpful macros that assist in avoiding
> the redefinition of memory layout for each MMU mode.
>
> Signed-off-by: Oleksii Kurochko
> ---
> Changes in V3:
> - drop OFFSET_BITS, and use PAGE_SHIFT instead.
> - code style
On 22.12.2023 16:13, Oleksii Kurochko wrote:
> Signed-off-by: Oleksii Kurochko
> ---
> Changes in V3:
> - Update the commit message
??? (again)
> @@ -53,6 +56,18 @@ struct cpu_user_regs
> unsigned long pregs;
> };
>
> +/* TODO: need to implement */
> +#define cpu_to_core(cpu) (0)
>
On Tue, 2024-01-23 at 12:18 +0100, Jan Beulich wrote:
> On 22.12.2023 16:13, Oleksii Kurochko wrote:
> > +static inline void arch_move_irqs(struct vcpu *v)
> > +{
> > + BUG();
> > +}
>
> As I think you said you're doing the conversion already - with this
> becoming the "canonical"
flight 184431 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/184431/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 184409
test-armhf-armhf-libvirt-qcow2 15
On 22.12.2023 16:13, Oleksii Kurochko wrote:> ---
a/xen/arch/riscv/include/asm/current.h
> +++ b/xen/arch/riscv/include/asm/current.h
> @@ -3,6 +3,21 @@
> #ifndef __ASM_CURRENT_H
> #define __ASM_CURRENT_H
>
> +#include
> +#include
> +#include
> +
> +#ifndef __ASSEMBLY__
> +
> +/* Which
On Tue, 2024-01-23 at 11:30 +0100, Jan Beulich wrote:
> On 23.01.2024 11:21, Oleksii wrote:
> > On Mon, 2024-01-22 at 17:56 +0100, Jan Beulich wrote:
> > > On 22.12.2023 16:12, Oleksii Kurochko wrote:
> > > > --- /dev/null
> > > > +++ b/xen/arch/riscv/include/asm/fence.h
> > > > @@ -0,0 +1,13 @@
>
On 22.12.2023 16:13, Oleksii Kurochko wrote:
> All necessary dummiy implementation of functions in this header
> will be introduced in stubs.c
>
> Signed-off-by: Oleksii Kurochko
Acked-by: Jan Beulich
On 22.12.2023 16:13, Oleksii Kurochko wrote:
> Signed-off-by: Oleksii Kurochko
> ---
> Changes in V3:
> - new patch
> ---
> README | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/README b/README
> index c8a108449e..1015a285c0 100644
> --- a/README
> +++ b/README
> @@ -48,6 +48,9
On Tue, 2024-01-23 at 11:28 +0100, Jan Beulich wrote:
> On 23.01.2024 11:15, Oleksii wrote:
> > On Mon, 2024-01-22 at 17:27 +0100, Jan Beulich wrote:
> > > On 22.12.2023 16:12, Oleksii Kurochko wrote:
> > > > + : "=r" (ret__), "+A" (*ptr__) \
> > > > + : "r" (new__) \
> > > >
On Tue, 2024-01-23 at 12:14 +0100, Jan Beulich wrote:
> On 22.12.2023 16:13, Oleksii Kurochko wrote:
> > --- a/xen/arch/riscv/include/asm/fence.h
> > +++ b/xen/arch/riscv/include/asm/fence.h
> > @@ -1,4 +1,4 @@
> > -/* SPDX-License-Identifier: GPL-2.0-or-later */
> > +/* SPDX-License-Identifier:
On Mon, 2024-01-22 at 17:56 +0100, Jan Beulich wrote:
> On 22.12.2023 16:12, Oleksii Kurochko wrote:
> > --- /dev/null
> > +++ b/xen/arch/riscv/include/asm/atomic.h
> > @@ -0,0 +1,384 @@
> > +/* SPDX-License-Identifier: GPL-2.0-only */
> > +/*
> > + * Taken and modified from Linux.
> > + *
> > +
On 23.01.2024 11:21, Oleksii wrote:
> On Mon, 2024-01-22 at 17:56 +0100, Jan Beulich wrote:
>> On 22.12.2023 16:12, Oleksii Kurochko wrote:
>>> --- /dev/null
>>> +++ b/xen/arch/riscv/include/asm/fence.h
>>> @@ -0,0 +1,13 @@
>>> +/* SPDX-License-Identifier: GPL-2.0-or-later */
>>> +#ifndef
flight 184429 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/184429/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 184426
On 23.01.2024 11:15, Oleksii wrote:
> On Mon, 2024-01-22 at 17:27 +0100, Jan Beulich wrote:
>> On 22.12.2023 16:12, Oleksii Kurochko wrote:
>>> + : "=r" (ret__), "+A" (*ptr__) \
>>> + : "r" (new__) \
>>> + : "memory" ); \
>>> + break; \
>>> + case 8: \
While not performance critical, these hook invocations still want
converting: This way all pre-filled struct cpu_dev instances can become
__initconst_cf_clobber, thus allowing to eliminate further 8 ENDBR
during the 2nd phase of alternatives patching (besides moving previously
resident data to
On 22.12.2023 16:13, Oleksii Kurochko wrote:
> Signed-off-by: Oleksii Kurochko
> Acked-by: Jan Beulich
> ---
> Changes in V3:
> - update the commit message
Once again I find this puzzling, considering there's no commit message
at all.
Jan
Hi Carlo,
On 18/01/2024 14:27, Carlo Nonato wrote:
On Tue, Jan 9, 2024 at 11:33 AM Jan Beulich wrote:
On 09.01.2024 11:28, Jan Beulich wrote:
On 02.01.2024 10:51, Carlo Nonato wrote:
v5:
- Carlo Nonato as the new author
- the colored allocator balances color usage for each domain and it
On 22.12.2023 16:13, Oleksii Kurochko wrote:
> Signed-off-by: Oleksii Kurochko
> ---
> Changes in V3:
> - update the commit message
??? (yet again)
> --- a/xen/arch/riscv/include/asm/mm.h
> +++ b/xen/arch/riscv/include/asm/mm.h
> @@ -3,8 +3,251 @@
> #ifndef _ASM_RISCV_MM_H
> #define
On Tue, Jan 23, 2024 at 10:13:52AM +, Chen, Jiqian wrote:
> On 2024/1/23 07:37, Bjorn Helgaas wrote:
> > On Fri, Jan 05, 2024 at 02:22:17PM +0800, Jiqian Chen wrote:
> >> There is a need for some scenarios to use gsi sysfs.
> >> For example, when xen passthrough a device to dumU, it will
> >>
On Tue, 2024-01-23 at 12:32 +0100, Jan Beulich wrote:
> On 22.12.2023 16:13, Oleksii Kurochko wrote:
> > Also, the patch adds some helpful macros that assist in avoiding
> > the redefinition of memory layout for each MMU mode.
> >
> > Signed-off-by: Oleksii Kurochko
> > ---
> > Changes in V3:
>
On Tue, 2024-01-23 at 12:35 +0100, Jan Beulich wrote:
> On 22.12.2023 16:13, Oleksii Kurochko wrote:> ---
> a/xen/arch/riscv/include/asm/current.h
> > +++ b/xen/arch/riscv/include/asm/current.h
> > @@ -3,6 +3,21 @@
> > #ifndef __ASM_CURRENT_H
> > #define __ASM_CURRENT_H
> >
> > +#include
> >
On Mon, Jan 22, 2024 at 11:54:14AM +, George Dunlap wrote:
> On Mon, Jan 22, 2024 at 12:31 AM Demi Marie Obenour
> wrote:
> >
> > On Fri, Sep 29, 2023 at 05:42:16PM +0100, George Dunlap wrote:
> > > The basic credit2 algorithm goes something like this:
> > >
> > > 1. All vcpus start with the
On 23.01.2024 15:49, Oleksii wrote:
> On Tue, 2024-01-23 at 12:22 +0100, Jan Beulich wrote:
>> On 22.12.2023 16:13, Oleksii Kurochko wrote:
>>> Signed-off-by: Oleksii Kurochko
>>> ---
>>> Changes in V3:
>>> - new patch
>>> ---
>>> README | 3 +++
>>> 1 file changed, 3 insertions(+)
>>>
>>>
On Tue, 2024-01-23 at 12:36 +0100, Jan Beulich wrote:
> On 22.12.2023 16:13, Oleksii Kurochko wrote:
> > Signed-off-by: Oleksii Kurochko
> > Acked-by: Jan Beulich
> > ---
> > Changes in V3:
> > - update the commit message
>
> Once again I find this puzzling, considering there's no commit
>
On Tue, 2024-01-23 at 12:39 +0100, Jan Beulich wrote:
> On 22.12.2023 16:13, Oleksii Kurochko wrote:
> > Signed-off-by: Oleksii Kurochko
> > ---
> > Changes in V3:
> > - Update the commit message
>
> ??? (again)
The same as with previous. asm/processor.h was changed to processor.h
>
> > @@
On Tue, 2024-01-23 at 14:20 +0100, Jan Beulich wrote:
> On 22.12.2023 16:13, Oleksii Kurochko wrote:
> > --- a/xen/arch/riscv/early_printk.c
> > +++ b/xen/arch/riscv/early_printk.c
> > @@ -40,171 +40,3 @@ void early_printk(const char *str)
> > str++;
> > }
> > }
> > -
> > -/*
> > -
On Tue, 2024-01-23 at 18:05 +0100, Jan Beulich wrote:
> On 23.01.2024 15:49, Oleksii wrote:
> > On Tue, 2024-01-23 at 12:22 +0100, Jan Beulich wrote:
> > > On 22.12.2023 16:13, Oleksii Kurochko wrote:
> > > > Signed-off-by: Oleksii Kurochko
> > > > ---
> > > > Changes in V3:
> > > > - new
On Tue, 2024-01-23 at 14:03 +0100, Jan Beulich wrote:
> On 22.12.2023 16:13, Oleksii Kurochko wrote:
> > Signed-off-by: Oleksii Kurochko
> > ---
> > Changes in V3:
> > - update the commit message
>
> ??? (yet again)
asm/mm.h was changed to mm.h
>
> > --- a/xen/arch/riscv/include/asm/mm.h
> >
flight 184436 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/184436/
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
76 matches
Mail list logo
