On 16.03.2023 23:03, Elliott Mitchell wrote:
> On Mon, Mar 13, 2023 at 08:01:02AM +0100, Jan Beulich wrote:
>> On 11.03.2023 01:09, Elliott Mitchell wrote:
>>> On Thu, Mar 09, 2023 at 10:03:23AM +0100, Jan Beulich wrote:
In any event you will want to collect a serial log at maximum verbos
On 16.03.2023 23:59, Stefano Stabellini wrote:
> On Thu, 16 Mar 2023, Jan Beulich wrote:
>> On 16.03.2023 11:26, Michal Orzel wrote:
>>> --- a/xen/drivers/char/console.c
>>> +++ b/xen/drivers/char/console.c
>>> @@ -490,7 +490,24 @@ static void switch_serial_input(void)
>>> }
>>> else
>>>
On Tue, Mar 14, 2023 at 08:56:30PM +, Volodymyr Babchuk wrote:
> From: Oleksandr Andrushchenko
>
> A guest would be able to read and write those registers which are not
> emulated and have no respective vPCI handlers, so it will be possible
> for it to access the hardware directly.
> In order
On 17.03.2023 00:19, Stefano Stabellini wrote:
> On Thu, 16 Mar 2023, Jan Beulich wrote:
>> So yes, it then all boils down to that Linux-
>> internal question.
>
> Excellent question but we'll have to wait for Ray as he is the one with
> access to the hardware. But I have this data I can share in
On Tue, Mar 14, 2023 at 08:56:30PM +, Volodymyr Babchuk wrote:
> vPCI MMIO handlers are accessing pdevs without protecting this
> access with pcidevs_{lock|unlock}. This is not a problem as of now
> as these are only used by Dom0. But, towards vPCI is used also for
> guests, we need to properly
On 16.03.2023 18:16, Marek Marczykowski-Górecki wrote:
> Python2 is not supported anymore.
There are two things here which concern me: For one, how come this is
at the end of a series? You want to keep in mind that any series may
be committed piecemeal (unless an indication to the contrary is in
t
On Tue, Mar 14, 2023 at 08:56:30PM +, Volodymyr Babchuk wrote:
> This can be handy during new reference counter approach evaluation.
>
> Signed-off-by: Volodymyr Babchuk
>
> ---
>
> v3:
> - Moved from another patch series
> ---
> xen/drivers/passthrough/pci.c | 3 ++-
> 1 file changed, 2
On Thu, 2023-03-16 at 12:26 +0100, Jan Beulich wrote:
> On 15.03.2023 18:21, Oleksii Kurochko wrote:
> > --- /dev/null
> > +++ b/xen/common/bug.c
> > @@ -0,0 +1,108 @@
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +#include
> > +
> > +
On 17/03/2023 09:36, Jan Beulich wrote:
>
>
> On 16.03.2023 23:59, Stefano Stabellini wrote:
>> On Thu, 16 Mar 2023, Jan Beulich wrote:
>>> On 16.03.2023 11:26, Michal Orzel wrote:
--- a/xen/drivers/char/console.c
+++ b/xen/drivers/char/console.c
@@ -490,7 +490,24 @@ static void
On Fri, Mar 17, 2023 at 09:39:52AM +0100, Jan Beulich wrote:
> On 17.03.2023 00:19, Stefano Stabellini wrote:
> > On Thu, 16 Mar 2023, Jan Beulich wrote:
> >> So yes, it then all boils down to that Linux-
> >> internal question.
> >
> > Excellent question but we'll have to wait for Ray as he is th
On Thu, Mar 16, 2023 at 05:56:00PM +0100, Jan Beulich wrote:
> On 16.03.2023 17:48, Roger Pau Monné wrote:
> > On Thu, Mar 16, 2023 at 05:43:18PM +0100, Jan Beulich wrote:
> >> On 16.03.2023 17:39, Roger Pau Monné wrote:
> >>> On Thu, Mar 16, 2023 at 05:32:38PM +0100, Jan Beulich wrote:
> On 1
On Fri, Mar 10, 2023 at 10:18:32AM +0100, Roger Pau Monné wrote:
> On Fri, Mar 10, 2023 at 10:01:39AM +1100, Michael Ellerman wrote:
> > Roger Pau Monné writes:
> > > On Mon, Dec 12, 2022 at 01:36:48PM +0100, Roger Pau Monné wrote:
> > >> On Fri, Dec 02, 2022 at 12:40:05PM +0100, Roger Pau Monné w
On Thu, Mar 16, 2023 at 04:09:44PM -0700, Stefano Stabellini wrote:
> On Thu, 16 Mar 2023, Juergen Gross wrote:
> > On 16.03.23 14:53, Alex Deucher wrote:
> > > On Thu, Mar 16, 2023 at 9:48 AM Juergen Gross wrote:
> > > >
> > > > On 16.03.23 14:45, Alex Deucher wrote:
> > > > > On Thu, Mar 16, 20
From: David Woodhouse
The emulated PIIX3 uses a nybble for the status of each PCI function,
so the status for e.g. slot 0 functions 0 and 1 respectively can be
read as (\_GPE.PH00 & 0x0F), and (\_GPE.PH00 >> 0x04).
The AML that Xen gives to a guest gets the operand order for the odd-
numbered fu
On Thu, Feb 23, 2023 at 08:31:29PM +, Julien Grall wrote:
> Hi,
>
> On 23/02/2023 16:01, Andrew Cooper wrote:
> > On 07/10/2022 1:39 pm, Matias Ezequiel Vara Larsen wrote:
> >
> > A couple of observations, all unrelated to the stats themselves.
> >
> > Although overall, I'm not entirely cert
flight 179697 xen-unstable real [real]
flight 179714 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/179697/
http://logs.test-lab.xenproject.org/osstest/logs/179714/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd6
On 15/03/2023 6:54 pm, Dmitry Isaykin wrote:
> diff --git a/xen/arch/x86/hvm/svm/svm.c b/xen/arch/x86/hvm/svm/svm.c
> index a43bcf2e92..49225f48a7 100644
> --- a/xen/arch/x86/hvm/svm/svm.c
> +++ b/xen/arch/x86/hvm/svm/svm.c
> @@ -2939,17 +2939,26 @@ void svm_vmexit_handler(void)
> break;
>
2 small patches cleaning up the parsing code in xl a little bit.
Juergen Gross (2):
tools/xl: allow split_string_into_pair() to trim values
tools/xl: rework p9 config parsing
tools/xl/xl_parse.c | 114 +---
tools/xl/xl_parse.h | 4 +-
2 files changed
Most use cases of split_string_into_pair() are requiring the returned
strings to be white space trimmed.
In order to avoid the same code pattern multiple times, add a predicate
parameter to split_string_into_pair() which can be specified to call
trim() with that predicate for the string pair retur
Rework the config parsing of a p9 device to use the
split_string_into_pair() function instead of open coding it.
Signed-off-by: Juergen Gross
---
tools/xl/xl_parse.c | 72 ++---
1 file changed, 35 insertions(+), 37 deletions(-)
diff --git a/tools/xl/xl_pa
On Mon, Jul 15, 2019 at 02:39:04PM +, Jan Beulich wrote:
> This is faster than using the software implementation, and the insn is
> available on all half-way recent hardware. Therefore convert
> generic_hweight() to out-of-line functions (without affecting Arm)
> and use alternatives patching t
On Tue, May 26, 2020 at 06:40:16PM +0200, Jan Beulich wrote:
> On 26.05.2020 17:01, Andrew Cooper wrote:
> > On 26/05/2020 14:35, Jan Beulich wrote:
> >> On 26.05.2020 13:17, Andrew Cooper wrote:
> >>> On 26/05/2020 07:49, Jan Beulich wrote:
> Respective Core Gen10 processor lines are affected
Adds monitor support for I/O instructions.
Signed-off-by: Dmitry Isaykin
Signed-off-by: Anton Belousov
Acked-by: Tamas K Lengyel
---
Changes in v3:
* Rebase on staging
* Refactor branch logic on monitor_traps response
Changes in v2:
* Handled INS and OUTS instructions too
* Added I/O monit
On Fri, Mar 17, 2023 at 09:46:33AM +0100, Jan Beulich wrote:
> On 16.03.2023 18:16, Marek Marczykowski-Górecki wrote:
> > Python2 is not supported anymore.
>
> There are two things here which concern me: For one, how come this is
> at the end of a series? You want to keep in mind that any series m
flight 179713 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/179713/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 410ca0ff94a42ee541dd6ceab70ea974eeb7e500
baseline version:
ovmf 0e5717009779ec6c1e35f
On 17/03/2023 11:22 am, Roger Pau Monné wrote:
> On Mon, Jul 15, 2019 at 02:39:04PM +, Jan Beulich wrote:
>> This is faster than using the software implementation, and the insn is
>> available on all half-way recent hardware. Therefore convert
>> generic_hweight() to out-of-line functions (with
On Fri, Mar 17, 2023 at 8:46 AM Jan Beulich wrote:
> On 16.03.2023 18:16, Marek Marczykowski-Górecki wrote:
> > Python2 is not supported anymore.
>
> There are two things here which concern me: For one, how come this is
> at the end of a series? You want to keep in mind that any series may
> be c
On 16.03.23 17:42, Roger Pau Monne wrote:
In ACPI systems, the OS can direct power management, as opposed to the
firmware. This OS-directed Power Management is called OSPM. Part of
telling the firmware that the OS going to direct power management is
making ACPI "_PDC" (Processor Driver Capabili
flight 179716 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/179716/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
Add sve_vl_bits field to arch_domain and sve_vl field to
xen_arch_domainconfig struct, to allow the domain to have an
information about the SVE feature and the number of SVE register
bits that are allowed for this domain.
sve_vl field is the vector length in bits divided by 128, this
allows to use
Enable Xen to handle the SVE extension, add code in cpufeature module
to handle ZCR SVE register, disable trapping SVE feature on system
boot only when SVE resources are accessed.
While there, correct coding style for the comment on coprocessor
trapping.
Now cptr_el2 is part of the domain context
When a guest is allowed to use SVE, expose the SVE features through
the identification registers.
Signed-off-by: Luca Fancellu
---
Changes from v2:
- no changes
Changes from v1:
- No changes
Changes from RFC:
- No changes
---
xen/arch/arm/arm64/vsysreg.c | 39 +
When the arm platform supports SVE, advertise the feature in the
field arch_capabilities in struct xen_sysctl_physinfo by encoding
the SVE vector length in it.
Signed-off-by: Luca Fancellu
---
Changes from v2:
- Remove XEN_SYSCTL_PHYSCAP_ARM_SVE_SHFT, use MASK_INSR and
protect with ifdef XEN_
SVE has a new exception class with code 0x19, introduce the new code
and handle the exception.
Signed-off-by: Luca Fancellu
---
Changes from v2:
- No changes
Changes from v1:
- No changes
Changes from RFC:
- No changes
---
xen/arch/arm/include/asm/processor.h | 1 +
xen/arch/arm/traps.c
On Arm, the SVE vector length is encoded in arch_capabilities field
of struct xen_sysctl_physinfo, make use of this field in the tools
when building for arm.
Signed-off-by: Luca Fancellu
---
Changes from v2:
- rename arm_arch_capabilities.h in arm-arch-capabilities.h, use
MASK_EXTR.
- Now ar
This serie is introducing the possibility for Dom0 and DomU guests to use
sve/sve2 instructions.
SVE feature introduces new instruction and registers to improve performances on
floating point operations.
The SVE feature is advertised using the ID_AA64PFR0_EL1 register, SVE field, and
when availab
Add a command line parameter to allow Dom0 the use of SVE resources,
the command line parameter dom0_sve controls the feature on this
domain and sets the maximum SVE vector length for Dom0.
Signed-off-by: Luca Fancellu
---
Changes from v2:
- xen_domctl_createdomain field has changed into sve_vl
Add a device tree property in the dom0less domU configuration
to enable the guest to use SVE.
Update documentation.
Signed-off-by: Luca Fancellu
---
Changes from v2:
- xen_domctl_createdomain field name has changed into sve_vl
and its value is the VL/128, use domainconfig_encode_vl
to enc
Add sve parameter in XL configuration to allow guests to use
SVE feature.
Signed-off-by: Luca Fancellu
Acked-by: George Dunlap
---
Changes from v2:
- domain configuration field name has changed to sve_vl,
also its value now is VL/128.
- Add Ack-by George for the Golang bits
Changes from v1:
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 memory depends on
how many bits is the vector length for the domain and how many bits
are supported by the platform.
Save P0
On 30.11.22 16:09, 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 implemen
On 15.02.23 09:31, Jan Beulich wrote:
On 15.02.2023 01:07, Boris Ostrovsky wrote:
On 2/14/23 6:53 PM, Boris Ostrovsky wrote:
On 2/14/23 11:13 AM, Jan Beulich wrote:
--- a/arch/x86/kernel/cpu/bugs.c
+++ b/arch/x86/kernel/cpu/bugs.c
@@ -18,6 +18,8 @@
#include
#include
+#include
+
On 17/03/2023 1:56 pm, Juergen Gross wrote:
> On 15.02.23 09:31, Jan Beulich wrote:
>> On 15.02.2023 01:07, Boris Ostrovsky wrote:
>>>
>>> On 2/14/23 6:53 PM, Boris Ostrovsky wrote:
On 2/14/23 11:13 AM, Jan Beulich wrote:
> --- a/arch/x86/kernel/cpu/bugs.c
> +++ b/arch/x86/ke
On 17.03.23 15:21, Andrew Cooper wrote:
On 17/03/2023 1:56 pm, Juergen Gross wrote:
On 15.02.23 09:31, Jan Beulich wrote:
On 15.02.2023 01:07, Boris Ostrovsky wrote:
On 2/14/23 6:53 PM, Boris Ostrovsky wrote:
On 2/14/23 11:13 AM, Jan Beulich wrote:
--- a/arch/x86/kernel/cpu/bugs.c
+++ b/a
On Thu, Apr 15, 2021 at 11:47:42AM +0200, Jan Beulich wrote:
> There are three noteworthy drawbacks:
> 1) The intercepts we need to enable here are CPL-independent, i.e. we
>now have to emulate certain instructions for ring 0.
> 2) On VMX there's no intercept for SMSW, so the emulation isn't re
On Thu, Mar 16, 2023 at 7:09 PM Stefano Stabellini
wrote:
>
> On Thu, 16 Mar 2023, Juergen Gross wrote:
> > On 16.03.23 14:53, Alex Deucher wrote:
> > > On Thu, Mar 16, 2023 at 9:48 AM Juergen Gross wrote:
> > > >
> > > > On 16.03.23 14:45, Alex Deucher wrote:
> > > > > On Thu, Mar 16, 2023 at 3:
On 17.03.2023 11:05, Roger Pau Monné wrote:
> On Thu, Mar 16, 2023 at 05:56:00PM +0100, Jan Beulich wrote:
>> On 16.03.2023 17:48, Roger Pau Monné wrote:
>>> On Thu, Mar 16, 2023 at 05:43:18PM +0100, Jan Beulich wrote:
On 16.03.2023 17:39, Roger Pau Monné wrote:
> On Thu, Mar 16, 2023 at 0
On 17.03.2023 13:37, George Dunlap wrote:
> On Fri, Mar 17, 2023 at 8:46 AM Jan Beulich wrote:
>
>> On 16.03.2023 18:16, Marek Marczykowski-Górecki wrote:
>>> Python2 is not supported anymore.
>>
>> There are two things here which concern me: For one, how come this is
>> at the end of a series? Y
On 17.03.2023 10:32, Michal Orzel wrote:
>
>
> On 17/03/2023 09:36, Jan Beulich wrote:
>>
>>
>> On 16.03.2023 23:59, Stefano Stabellini wrote:
>>> On Thu, 16 Mar 2023, Jan Beulich wrote:
On 16.03.2023 11:26, Michal Orzel wrote:
> --- a/xen/drivers/char/console.c
> +++ b/xen/drivers/c
On 17.03.2023 10:23, Oleksii wrote:
> On Thu, 2023-03-16 at 12:26 +0100, Jan Beulich wrote:
>> On 15.03.2023 18:21, Oleksii Kurochko wrote:
>>> --- /dev/null
>>> +++ b/xen/common/bug.c
>>> @@ -0,0 +1,108 @@
>>> +#include
>>> +#include
>>> +#include
>>> +#include
>>> +#include
>>> +#include
>>
On 17.03.2023 15:29, Roger Pau Monné wrote:
> On Thu, Apr 15, 2021 at 11:47:42AM +0200, Jan Beulich wrote:
>> There are three noteworthy drawbacks:
>> 1) The intercepts we need to enable here are CPL-independent, i.e. we
>>now have to emulate certain instructions for ring 0.
>> 2) On VMX there'
flight 179720 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/179720/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
On Fri, Mar 17, 2023 at 04:01:59PM +0100, Jan Beulich wrote:
> On 17.03.2023 15:29, Roger Pau Monné wrote:
> > On Thu, Apr 15, 2021 at 11:47:42AM +0200, Jan Beulich wrote:
> >> There are three noteworthy drawbacks:
> >> 1) The intercepts we need to enable here are CPL-independent, i.e. we
> >>n
On Mon, Jul 20, 2020 at 01:11:18PM +0200, Roger Pau Monné wrote:
> On Wed, Jul 15, 2020 at 01:57:07PM +0200, Jan Beulich wrote:
> > ... in order to also intercept accesses through the alias ports.
> >
> > Also stop intercepting accesses to the CMOS ports if we won't ourselves
> > use the CMOS RTC.
flight 179711 linux-5.4 real [real]
flight 179722 linux-5.4 real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/179711/
http://logs.test-lab.xenproject.org/osstest/logs/179722/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
t
On 17/03/2023 2:29 pm, Roger Pau Monné wrote:
> On Thu, Apr 15, 2021 at 11:47:42AM +0200, Jan Beulich wrote:
>> There are three noteworthy drawbacks:
>> 1) The intercepts we need to enable here are CPL-independent, i.e. we
>>now have to emulate certain instructions for ring 0.
>> 2) On VMX ther
This takes care of the issue of APIC errors tending to occur on multiple
cores at one. In turn this tends to causes the error messages to be
merged together, making understanding them difficult.
Signed-off-by: Elliott Mitchell
---
xen/arch/x86/apic.c | 22 +-
1 file changed,
flight 179702 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/179702/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-freebsd12-amd64 13 guest-start fail REGR. vs. 178042
test-amd64-amd64-xl
On Fri, Mar 17, 2023 at 09:22:09AM +0100, Jan Beulich wrote:
> On 16.03.2023 23:03, Elliott Mitchell wrote:
> > On Mon, Mar 13, 2023 at 08:01:02AM +0100, Jan Beulich wrote:
> >> On 11.03.2023 01:09, Elliott Mitchell wrote:
> >>> On Thu, Mar 09, 2023 at 10:03:23AM +0100, Jan Beulich wrote:
>
>
The pull request you sent on Fri, 17 Mar 2023 07:40:23 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for-linus-6.3-rc3-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0eb392ec095ee29b932985deefb43e6d86d8a463
Thank you!
--
Deet-doot-dot, I
flight 179706 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/179706/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt-xsm 15 migrate-support-checkfail never pass
test-amd64-i386-libvirt-xsm 15 migrate-s
On Fri, 17 Mar 2023, Roger Pau Monné wrote:
> On Fri, Mar 17, 2023 at 09:39:52AM +0100, Jan Beulich wrote:
> > On 17.03.2023 00:19, Stefano Stabellini wrote:
> > > On Thu, 16 Mar 2023, Jan Beulich wrote:
> > >> So yes, it then all boils down to that Linux-
> > >> internal question.
> > >
> > > Exc
On Fri, Mar 17, 2023 at 11:15:37AM -0700, Stefano Stabellini wrote:
> On Fri, 17 Mar 2023, Roger Pau Monné wrote:
> > On Fri, Mar 17, 2023 at 09:39:52AM +0100, Jan Beulich wrote:
> > > On 17.03.2023 00:19, Stefano Stabellini wrote:
> > > > On Thu, 16 Mar 2023, Jan Beulich wrote:
> > > >> So yes, it
Using a somewhat distinct strategy with the printk(). This is two
patches, since nominally the first can work with other strategies. I
could see them being squashed during commit to the main repository.
Elliott Mitchell (2):
x86/APIC: include full string with error_interrupt() error messages
Rather than adding ", " with each printf(), simply include them in the
string initially.
Signed-off-by: Elliott Mitchell
---
xen/arch/x86/apic.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/xen/arch/x86/apic.c b/xen/arch/x86/apic.c
index f71474d47d..8cfb
This takes care of the issue of APIC errors tending to occur on multiple
cores at one. In turn this tends to causes the error messages to be
merged together, making understanding them difficult.
Signed-off-by: Elliott Mitchell
---
xen/arch/x86/apic.c | 11 ++-
1 file changed, 6 insertio
On Fri, 17 Mar 2023, Roger Pau Monné wrote:
> On Fri, Mar 17, 2023 at 11:15:37AM -0700, Stefano Stabellini wrote:
> > On Fri, 17 Mar 2023, Roger Pau Monné wrote:
> > > On Fri, Mar 17, 2023 at 09:39:52AM +0100, Jan Beulich wrote:
> > > > On 17.03.2023 00:19, Stefano Stabellini wrote:
> > > > > On Th
flight 179708 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/179708/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt 14 guest-start fail REGR. vs. 179518
test-amd64-i386-l
On Fri, 17 Mar 2023, Marek Marczykowski-Górecki wrote:
> It will be used in tests added in subsequent patches.
> Enable config options needed for those tests.
Thanks for the patch! Looks great.
Can you also remove the old 5.10.74 Dockerfile
(automation/tests-artifacts/kernel/5.10.74.dockerfile),
flight 179730 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/179730/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf b17a3a133b18fb41493fba7d86e9b5804ea6a8cf
baseline version:
ovmf 410ca0ff94a42ee541dd6
On Fri, 17 Mar 2023, Marek Marczykowski-Górecki wrote:
> This is a first test using Qubes OS CI infra. The gitlab-runner has
> access to ssh-based control interface (control@thor.testnet, ssh key
> exposed to the test via ssh-agent) and pre-configured HTTP dir for boot
> files (mapped under /scratc
On Sun, 12 Mar 2023, Huang Rui wrote:
> The xen_map_cache function wants to pass offset and size of this memory
> block as the input parameters to map the host virtual address. However,
> block->offset is too large as 0x1 (4G), if we assign the size as
> block->max_length (0x11000), the
On Sun, 12 Mar 2023, Huang Rui wrote:
> Introduce xen_ram_block_check function to check whether current ramblock
> is xen ram memory.
>
> Signed-off-by: Huang Rui
> ---
> hw/i386/xen/xen-hvm.c | 15 +++
> include/hw/xen/xen.h | 1 +
> 2 files changed, 16 insertions(+)
>
> diff --g
On Fri, Mar 17, 2023 at 04:10:22PM -0700, Stefano Stabellini wrote:
> On Fri, 17 Mar 2023, Marek Marczykowski-Górecki wrote:
> > This is a first test using Qubes OS CI infra. The gitlab-runner has
> > access to ssh-based control interface (control@thor.testnet, ssh key
> > exposed to the test via s
flight 179717 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/179717/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-qemuu-debianhvm-amd64 7 xen-install fail in 179697 pass in
179717
test-amd64-i386-examine-u
flight 179725 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/179725/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qcow2 21 guest-start/debian.repeat fail REGR. vs. 179598
Tests which are faili
76 matches
Mail list logo
