flight 175665 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175665/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-xsm 8 xen-boot fail REGR. vs. 173462
On Mon, Jan 9, 2023 at 4:28 PM Alistair Francis
wrote:
> On Tue, Jan 10, 2023 at 1:47 AM Oleksii Kurochko
> wrote:
> >
> > The patch introduces a basic stuff of early_printk functionality
> > which will be enough to print 'hello from C environment".
> > early_printk() function was changed in
Intel specifies that the Intel IGD must occupy slot 2 on the PCI bus,
as noted in docs/igd-assign.txt in the Qemu source code.
Currently, when the xl toolstack is used to configure a Xen HVM guest with
Intel IGD passthrough to the guest with the Qemu upstream device model,
a Qemu emulated PCI
flight 175683 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175683/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 2cc6d4c8ed54e36fd9638dafdb293dd9a4c54cf9
baseline version:
ovmf
On 1/10/2023 12:27 AM, Michael S. Tsirkin wrote:
> On Mon, Jan 09, 2023 at 07:05:35PM -0500, Chuck Zmudzinski wrote:
> > On 1/9/23 6:33 PM, Michael S. Tsirkin wrote:
> > > On Mon, Jan 09, 2023 at 04:55:42PM -0500, Chuck Zmudzinski wrote:
> > >> Intel specifies that the Intel IGD must occupy slot 2
On 10.01.23 06:47, Juergen Gross wrote:
On 09.01.23 19:28, Michael Kelley (LINUX) wrote:
I've come across a case with a VM running on Hyper-V that doesn't get
MTRRs, but the PAT is functional. (This is a Confidential VM using
AMD's SEV-SNP encryption technology with the vTOM option.) In this
On 09.01.23 19:28, Michael Kelley (LINUX) wrote:
I've come across a case with a VM running on Hyper-V that doesn't get
MTRRs, but the PAT is functional. (This is a Confidential VM using
AMD's SEV-SNP encryption technology with the vTOM option.) In this
case, the changes in commit 72cbc8f04fe2
On Mon, Jan 09, 2023 at 09:11:22PM -0500, Chuck Zmudzinski wrote:
> On 1/9/2023 7:05 PM, Chuck Zmudzinski wrote:
> > On 1/9/23 6:33 PM, Michael S. Tsirkin wrote:
> > > On Mon, Jan 09, 2023 at 04:55:42PM -0500, Chuck Zmudzinski wrote:
> > >> Intel specifies that the Intel IGD must occupy slot 2 on
On Mon, Jan 09, 2023 at 07:05:35PM -0500, Chuck Zmudzinski wrote:
> On 1/9/23 6:33 PM, Michael S. Tsirkin wrote:
> > On Mon, Jan 09, 2023 at 04:55:42PM -0500, Chuck Zmudzinski wrote:
> >> Intel specifies that the Intel IGD must occupy slot 2 on the PCI bus,
> >> as noted in docs/igd-assign.txt in
flight 175672 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175672/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 175623
build-amd64
> -Original Message-
> From: Julien Grall
> Sent: Tuesday, January 10, 2023 2:23 AM
> To: Penny Zheng ; xen-devel@lists.xenproject.org
> Cc: Wei Chen ; Stefano Stabellini
> ; Bertrand Marquis ;
> Volodymyr Babchuk
> Subject: Re: [PATCH v1 06/13] xen/arm: assign shared memory to owner
>
On Mon, 9 Jan 2023, Oleksii Kurochko wrote:
> Add check if there is a message 'Hello from C env' presents
> in log file to be sure that stack is set and C part of early printk
> is working.
>
> Signed-off-by: Oleksii Kurochko
> ---
> Changes in V2:
> - Move changes in the dockerfile to
On 1/9/2023 7:05 PM, Chuck Zmudzinski wrote:
> On 1/9/23 6:33 PM, Michael S. Tsirkin wrote:
> > On Mon, Jan 09, 2023 at 04:55:42PM -0500, Chuck Zmudzinski wrote:
> >> Intel specifies that the Intel IGD must occupy slot 2 on the PCI bus,
> >> as noted in docs/igd-assign.txt in the Qemu source code.
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 git://git.qemu.org/qemu.git
Tree: seabios git://xenbits.xen.org/osstest/seabios.git
Tree: xen
On Tue, Jan 10, 2023 at 1:47 AM Oleksii Kurochko
wrote:
>
> Signed-off-by: Oleksii Kurochko
Reviewed-by: Alistair Francis
Alistair
> ---
> xen/arch/riscv/riscv64/head.S | 4 +---
> xen/arch/riscv/setup.c| 12
> 2 files changed, 13 insertions(+), 3 deletions(-)
>
> diff
On Tue, Jan 10, 2023 at 1:47 AM Oleksii Kurochko
wrote:
>
> The patch introduces a basic stuff of early_printk functionality
> which will be enough to print 'hello from C environment".
> early_printk() function was changed in comparison with original as
> common isn't being built now so there is
flight 175664 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175664/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 175623
build-amd64
On 1/9/23 6:35 PM, Michael S. Tsirkin wrote:
> On Mon, Jan 09, 2023 at 06:28:44PM -0500, Chuck Zmudzinski wrote:
>> On 1/9/23 5:33 PM, Michael S. Tsirkin wrote:
>> > On Mon, Jan 09, 2023 at 04:55:42PM -0500, Chuck Zmudzinski wrote:
>> >> Intel specifies that the Intel IGD must occupy slot 2 on the
On 1/9/23 6:33 PM, Michael S. Tsirkin wrote:
> On Mon, Jan 09, 2023 at 04:55:42PM -0500, Chuck Zmudzinski wrote:
>> Intel specifies that the Intel IGD must occupy slot 2 on the PCI bus,
>> as noted in docs/igd-assign.txt in the Qemu source code.
>>
>> Currently, when the xl toolstack is used to
flight 175651 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175651/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-vhd 21 guest-start/debian.repeatfail like 175624
On Mon, Jan 09, 2023 at 06:28:44PM -0500, Chuck Zmudzinski wrote:
> On 1/9/23 5:33 PM, Michael S. Tsirkin wrote:
> > On Mon, Jan 09, 2023 at 04:55:42PM -0500, Chuck Zmudzinski wrote:
> >> Intel specifies that the Intel IGD must occupy slot 2 on the PCI bus,
> >> as noted in docs/igd-assign.txt in
On Mon, Jan 09, 2023 at 04:55:42PM -0500, Chuck Zmudzinski wrote:
> Intel specifies that the Intel IGD must occupy slot 2 on the PCI bus,
> as noted in docs/igd-assign.txt in the Qemu source code.
>
> Currently, when the xl toolstack is used to configure a Xen HVM guest with
> Intel IGD
On 1/9/23 5:33 PM, Michael S. Tsirkin wrote:
> On Mon, Jan 09, 2023 at 04:55:42PM -0500, Chuck Zmudzinski wrote:
>> Intel specifies that the Intel IGD must occupy slot 2 on the PCI bus,
>> as noted in docs/igd-assign.txt in the Qemu source code.
>>
>> Currently, when the xl toolstack is used to
branch xen-unstable
xenbranch xen-unstable
job build-i386
testid xen-build
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tree: qemuu git://git.qemu.org/qemu.git
Tree: seabios git://xenbits.xen.org/osstest/seabios.git
Tree: xen
It is possible for the administrator to manually specify the virtual
slot addresses of passed through pci devices on the guest's pci bus
using the @VSLOT parameter in xl.cfg. With this patch, libxl will by
default assign the Intel IGD to slot 2 when gfx_passthru is configured
for the Intel IGD so
By default, except for the ich9-usb-uhci device which libxl assigns to
slot 29 (0xid), libxl defers to qemu upstream's automatic slot assignment
process, which is simply to assign each emulated device to the next
available slot on the pci bus. With this default behavior, libxl and
qemu will not
The default qemu upstream "xenfv" machine type that is used when an HVM
guest is configured for Intel IGD passthrough assigns slot 2 to the
xen platform pci device. It is a requirement that slot 2 be assigned to
the Intel IGD when it is passed through as the primary graphics adapter.
Using the
Sorry for the length of this cover letter but it is helpful to put all
the pros and cons of the two different approaches to solving the problem
of configuring the Intel IGD with qemu upstream and libxl in one place,
which I attempt to do here. Of course the other approach involves a
patch to qemu
On Mon, Jan 09, 2023 at 04:55:42PM -0500, Chuck Zmudzinski wrote:
> Intel specifies that the Intel IGD must occupy slot 2 on the PCI bus,
> as noted in docs/igd-assign.txt in the Qemu source code.
>
> Currently, when the xl toolstack is used to configure a Xen HVM guest with
> Intel IGD
flight 175642 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175642/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-xsm 8 xen-boot fail REGR. vs. 173462
Intel specifies that the Intel IGD must occupy slot 2 on the PCI bus,
as noted in docs/igd-assign.txt in the Qemu source code.
Currently, when the xl toolstack is used to configure a Xen HVM guest with
Intel IGD passthrough to the guest with the Qemu upstream device model,
a Qemu emulated PCI
flight 175653 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175653/
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 175654 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175654/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 175623
build-amd64
flight 175655 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175655/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 33a3408fbbf988aaa8ecc6e721cf83e3ae810e54
baseline version:
ovmf
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 git://git.qemu.org/qemu.git
Tree: seabios git://xenbits.xen.org/osstest/seabios.git
Tree: xen
On Mon, 2023-01-09 at 17:53 +, Andrew Cooper wrote:
> On 09/01/2023 9:50 am, Oleksii Kurochko wrote:
> > qemu-system-riscv will be used to run RISC-V Xen binary and
> > gather logs for smoke tests.
> >
> > Signed-off-by: Oleksii Kurochko
>
> I've committed this, and rebuilt the container.
I've come across a case with a VM running on Hyper-V that doesn't get
MTRRs, but the PAT is functional. (This is a Confidential VM using
AMD's SEV-SNP encryption technology with the vTOM option.) In this
case, the changes in commit 72cbc8f04fe2 ("x86/PAT: Have pat_enabled()
properly reflect
Hi Penny,
On 09/01/2023 11:58, Penny Zheng wrote:
-Original Message-
From: Julien Grall
Sent: Monday, January 9, 2023 6:58 PM
To: Penny Zheng ; xen-devel@lists.xenproject.org
Cc: Wei Chen ; Stefano Stabellini
; Bertrand Marquis ;
Volodymyr Babchuk
Subject: Re: [PATCH v1 06/13]
flight 175647 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175647/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 175623
build-amd64
On 09/01/2023 9:50 am, Oleksii Kurochko wrote:
> qemu-system-riscv will be used to run RISC-V Xen binary and
> gather logs for smoke tests.
>
> Signed-off-by: Oleksii Kurochko
I've committed this, and rebuilt the container. Subsequent Gitlab-CI
runs should be able to run the RISC-V smoke tests.
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 git://git.qemu.org/qemu.git
Tree: seabios git://xenbits.xen.org/osstest/seabios.git
Tree: xen
flight 175644 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175644/
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 21/12/2021 12:18 pm, Jan Beulich wrote:
> On 16.12.2021 10:54, Andrew Cooper wrote:
>> With all infrastructure in place, advertise the PKS CPUID bit to guests, and
>> let them set CR4.PKS.
>>
>> Experiment with a tweak to the layout of hvm_cr4_guest_valid_bits() so future
>> additions will be
On 21/12/2021 11:56 am, Jan Beulich wrote:
> On 16.12.2021 10:54, Andrew Cooper wrote:
>> @@ -42,4 +45,49 @@ static inline void wrpkru(uint32_t pkru)
>> :: "a" (pkru), "d" (0), "c" (0) );
>> }
>>
>> +/*
>> + * Xen does not use PKS.
>> + *
>> + * Guest kernel use is expected
On Thu, Dec 8, 2022 at 2:26 PM George Dunlap
wrote:
>
>
> On Thu, Dec 8, 2022 at 1:58 PM Julien Grall wrote:
>
>> Hi George,
>>
>> On 08/12/2022 10:49, George Dunlap wrote:
>> > From: George Dunlap
>> >
>> > There was a question raised recently about the requriements for
>>
>> Typo:
On 09.01.2023 15:57, Andrew Cooper wrote:
> On 21/12/2021 11:28 am, Jan Beulich wrote:
>> On 16.12.2021 10:54, Andrew Cooper wrote:
>>> --- /dev/null
>>> +++ b/xen/arch/x86/include/asm/prot-key.h
>>> @@ -0,0 +1,45 @@
>>>
On 09.01.2023 16:46, Oleksii Kurochko wrote:
> --- a/xen/arch/riscv/Kconfig.debug
> +++ b/xen/arch/riscv/Kconfig.debug
> @@ -0,0 +1,7 @@
> +config EARLY_PRINTK
> +bool "Enable early printk config"
Nit: Stray "config" in the prompt text.
Jan
On Thu, Jan 5, 2023 at 10:56 PM Andrew Cooper wrote:
> > diff --git a/xen/arch/x86/cpu/microcode/private.h
> > b/xen/arch/x86/cpu/microcode/private.h
> > index 73b095d5bf..c4c6729f56 100644
> > --- a/xen/arch/x86/cpu/microcode/private.h
> > +++ b/xen/arch/x86/cpu/microcode/private.h
> > @@ -7,6
On 09.01.2023 16:46, Oleksii Kurochko wrote:
> --- a/xen/arch/riscv/include/asm/config.h
> +++ b/xen/arch/riscv/include/asm/config.h
> @@ -43,6 +43,8 @@
>
> #define SMP_CACHE_BYTES (1 << 6)
>
> +#define STACK_SIZE (PAGE_SIZE)
Btw, nit: No need for parentheses here.
Jan
On Mon, Jan 09, 2023 at 12:37:34PM +0100, Jan Beulich wrote:
> On 07.01.2023 23:07, Demi Marie Obenour wrote:
> > --- a/xen/arch/x86/Kconfig
> > +++ b/xen/arch/x86/Kconfig
> > @@ -227,6 +227,39 @@ config XEN_ALIGN_2M
> >
> > endchoice
> >
> > +config LINUX_PAT
> > + bool "Use Linux's PAT
Hi,
On 09/01/2023 15:46, Oleksii Kurochko wrote:
The patch introduces and sets up a stack in order to go to C environment
Signed-off-by: Oleksii Kurochko
It looks like the comments from Andrew were missed.
---
Changes in V2:
- introduce STACK_SIZE define.
- use consistent
Hi,
On 09/01/2023 15:46, Oleksii Kurochko wrote:
The patch introduces a basic stuff of early_printk functionality
which will be enough to print 'hello from C environment".
early_printk() function was changed in comparison with original as
common isn't being built now so there is no vscnprintf.
flight 175638 libvirt real [real]
flight 175645 libvirt real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/175638/
http://logs.test-lab.xenproject.org/osstest/logs/175645/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
Hi,
On 09/01/2023 15:46, Oleksii Kurochko wrote:
The patch introduce sbi_putchar() SBI call which is necessary
to implement initial early_printk
Signed-off-by: Oleksii Kurochko
---
Changes in V2:
- add an explanatory comment about sbi_console_putchar() function.
- order the files
On 09.01.2023 16:46, Oleksii Kurochko wrote:
> --- /dev/null
> +++ b/xen/arch/riscv/include/asm/sbi.h
> @@ -0,0 +1,34 @@
> +/* SPDX-License-Identifier: (GPL-2.0-or-later) */
> +/*
> + * Copyright (c) 2021 Vates SAS.
> + *
> + * Taken from xvisor, modified by Bobby Eshleman
Signed-off-by: Oleksii Kurochko
---
xen/arch/riscv/riscv64/head.S | 4 +---
xen/arch/riscv/setup.c| 12
2 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/xen/arch/riscv/riscv64/head.S b/xen/arch/riscv/riscv64/head.S
index c1f33a1934..d444dd8aad 100644
---
should be included because second argument of
early_puts has type 'size_t' which is defined in
Signed-off-by: Oleksii Kurochko
Acked-by: Julien Grall
---
Changes in V2:
- add Acked-by: Julien Grall
---
xen/include/xen/early_printk.h | 2 ++
1 file changed, 2 insertions(+)
diff --git
Signed-off-by: Oleksii Kurochko
---
Changes in V2:
- Remove unneeded now types from
---
xen/arch/riscv/include/asm/types.h | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 xen/arch/riscv/include/asm/types.h
diff --git a/xen/arch/riscv/include/asm/types.h
The patch introduces a basic stuff of early_printk functionality
which will be enough to print 'hello from C environment".
early_printk() function was changed in comparison with original as
common isn't being built now so there is no vscnprintf.
Because printk() relies on a serial driver (like
Add check if there is a message 'Hello from C env' presents
in log file to be sure that stack is set and C part of early printk
is working.
Signed-off-by: Oleksii Kurochko
---
Changes in V2:
- Move changes in the dockerfile to separate patch and send it to
mailing list separately:
The following patches require which includes
Signed-off-by: Oleksii Kurochko
---
Changes in V2:
- Add explanation comment to the comment message
---
xen/arch/riscv/include/asm/init.h | 12
1 file changed, 12 insertions(+)
create mode 100644 xen/arch/riscv/include/asm/init.h
The patch introduce sbi_putchar() SBI call which is necessary
to implement initial early_printk
Signed-off-by: Oleksii Kurochko
---
Changes in V2:
- add an explanatory comment about sbi_console_putchar() function.
- order the files alphabetically in Makefile
---
xen/arch/riscv/Makefile
The patch introduces and sets up a stack in order to go to C environment
Signed-off-by: Oleksii Kurochko
---
Changes in V2:
- introduce STACK_SIZE define.
- use consistent padding between instruction mnemonic and operand(s)
---
xen/arch/riscv/Makefile | 1 +
The patch series introduces the following:
- the minimal set of headers and changes inside them.
- SBI (RISC-V Supervisor Binary Interface) things necessary for basic
early_printk implementation.
- things needed to set up the stack.
- early_printk() function to print only strings.
- RISC-V smoke
flight 175643 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175643/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 175623
build-amd64
Commit 3f4c8211d982 ("x86/mm: Use mm_alloc() in poking_init()") broke
the kernel for running as Xen PV guest.
It seems as if the new address space is never activated before being
used, resulting in Xen rejecting to accept the new CR3 value (the PGD
isn't pinned).
Fix that by adding the now
On 16.12.22 15:58, Juergen Gross wrote:
Some small cleanup patches I had lying around for some time now.
Juergen Gross (4):
xen/blkback: fix white space code style issues
xen/blkback: remove stale prototype
xen/blkback: simplify free_persistent_gnts() interface
xen/blkback: move
On 21/12/2021 11:28 am, Jan Beulich wrote:
> On 16.12.2021 10:54, Andrew Cooper wrote:
>> --- /dev/null
>> +++ b/xen/arch/x86/include/asm/prot-key.h
>> @@ -0,0 +1,45 @@
>> +/**
>> + * arch/x86/include/asm/spec_ctrl.h
>> +
> On 9 Jan 2023, at 11:41, Jan Beulich wrote:
>
> On 09.01.2023 12:15, Michal Orzel wrote:
>> On 06/01/2023 11:41, Luca Fancellu wrote:
>>> Sort alphabetically cppcheck report entries when producing the text
>>> report, this will help comparing different reports and will group
>>> together
On 07.01.2023 23:07, Demi Marie Obenour wrote:
> @@ -6412,6 +6414,100 @@ static void __init __maybe_unused
> build_assertions(void)
> * using different PATs will not work.
> */
> BUILD_BUG_ON(XEN_MSR_PAT != 0x050100070406ULL);
> +
> +/*
> + * _PAGE_WB must be zero. Linux
On 07.01.2023 23:07, Demi Marie Obenour wrote:
> Setting cacheability flags that are not ones specified by Xen is a bug
> in the guest. By default, return -EINVAL if a guests attempts to do
> this. The invalid-cacheability= Xen command-line flag allows the
> administrator to allow such attempts
There's no need for this as struct domain starts out zero-filled.
Signed-off-by: Jan Beulich
Reviewed-by: Andrew Cooper
---
v2: Re-base over changes earlier in the series.
--- a/xen/arch/x86/mm/shadow/common.c
+++ b/xen/arch/x86/mm/shadow/common.c
@@ -64,12 +64,8 @@ int
The hook isn't mode dependent, hence it's misplaced in struct
paging_mode. (Or alternatively I see no reason why the alloc_page() and
free_page() hooks don't also live there.) Move it to struct
paging_domain.
The hook also is used for HVM guests only, so make respective pieces
conditional upon
The hook isn't mode dependent, hence it's misplaced in struct
paging_mode. (Or alternatively I see no reason why the alloc_page() and
free_page() hooks don't also live there.) Move it to struct
paging_domain.
Signed-off-by: Jan Beulich
---
v2: Undo rename (plural -> singular). Add a comment in
The fixes for XSA-410 have arranged for P2M pages being freed by P2M
code to be properly freed directly, rather than being put back on the
paging pool list. Therefore whatever p2m_teardown() may return will no
longer need taking care of here. Drop the code, leaving the assertions
in place and
HAP does a few things beyond what's common, which are left there at
least for now. Common operations, however, are moved to
paging_final_teardown(), allowing shadow_final_teardown() to go away.
While moving (and hence generalizing) the respective SHADOW_PRINTK()
drop the logging of total_pages
Various tidying changes accumulated during that effort. They're all
functionally independent afaict, but there may be contextual
interactions between some of them.
v2 addresses review comments, which however goes as far as introducing
a new patch (2).
1: paging: fold most HAP and shadow final
flight 175637 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175637/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-credit2 broken in 175629
Tests
On Fri, 2023-01-06 at 17:16 +, Andrew Cooper wrote:
> On 20/12/2022 6:23 am, Bobby Eshleman wrote:
> > On Fri, Jan 06, 2023 at 03:14:25PM +0200, Oleksii Kurochko wrote:
> > > The patch introduce sbi_putchar() SBI call which is necessary
> > > to implement initial early_printk
> > >
> > I
There is no point repeating this calculation at runtime, especially as it is
in the fallback path of the WRSMR/RDMSR handlers.
Move the infrastructure higher in vmx.c to avoid forward declarations,
renaming last_branch_msr_get() to get_model_specific_lbr() to highlight that
these are
Ice Lake (server at least) has both Arch LBR and model-specific LBR. Sapphire
Rapids does not have model-specific LBR at all. I.e. On SPR and later,
model_specific_lbr will always be NULL, so we must make changes to avoid
reliably hitting the domain_crash().
The Arch LBR spec states that CPUs
On 9 January 2023 07:40:06 GMT, Juergen Gross wrote:
>Sorry for the late answer, but I was pretty busy before my 3 week time off. :-)
No problem, I had lots of other things to work on, including my own time off.
Hope you enjoyed it!
>On 20.12.22 13:02, David Woodhouse wrote:
>> I've been
This is the minimum bodge required to stop guests crashing on Sapphire Rapids
hardware.
Note that both Arch LBR and safely (in terms of migration) enumerating
PDCM/MSR_PERF_CAPS depend on improved MSR levelling support which is still not
yet complete.
i.e. We cannot do the second half
> -Original Message-
> From: Julien Grall
> Sent: Monday, January 9, 2023 6:58 PM
> To: Penny Zheng ; xen-devel@lists.xenproject.org
> Cc: Wei Chen ; Stefano Stabellini
> ; Bertrand Marquis ;
> Volodymyr Babchuk
> Subject: Re: [PATCH v1 06/13] xen/arm: assign shared memory to owner
>
On 05.01.2023 18:56, Andrew Cooper wrote:
> On 22/12/2022 7:51 am, Jan Beulich wrote:
>> On 21.12.2022 18:16, Andrew Cooper wrote:
>>> On 21/12/2022 1:25 pm, Jan Beulich wrote:
+ d, d->arch.paging.total_pages,
+ d->arch.paging.free_pages,
On Thu, Dec 29, 2022 at 10:34:55AM +0100, Thomas Huth wrote:
> On 19/12/2022 14.02, Daniel P. Berrangé wrote:
> > Signed-off-by: Daniel P. Berrangé
> > ---
> > tests/qtest/ahci-test.c | 3 +++
> > tests/qtest/arm-cpu-features.c| 1 +
> > tests/qtest/erst-test.c | 2
flight 175635 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175635/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 175624
test-amd64-i386-xl-qemuu-win7-amd64
On 09.01.2023 12:15, Michal Orzel wrote:
> On 06/01/2023 11:41, Luca Fancellu wrote:
>> Sort alphabetically cppcheck report entries when producing the text
>> report, this will help comparing different reports and will group
>> together findings from the same file.
>>
>> Signed-off-by: Luca
On 07.01.2023 23:07, Demi Marie Obenour wrote:
> --- a/xen/arch/x86/Kconfig
> +++ b/xen/arch/x86/Kconfig
> @@ -227,6 +227,39 @@ config XEN_ALIGN_2M
>
> endchoice
>
> +config LINUX_PAT
> + bool "Use Linux's PAT instead of Xen's default"
> + help
> + Use Linux's Page Attribute
Hi Luca,
On 06/01/2023 11:41, Luca Fancellu wrote:
>
>
> Sort alphabetically cppcheck report entries when producing the text
> report, this will help comparing different reports and will group
> together findings from the same file.
>
> Signed-off-by: Luca Fancellu
> ---
>
Hi,
On 09/01/2023 09:10, Oleksii wrote:
On Fri, 2023-01-06 at 13:51 +, Julien Grall wrote:
Hi,
On 06/01/2023 13:14, Oleksii Kurochko wrote:
The patch introduces a basic stuff of early_printk functionality
which will be enough to print 'hello from C environment"
Signed-off-by: Oleksii
On 06.01.2023 19:21, Andrew Cooper wrote:
> On SPR, MSR_DBG_CTRL.LBR is a write-discard bit. There really are no
> model specific LBRs, so we should emulate it as write discard too. More
> generally, I think we should apply that to any system were we don't know
> the model-specific indices.
>
>
Hi Oleksii,
On 09/01/2023 09:04, Oleksii wrote:
On Fri, 2023-01-06 at 13:40 +, Julien Grall wrote:
Hi,
On 06/01/2023 13:14, Oleksii Kurochko wrote:
The patch introduce sbi_putchar() SBI call which is necessary
to implement initial early_printk
Signed-off-by: Oleksii Kurochko
---
flight 175634 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/175634/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-xsm 8 xen-boot fail REGR. vs. 173462
On 09/01/2023 07:49, Penny Zheng wrote:
Hi Julien
Hi Penny,
Happy new year
Happy new year too!
-Original Message-
From: Julien Grall
Sent: Sunday, January 8, 2023 8:53 PM
To: Penny Zheng ; xen-devel@lists.xenproject.org
Cc: Wei Chen ; Stefano Stabellini
; Bertrand Marquis
Hi Penny,
On 09/01/2023 07:50, Penny Zheng wrote:
-Original Message-
From: Julien Grall
Sent: Sunday, January 8, 2023 8:23 PM
To: Penny Zheng ; xen-devel@lists.xenproject.org
Cc: Wei Chen ; Stefano Stabellini
; Bertrand Marquis ;
Volodymyr Babchuk
Subject: Re: [PATCH v1 05/13]
Hi Penny,
On 09/01/2023 07:48, Penny Zheng wrote:
-Original Message-
From: Julien Grall
Sent: Sunday, January 8, 2023 7:44 PM
To: Penny Zheng ; xen-devel@lists.xenproject.org
Cc: Wei Chen ; Stefano Stabellini
; Bertrand Marquis ;
Volodymyr Babchuk
Subject: Re: [PATCH v1 01/13]
qemu-system-riscv will be used to run RISC-V Xen binary and
gather logs for smoke tests.
Signed-off-by: Oleksii Kurochko
---
automation/build/archlinux/riscv64.dockerfile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/automation/build/archlinux/riscv64.dockerfile
On 06.01.2023 03:03, Andrew Cooper wrote:
> On 05/01/2023 4:05 pm, Jan Beulich wrote:
>> The "n" input is a GFN value and hence bounded by the physical address
>> bits in use on a system.
>
> The one case where this isn't obviously true is in sh_audit(). It comes
> from a real MFN in the system,
On 08.01.23 18:06, Julien Grall wrote:
Hello Julien, Ayan, all
Hi Ayan,
On 21/12/2022 18:53, Ayan Kumar Halder wrote:
Currently, kernel_uimage_probe() does not read the load/entry point
address
set in the uImge header. Thus, info->zimage.start is 0 (default
value). This
causes,
1 - 100 of 114 matches
Mail list logo
