Hi Luca,
On 17/05/2023 02:44, Stefano Stabellini wrote:
>
>
> On Thu, 4 May 2023, Luca Fancellu wrote:
>> repository in the reports
>>
>> Currently the cppcheck report entries shows the relative file path
>> from the /xen folder of the repository instead of the base folder.
>> In order to ease t
flight 180701 xen-unstable real [real]
flight 180719 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/180701/
http://logs.test-lab.xenproject.org/osstest/logs/180719/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be r
> On 19 May 2023, at 08:08, Michal Orzel wrote:
>
> Hi Luca,
>
> On 17/05/2023 02:44, Stefano Stabellini wrote:
>>
>>
>> On Thu, 4 May 2023, Luca Fancellu wrote:
>>> repository in the reports
>>>
>>> Currently the cppcheck report entries shows the relative file path
>>> from the /xen folder
On 18.05.2023 12:34, Roger Pau Monné wrote:
> On Wed, May 17, 2023 at 05:59:31PM -0700, Stefano Stabellini wrote:
>> I have run into another PVH Dom0 issue. I am trying to enable a PVH Dom0
>> test with the brand new gitlab-ci runner offered by Qubes. It is an AMD
>> Zen3 system and we already have
On 19/05/2023 09:12, Luca Fancellu wrote:
>
>
>> On 19 May 2023, at 08:08, Michal Orzel wrote:
>>
>> Hi Luca,
>>
>> On 17/05/2023 02:44, Stefano Stabellini wrote:
>>>
>>>
>>> On Thu, 4 May 2023, Luca Fancellu wrote:
repository in the reports
Currently the cppcheck report entries
On Fri, May 19, 2023 at 09:22:58AM +0200, Jan Beulich wrote:
> On 18.05.2023 12:34, Roger Pau Monné wrote:
> > On Wed, May 17, 2023 at 05:59:31PM -0700, Stefano Stabellini wrote:
> >> I have run into another PVH Dom0 issue. I am trying to enable a PVH Dom0
> >> test with the brand new gitlab-ci run
On Thu, May 18, 2023 at 06:46:52PM -0700, Stefano Stabellini wrote:
> On Thu, 18 May 2023, Roger Pau Monné wrote:
> > On Wed, May 17, 2023 at 05:59:31PM -0700, Stefano Stabellini wrote:
> > > Hi all,
> > >
> > > I have run into another PVH Dom0 issue. I am trying to enable a PVH Dom0
> > > test wi
On 19.05.2023 09:38, Roger Pau Monné wrote:
> On Fri, May 19, 2023 at 09:22:58AM +0200, Jan Beulich wrote:
>> On 18.05.2023 12:34, Roger Pau Monné wrote:
>>> On Wed, May 17, 2023 at 05:59:31PM -0700, Stefano Stabellini wrote:
I have run into another PVH Dom0 issue. I am trying to enable a PVH
On 17.05.2023 17:56, Oleksii wrote:
> On Tue, 2023-05-16 at 17:42 +0200, Jan Beulich wrote:
>> On 11.05.2023 19:09, Oleksii Kurochko wrote:
>>> ===
>>> =
>>> + * Start addr | End addr | Size | Slot
>>> |a
On 18.05.2023 23:27, Stewart Hildebrand wrote:
> On 5/5/23 01:59, Juergen Gross wrote:
>> On 01.05.23 22:30, Stewart Hildebrand wrote:
>>> When creating a domU, but the creation fails, there is a corner case that
>>> may
>>> lead to a crash in the null scheduler when running a debug build of Xen.
On 18.05.2023 23:06, Stewart Hildebrand wrote:
> --- a/xen/include/xen/iommu.h
> +++ b/xen/include/xen/iommu.h
> @@ -26,6 +26,7 @@
> #include
> #include
> #include
> +#include
> #include
I view this as problematic: It'll require all architectures with an
IOMMU implementation to have an as
On Wed, May 17, 2023 at 06:10:17PM -0400, Stefan Hajnoczi wrote:
Introduce a new API for thread-local blk_io_plug() that does not
traverse the block graph. The goal is to make blk_io_plug() multi-queue
friendly.
Instead of having block drivers track whether or not we're in a plugged
section, pro
On Wed, May 17, 2023 at 06:10:18PM -0400, Stefan Hajnoczi wrote:
Stop using the .bdrv_co_io_plug() API because it is not multi-queue
block layer friendly. Use the new blk_io_plug_call() API to batch I/O
submission instead.
Signed-off-by: Stefan Hajnoczi
---
block/nvme.c | 44 ---
On Wed, May 17, 2023 at 06:10:19PM -0400, Stefan Hajnoczi wrote:
Stop using the .bdrv_co_io_plug() API because it is not multi-queue
block layer friendly. Use the new blk_io_plug_call() API to batch I/O
submission instead.
Signed-off-by: Stefan Hajnoczi
---
block/blkio.c | 40 ++
Hi Ayan,
On 18/05/2023 16:39, Ayan Kumar Halder wrote:
> Restructure the code so that one can use pa_range_info[] table for both
> ARM_32 as well as ARM_64.
>
> Also, removed the hardcoding for P2M_ROOT_ORDER and P2M_ROOT_LEVEL as
> p2m_root_order can be obtained from the pa_range_info[].root_ord
On Fri, May 19, 2023 at 10:20:24AM +0200, Jan Beulich wrote:
> On 19.05.2023 09:38, Roger Pau Monné wrote:
> > On Fri, May 19, 2023 at 09:22:58AM +0200, Jan Beulich wrote:
> >> On 18.05.2023 12:34, Roger Pau Monné wrote:
> >>> On Wed, May 17, 2023 at 05:59:31PM -0700, Stefano Stabellini wrote:
> >>
Hi Ayan,
On 18/05/2023 16:39, Ayan Kumar Halder wrote:
> Some Arm based hardware platforms which does not support LPAE
> (eg Cortex-R52), uses 32 bit physical addresses.
> Also, users may choose to use 32 bits to represent physical addresses
> for optimization.
>
> To support the above use cases,
On 18.05.2023 12:57, Roger Pau Monne wrote:
> When a domain parameter is provided to pci_get_pdev() the search
> function would match against the bdf, without taking the segment into
> account.
>
> Fix this and also account for the passed segment.
>
> Fixes: 8cf6e0738906 ('PCI: simplify (and thus
On 19.05.2023 10:55, Roger Pau Monné wrote:
> On Fri, May 19, 2023 at 10:20:24AM +0200, Jan Beulich wrote:
>> On 19.05.2023 09:38, Roger Pau Monné wrote:
>>> On Fri, May 19, 2023 at 09:22:58AM +0200, Jan Beulich wrote:
On 18.05.2023 12:34, Roger Pau Monné wrote:
> On Wed, May 17, 2023 at 0
From: Arnd Bergmann
These function are all called from assembler files, or from inline assembler,
so there is no immediate need for a prototype in a header, but if
-Wmissing-prototypes
is enabled, the compiler warns about them:
arch/x86/xen/efi.c:130:13: error: no previous prototype for 'xen_ef
Currenly there is a latent bug that is not triggered because
the function cppcheck_merge_txt_fragments is called with the
parameter strip_paths having a list of only one element.
The bug is that the split function should not be in the
loop for strip_paths, but one level before, fix it.
Fixes: 02b
Fix the generation of the relative path from the repo, for cppcheck
reports, when the script is launching make with in-tree build.
Fixes: b046f7e37489 ("xen/misra: xen-analysis.py: use the relative path from
the ...")
Reported-by: Michal Orzel
Signed-off-by: Luca Fancellu
---
.../xen_analysis/
Use tuple comparison to check the cppcheck version.
Take the occasion to harden the regex, escaping the dots so that we
check for them instead of generic characters.
Suggested-by: Andrew Cooper
Signed-off-by: Luca Fancellu
---
xen/scripts/xen_analysis/cppcheck_analysis.py | 13 -
1
This serie includes one improvement suggested by Andrew Cooper, and two bug fix
for the xen-analysis.py tool.
Luca Fancellu (3):
xen/misra: xen-analysis.py: Improve the cppcheck version check
xen/misra: xen-analysis.py: Fix latent bug
xen/misra: xen-analysis.py: Fix cppcheck report relative
Add a feature to the diff-report.py script that improves the comparison
between two analysis report, one from a baseline codebase and the other
from the changes applied to the baseline.
The comparison between reports of different codebase is an issue because
entries in the baseline could have been
Add a new tool, diff-report.py that can be used to make diff between
reports generated by xen-analysis.py tool.
Currently this tool supports the Xen cppcheck text report format in
its operations.
The tool prints every finding that is in the report passed with -r
(check report) which is not in the
This serie is dependent on this patch, in case cppcheck report are generated
using xen-analysis.py that calls the makefile with in-tree build:
https://patchwork.kernel.org/project/xen-devel/patch/20230519093019.2131896
> On 19 May 2023, at 08:25, Michal Orzel wrote:
>
>
> On 19/05/2023 09:12, Luca Fancellu wrote:
>>
>>
>>> On 19 May 2023, at 08:08, Michal Orzel wrote:
>>>
>>> Hi Luca,
>>>
>>> On 17/05/2023 02:44, Stefano Stabellini wrote:
On Thu, 4 May 2023, Luca Fancellu wrote:
> r
On Fri, May 19, 2023 at 12:56 AM Dave Hansen wrote:
> On 5/16/23 12:35, Arnd Bergmann wrote:
> I picked up the ones that were blatantly obvious, but left out 03, 04,
> 10, 12 and 19 for the moment.
Btw, there is series that went unnoticed
https://lore.kernel.org/all/2029110017.48510-1-andri
On Fri, May 19, 2023 at 06:04:05AM +0200, Christoph Hellwig wrote:
> On Thu, May 18, 2023 at 08:18:39PM +0200, Marek Marczykowski-Górecki wrote:
> > On Thu, May 18, 2023 at 03:42:51PM +0200, Christoph Hellwig wrote:
> > > Remove the dangerous late initialization of xen-swiotlb in
> > > pci_xen_swio
> On 19 May 2023, at 10:46, Luca Fancellu wrote:
>
> Add a feature to the diff-report.py script that improves the comparison
> between two analysis report, one from a baseline codebase and the other
> from the changes applied to the baseline.
>
> The comparison between reports of different cod
On 19.05.2023 11:46, Luca Fancellu wrote:
> Add a new tool, diff-report.py that can be used to make diff between
> reports generated by xen-analysis.py tool.
> Currently this tool supports the Xen cppcheck text report format in
> its operations.
>
> The tool prints every finding that is in the rep
On Thu, May 18, 2023, at 19:28, Dave Hansen wrote:
> On 5/16/23 12:35, Arnd Bergmann wrote:
>>
>> arch/x86/xen/enlighten_pv.c:1233:34: error: no previous prototype for
>> 'xen_start_kernel' [-Werror=missing-prototypes]
>> arch/x86/xen/irq.c:22:14: error: no previous prototype for
>> 'xen_force_e
> On 19 May 2023, at 11:53, Jan Beulich wrote:
>
> On 19.05.2023 11:46, Luca Fancellu wrote:
>> Add a new tool, diff-report.py that can be used to make diff between
>> reports generated by xen-analysis.py tool.
>> Currently this tool supports the Xen cppcheck text report format in
>> its operat
XSM is a subsystem where it is equally important of how and where its hooks are
called as is the implementation of the hooks. The people best suited for
evaluating the how and where are the XSM maintainers and reviewers. This
creates a challenge as the hooks are used throughout the hypervisor for w
On Thu, May 18, 2023, at 23:56, Dave Hansen wrote:
> On 5/16/23 12:35, Arnd Bergmann wrote:
>>
>> All of the warnings have to be addressed in some form before the warning
>> can be enabled by default.
>
> I picked up the ones that were blatantly obvious, but left out 03, 04,
> 10, 12 and 19 for th
On Fri, May 19, 2023 at 12:10:26PM +0200, Marek Marczykowski-Górecki wrote:
> While I would say PCI passthrough is not very common for PV guests, can
> the decision about xen-swiotlb be delayed until you can enumerate
> xenstore to check if there are any PCI devices connected (and not
> allocate xe
On 19/05/2023 1:41 pm, Christoph Hellwig wrote:
> On Fri, May 19, 2023 at 12:10:26PM +0200, Marek Marczykowski-Górecki wrote:
>> While I would say PCI passthrough is not very common for PV guests, can
>> the decision about xen-swiotlb be delayed until you can enumerate
>> xenstore to check if there
On Fri, May 19, 2023 at 01:49:46PM +0100, Andrew Cooper wrote:
> > The alternative would be to finally merge swiotlb-xen into swiotlb, in
> > which case we might be able to do this later. Let me see what I can
> > do there.
>
> If that is an option, it would be great to reduce the special-cashing
flight 180706 linux-linus real [real]
flight 180734 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/180706/
http://logs.test-lab.xenproject.org/osstest/logs/180734/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run
On 19.05.2023 13:10, Luca Fancellu wrote:
>
>
>> On 19 May 2023, at 11:53, Jan Beulich wrote:
>>
>> On 19.05.2023 11:46, Luca Fancellu wrote:
>>> Add a new tool, diff-report.py that can be used to make diff between
>>> reports generated by xen-analysis.py tool.
>>> Currently this tool supports t
Hi Oleg,
On 19/05/2023 15:38, Oleg Nikitenko wrote:
>
>
>
> Hello,
>
> Thanks Michal.
>
> Then the next question. Now it is more related to the integration than to the
> development.
> A license for the xen in 4.17 revision at branch xlnx_rebase_4.17 xilinx repo
> has changed.
> I fou
flight 180721 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180721/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 180691
build-amd64
On Mon, May 01, 2023 at 03:30:28PM -0400, Jason Andryuk wrote:
> Expose the hwp_para fields through libxc.
>
> Signed-off-by: Jason Andryuk
Acked-by: Anthony PERARD
Thanks,
--
Anthony PERARD
On Mon, May 01, 2023 at 03:30:31PM -0400, Jason Andryuk wrote:
> Add xc_set_cpufreq_hwp to allow calling xen_systctl_pm_op
> SET_CPUFREQ_HWP.
>
> Signed-off-by: Jason Andryuk
Acked-by: Anthony PERARD
Thanks,
--
Anthony PERARD
On 19.05.2023 08:15, Jan Beulich wrote:
> On 17.05.2023 19:05, Andrew Cooper wrote:
>> On 17/05/2023 3:22 pm, Jan Beulich wrote:
>>> There's no real need for the associated probing - we can easily convert
>>> to a uniform value without knowing the specific behavior (note also that
>>> the respectiv
> On 18 May 2023, at 10:35, Julien Grall wrote:
>
> Hi Luca,
>
> Sorry for jumping late in the review.
Hi Julien,
Thank you for taking the time to review,
>>
>> /*
>>* Comment from Linux:
>>* Userspace may perform DC ZVA instructions. Mismatched block sizes
>> diff --git a/xen/ar
On 5/19/23 04:45, Jan Beulich wrote:
> On 18.05.2023 23:06, Stewart Hildebrand wrote:
>> --- a/xen/include/xen/iommu.h
>> +++ b/xen/include/xen/iommu.h
>> @@ -26,6 +26,7 @@
>> #include
>> #include
>> #include
>> +#include
>> #include
>
> I view this as problematic: It'll require all archi
On 19/05/2023 7:00 am, Jan Beulich wrote:
> On 17.05.2023 18:35, Andrew Cooper wrote:
>> On 17/05/2023 3:47 pm, Jan Beulich wrote:
>>> On 16.05.2023 16:53, Andrew Cooper wrote:
@@ -401,6 +400,8 @@ static void __init print_details(enum ind_thunk thunk,
uint64_t caps)
cpuid_c
flight 180714 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180714/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt-raw 15 saverestore-support-checkfail like 180698
test-armhf-armhf-libvirt-qcow2 15 saveres
Hi Luca,
On 19/05/2023 15:26, Luca Fancellu wrote:
On 18 May 2023, at 10:35, Julien Grall wrote:
/*
* Comment from Linux:
* Userspace may perform DC ZVA instructions. Mismatched block sizes
diff --git a/xen/arch/arm/arm64/sve-asm.S b/xen/arch/arm/arm64/sve-asm.S
new file mode 100644
> On 19 May 2023, at 15:46, Julien Grall wrote:
>
> Hi Luca,
>
> On 19/05/2023 15:26, Luca Fancellu wrote:
>>> On 18 May 2023, at 10:35, Julien Grall wrote:
/*
* Comment from Linux:
* Userspace may perform DC ZVA instructions. Mismatched block sizes
diff --git a/xe
On 19/05/2023 15:51, Luca Fancellu wrote:
/* Control Registers */
/*
* CPTR_EL2 needs to be written before calling vfp_restore_state, a
* synchronization instruction is expected after the write (isb)
*/
WRITE_SYSREG(n->arch.cptr_el2, CPTR_EL2);
WRITE_SYSREG(n->arch.cpacr, CPACR_EL1);
/*
* Thi
> On 19 May 2023, at 16:00, Julien Grall wrote:
>
>
>
> On 19/05/2023 15:51, Luca Fancellu wrote:
>> /* Control Registers */
>> /*
>> * CPTR_EL2 needs to be written before calling vfp_restore_state, a
>> * synchronization instruction is expected after the write (isb)
>> */
>> WRITE_SYSREG(n-
Hi,
On 19/05/2023 16:13, Luca Fancellu wrote:
On 19/05/2023 15:51, Luca Fancellu wrote:
/* Control Registers */
/*
* CPTR_EL2 needs to be written before calling vfp_restore_state, a
* synchronization instruction is expected after the write (isb)
*/
WRITE_SYSREG(n->arch.cptr_el2, CPTR_EL2);
WRIT
On 17/05/2023 3:01 pm, Jan Beulich wrote:
> On 16.05.2023 16:53, Andrew Cooper wrote:
>> --- a/xen/arch/x86/include/asm/cpufeature.h
>> +++ b/xen/arch/x86/include/asm/cpufeature.h
>> @@ -7,6 +7,7 @@
>> #define __ASM_I386_CPUFEATURE_H
>>
>> #include
>> +#include
>> #include
> This isn't need
On 16/05/2023 1:02 pm, Jan Beulich wrote:
> On 15.05.2023 16:42, Andrew Cooper wrote:
>> Bits through 24 are already defined, meaning that we're not far off needing
>> the second word. Put both in right away.
>>
>> The bool bitfield names in the arch_caps union are unused, and somewhat out
>> of
On 17/05/2023 10:20 am, Jan Beulich wrote:
> On 16.05.2023 21:31, Andrew Cooper wrote:
>> On 16/05/2023 3:53 pm, Jan Beulich wrote:
>>> I guess that's no
>>> different from other max-only features with dependents, but I wonder
>>> whether that's good behavior.
>> It's not really something you get a
On 16/05/2023 3:58 pm, Jan Beulich wrote:
> On 15.05.2023 16:42, Andrew Cooper wrote:
>> --- a/xen/arch/x86/cpu-policy.c
>> +++ b/xen/arch/x86/cpu-policy.c
>> @@ -408,6 +408,25 @@ static void __init calculate_host_policy(void)
>> p->platform_info.cpuid_faulting = cpu_has_cpuid_faulting;
>> }
On Thu, Apr 06, 2023 at 03:57:12PM +0100, Peter Hoyes wrote:
> On 04/04/2023 17:28, Anthony PERARD wrote:
> > On Wed, Mar 22, 2023 at 01:58:00PM +, Peter Hoyes wrote:
> > > From: Peter Hoyes
> > >
> > > Saving, restoring and migrating domains are not currently supported on
> > > arm and arm64
Saving, restoring and migrating domains are not currently supported on
arm and arm64 platforms, so xendomains prints the warning:
An error occurred while saving domain:
command not implemented
when attempting to run `xendomains stop`. It otherwise continues to shut
down the domains cleanly, w
flight 180742 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180742/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 180691
build-amd64
On 19/05/2023 5:28 pm, Jeffrey Hugo wrote:
> DESCEND objtool
> INSTALL libsubcmd_headers
> CALL scripts/checksyscalls.sh
> AS arch/x86/kernel/head_64.o
> arch/x86/kernel/head_64.S: Assembler messages:
> arch/x86/kernel/head_64.S:261: Error: missing ')'
> arch/x86/kernel/head_64.S:26
> On 18 May 2023, at 19:27, Julien Grall wrote:
>
> Hi Luca,
>
> On 24/04/2023 07:02, Luca Fancellu wrote:
>> Save/restore context switch for SVE, allocate memory to contain
>> the Z0-31 registers whose length is maximum 2048 bits each and
>> FFR who can be maximum 256 bits, the allocated memo
Hi,
On 19/05/2023 18:35, Luca Fancellu wrote:
On 18 May 2023, at 19:27, Julien Grall wrote:
Hi Luca,
On 24/04/2023 07:02, Luca Fancellu wrote:
Save/restore context switch for SVE, allocate memory to contain
the Z0-31 registers whose length is maximum 2048 bits each and
FFR who can be maxi
branch xen-unstable
xenbranch xen-unstable
job build-amd64-xsm
testid xen-build
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu https://gitlab.com/qemu-project/qemu.git
Tree: seabios git://xenbits.xen.org/osstest/seabios.git
T
flight 180726 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180726/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-vhd 21 guest-start/debian.repeat fail REGR. vs. 180696
Tests which are fa
On 5/19/23 5:28 AM, Arnd Bergmann wrote:
diff --git a/arch/x86/xen/smp.h b/arch/x86/xen/smp.h
index 22fb982ff971..81a7821dd07f 100644
--- a/arch/x86/xen/smp.h
+++ b/arch/x86/xen/smp.h
@@ -1,7 +1,11 @@
/* SPDX-License-Identifier: GPL-2.0 */
#ifndef _XEN_SMP_H
+void asm_cpu_bringup_and_i
On Fri, 19 May 2023, Jan Beulich wrote:
> On 18.05.2023 12:34, Roger Pau Monné wrote:
> > On Wed, May 17, 2023 at 05:59:31PM -0700, Stefano Stabellini wrote:
> >> I have run into another PVH Dom0 issue. I am trying to enable a PVH Dom0
> >> test with the brand new gitlab-ci runner offered by Qubes.
branch xen-unstable
xenbranch xen-unstable
job build-amd64
testid xen-build
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu https://gitlab.com/qemu-project/qemu.git
Tree: seabios git://xenbits.xen.org/osstest/seabios.git
Tree:
On Fri, 19 May 2023, Roger Pau Monné wrote:
> On Thu, May 18, 2023 at 06:46:52PM -0700, Stefano Stabellini wrote:
> > On Thu, 18 May 2023, Roger Pau Monné wrote:
> > > On Wed, May 17, 2023 at 05:59:31PM -0700, Stefano Stabellini wrote:
> > > > Hi all,
> > > >
> > > > I have run into another PVH Do
On Fri, May 19, 2023 at 05:02:21PM -0700, Stefano Stabellini wrote:
> On Fri, 19 May 2023, Roger Pau Monné wrote:
> > On Thu, May 18, 2023 at 06:46:52PM -0700, Stefano Stabellini wrote:
> > > On Thu, 18 May 2023, Roger Pau Monné wrote:
> > > > On Wed, May 17, 2023 at 05:59:31PM -0700, Stefano Stabe
flight 180738 linux-linus real [real]
flight 180776 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/180738/
http://logs.test-lab.xenproject.org/osstest/logs/180776/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run
flight 180753 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180753/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 180691
build-amd64
Qubes OS is trying to switch from relying on populate-on-demand to
memory hotplug for Linux guests. However, this runs into a problem,
which is that only a limited amount of memory can be hotplugged.
My experiments with Qubes OS’s build of Linux 6.3.2 reveal:
- The more memory a guest starts off
branch xen-unstable
xenbranch xen-unstable
job build-i386-xsm
testid xen-build
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu https://gitlab.com/qemu-project/qemu.git
Tree: seabios git://xenbits.xen.org/osstest/seabios.git
Tr
pulled in this change via the next tree, tag next-20230519 and I get a
build failure using the x86_64_defconfig -
DESCEND objtool
INSTALL libsubcmd_headers
CALLscripts/checksyscalls.sh
AS arch/x86/kernel/head_64.o
arch/x86/kernel/head_64.S: Assembler messages:
arch/x86/kernel
Reviewed-by: Lyude Paul
Thanks for getting to this!
On Thu, 2023-05-18 at 15:42 +0200, Christoph Hellwig wrote:
> Drivers have no business looking into dma-mapping internals and check
> what backend is used. Unfortunstely the DRM core is still broken and
> tries to do plain page allocations ins
On 5/19/2023 10:57 AM, Andrew Cooper wrote:
On 19/05/2023 5:28 pm, Jeffrey Hugo wrote:
DESCEND objtool
INSTALL libsubcmd_headers
CALL scripts/checksyscalls.sh
AS arch/x86/kernel/head_64.o
arch/x86/kernel/head_64.S: Assembler messages:
arch/x86/kernel/head_64.S:261: Error: mis
On Fri, May 19, 2023 at 02:58:57PM +0200, Christoph Hellwig wrote:
> On Fri, May 19, 2023 at 01:49:46PM +0100, Andrew Cooper wrote:
> > > The alternative would be to finally merge swiotlb-xen into swiotlb, in
> > > which case we might be able to do this later. Let me see what I can
> > > do there.
80 matches
Mail list logo
