[qemu-mainline test] 180546: tolerable FAIL - PUSHED

flight 180546 qemu-mainline real [real] flight 180550 qemu-mainline real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/180546/ http://logs.test-lab.xenproject.org/osstest/logs/180550/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking):

Re: [PATCH 0/1] Updated: Ensure PV ring is drained on disconenct

On Thu, 20 Apr 2023, Mark Syms wrote: > Updated patch to address intermittent SIGSEGV on domain disconnect/shutdown. > > Mark Syms (1): > Ensure the PV ring is drained on disconnect > > hw/block/dataplane/xen-block.c | 31 +-- > 1 file changed, 25 insertions(+), 6

RE: [patch V2 38/38] x86/smpboot/64: Implement arch_cpuhp_init_parallel_bringup() and enable it

From: Thomas Gleixner Sent: Thursday, May 4, 2023 12:03 PM > > Implement the validation function which tells the core code whether > parallel bringup is possible. > > The only condition for now is that the kernel does not run in an encrypted > guest as these will trap the RDMSR via #VC, which

Re: [PATCH] xen/evtchn: Introduce new IOCTL to bind static evtchn

On Fri, 28 Apr 2023, Rahul Singh wrote: > Xen 4.17 supports the creation of static evtchns. To allow user space > application to bind static evtchns introduce new ioctl > "IOCTL_EVTCHN_BIND_STATIC". Existing IOCTL doing more than binding > that’s why we need to introduce the new IOCTL to only bind

Re: [PATCH] 9pfs/xen: Fix segfault on shutdown

On Tue, 2 May 2023, Jason Andryuk wrote: > xen_9pfs_free can't use gnttabdev since it is already closed and NULL-ed > out when free is called. Do the teardown in _disconnect(). This > matches the setup done in _connect(). > > trace-events are also added for the XenDevOps functions. > >

Re: [PATCH v2 2/2] LICENSES: Remove the use of deprecated SPDX tags

On Fri, 5 May 2023, Andrew Cooper wrote: > The GPL and LGPL SPDX forms without an explicit -only or -or-later suffix are > deprecated and should not be used. Update the documention. > > Somewhat unhelpfully at the time of writing, this only appears to be indicated > by the separation of the two

Re: [PATCH 1/2] LICENSES: Improve the legibility of these files

On Fri, 5 May 2023, Jan Beulich wrote: > On 05.05.2023 15:05, Andrew Cooper wrote: > > A few newlines go a very long way > > > > Signed-off-by: Andrew Cooper > > Acked-by: Jan Beulich Although I don't mind either way it should be noted that the LICENSES files came from Linux, and Linux

[linux-linus test] 180540: regressions - FAIL

flight 180540 linux-linus real [real] flight 180548 linux-linus real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/180540/ http://logs.test-lab.xenproject.org/osstest/logs/180548/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be

[PATCH v3] ns16550: enable memory decoding on MMIO-based PCI console card

pci_serial_early_init() enables PCI_COMMAND_IO for IO-based UART devices, add setting PCI_COMMAND_MEMORY for MMIO-based UART devices too. Note the MMIO-based devices in practice need a "pci" sub-option, otherwise a few parameters are not initialized (including bar_idx, reg_shift, reg_width etc).

[PATCH v2 2/2] drivers/char: Use sub-page ro API to make just xhci dbc cap RO

Not the whole page, which may contain other registers too. In fact on Tiger Lake and newer (at least), this page do contain other registers that Linux tries to use. And with share=yes, a domU would use them too. Without this patch, PV dom0 would fail to initialize the controller, while HVM would

[PATCH v2 1/2] x86/mm: add API for marking only part of a MMIO page read only

In some cases, only few registers on a page needs to be write-protected. Examples include USB3 console (64 bytes worth of registers) or MSI-X's PBA table (which doesn't need to span the whole table either), although in the latter case the spec forbids placing other registers on the same page.

[PATCH v2 0/2] Add API for making parts of a MMIO page R/O and use it in XHCI console

On older systems, XHCI xcap had a layout that no other (interesting) registers were placed on the same page as the debug capability, so Linux was fine with making the whole page R/O. But at least on Tiger Lake and Alder Lake, Linux needs to write to some other registers on the same page too. Add

[PATCH v2 2/2] LICENSES: Remove the use of deprecated SPDX tags

The GPL and LGPL SPDX forms without an explicit -only or -or-later suffix are deprecated and should not be used. Update the documention. Somewhat unhelpfully at the time of writing, this only appears to be indicated by the separation of the two tables at https://spdx.org/licenses/ The recent

[PATCH v2 1/2] LICENSES: Improve the legibility of these files

A few newlines go a very long way. Signed-off-by: Andrew Cooper Acked-by: Jan Beulich --- CC: George Dunlap CC: Jan Beulich CC: Stefano Stabellini CC: Wei Liu CC: Julien Grall --- LICENSES/BSD-2-Clause | 4 LICENSES/BSD-3-Clause | 4 LICENSES/BSD-3-Clause-Clear | 4

[PATCH v2 0/2] LICENSES improvements/corrections

Noticed in light of the recent LGPL changes to libacpi, but sadly only after the fact. Minor updates in the second patch. Andrew Cooper (2): LICENSES: Improve the legibility of these files LICENSES: Remove the use of deprecated SPDX tags LICENSES/BSD-2-Clause | 4

[PATCH 3/3] x86: Use CpuidUserDis if an AMD HVM guest toggles CPUID faulting

This is in order to aid guests of AMD hardware that we have exposed CPUID faulting to. If they try to modify the Intel MSR that enables the feature, trigger levelling so AMD's version of it (CpuidUserDis) is used instead. Signed-off-by: Alejandro Vallejo --- xen/arch/x86/msr.c | 9 - 1

[PATCH 2/3] x86: Add support for CpuidUserDis

Includes a refactor to move vendor-specific probes to vendor-specific files. Furthermore, because CpuIdUserDis is reported in Cpuid itself, the extended leaf containing that bit must be retrieved before calling c_early_init() Signed-off-by: Alejandro Vallejo --- xen/arch/x86/cpu/amd.c |

[PATCH 0/3] Add CpuidUserDis support

Nowadays AMD supports trapping the CPUID instruction from ring3 to ring0, (CpuidUserDis) akin to Intel's "CPUID faulting". There is a difference in that the toggle bit is in a different MSR and the support bit is in CPUID itself rather than yet another MSR. This patch enables AMD hosts to use it

[PATCH 1/3] x86: Add AMD's CpuidUserDis bit definitions

AMD reports support for CpuidUserDis in CPUID and provides the toggle in HWCR. This patch adds the positions of both of those bits to both xen and tools. No functional change. Signed-off-by: Alejandro Vallejo --- tools/libs/light/libxl_cpuid.c | 1 + tools/misc/xen-cpuid.c

[libvirt test] 180539: tolerable all pass - PUSHED

flight 180539 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/180539/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt 16 saverestore-support-checkfail like 180513 test-armhf-armhf-libvirt-raw 15

Re: [PATCH v1 2/9] KVM: x86/mmu: Add support for prewrite page tracking

On Fri, May 05, 2023, Micka�l Sala�n wrote: > > On 05/05/2023 18:28, Sean Christopherson wrote: > > I have no doubt that we'll need to solve performance and scaling issues > > with the > > memory attributes implementation, e.g. to utilize xarray multi-range support > > instead of storing

Re: [PATCH v1 4/9] KVM: x86: Add new hypercall to set EPT permissions

On Fri, May 05, 2023, Micka�l Sala�n wrote: > > On 05/05/2023 18:44, Sean Christopherson wrote: > > On Fri, May 05, 2023, Micka�l Sala�n wrote: > > > Add a new KVM_HC_LOCK_MEM_PAGE_RANGES hypercall that enables a guest to > > > set EPT permissions on a set of page ranges. > > > > IMO,

Re: [PATCH v1 4/9] KVM: x86: Add new hypercall to set EPT permissions

On 05/05/2023 18:44, Sean Christopherson wrote: On Fri, May 05, 2023, Micka�l Sala�n wrote: Add a new KVM_HC_LOCK_MEM_PAGE_RANGES hypercall that enables a guest to set EPT permissions on a set of page ranges. IMO, manipulation of protections, both for memory (this patch) and CPU state

Re: [PATCH v6 09/12] tools: add physinfo arch_capabilities handling for Arm

> On 5 May 2023, at 17:44, Anthony PERARD wrote: > > On Wed, May 03, 2023 at 09:23:19AM +, Luca Fancellu wrote: >> >> >>> On 2 May 2023, at 17:13, Anthony PERARD wrote: >>> >>> On Mon, Apr 24, 2023 at 07:02:45AM +0100, Luca Fancellu wrote: diff --git

Re: [PATCH v1 2/9] KVM: x86/mmu: Add support for prewrite page tracking

On 05/05/2023 18:28, Sean Christopherson wrote: On Fri, May 05, 2023, Micka�l Sala�n wrote: diff --git a/arch/x86/include/asm/kvm_page_track.h b/arch/x86/include/asm/kvm_page_track.h index eb186bc57f6a..a7fb4ff888e6 100644 --- a/arch/x86/include/asm/kvm_page_track.h +++

Re: [PATCH v1 4/9] KVM: x86: Add new hypercall to set EPT permissions

On Fri, May 05, 2023, Micka�l Sala�n wrote: > Add a new KVM_HC_LOCK_MEM_PAGE_RANGES hypercall that enables a guest to > set EPT permissions on a set of page ranges. IMO, manipulation of protections, both for memory (this patch) and CPU state (control registers in the next patch) should come

Re: [PATCH v6 09/12] tools: add physinfo arch_capabilities handling for Arm

On Wed, May 03, 2023 at 09:23:19AM +, Luca Fancellu wrote: > > > > On 2 May 2023, at 17:13, Anthony PERARD wrote: > > > > On Mon, Apr 24, 2023 at 07:02:45AM +0100, Luca Fancellu wrote: > >> diff --git a/tools/include/xen-tools/arm-arch-capabilities.h > >>

Re: [PATCH v6 10/12] xen/tools: add sve parameter in XL configuration

> On 5 May 2023, at 17:23, Anthony PERARD wrote: > > On Tue, May 02, 2023 at 07:54:19PM +, Luca Fancellu wrote: >>> On 2 May 2023, at 18:06, Anthony PERARD wrote: >>> On Mon, Apr 24, 2023 at 07:02:46AM +0100, Luca Fancellu wrote: diff --git a/tools/libs/light/libxl_arm.c

Re: [PATCH v1 2/9] KVM: x86/mmu: Add support for prewrite page tracking

On Fri, May 05, 2023, Micka�l Sala�n wrote: > diff --git a/arch/x86/include/asm/kvm_page_track.h > b/arch/x86/include/asm/kvm_page_track.h > index eb186bc57f6a..a7fb4ff888e6 100644 > --- a/arch/x86/include/asm/kvm_page_track.h > +++ b/arch/x86/include/asm/kvm_page_track.h > @@ -3,6 +3,7 @@ >

Re: [PATCH v6 10/12] xen/tools: add sve parameter in XL configuration

On Tue, May 02, 2023 at 07:54:19PM +, Luca Fancellu wrote: > > On 2 May 2023, at 18:06, Anthony PERARD wrote: > > On Mon, Apr 24, 2023 at 07:02:46AM +0100, Luca Fancellu wrote: > >> diff --git a/tools/libs/light/libxl_arm.c b/tools/libs/light/libxl_arm.c > >> index ddc7b2a15975..1e69dac2c4fa

[ovmf test] 180545: all pass - PUSHED

flight 180545 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/180545/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf b65c0eed6bc028388d790fe4e30a76770ebb46c4 baseline version: ovmf

Re: [PATCH RFC] build: respect top-level .config also for out-of-tree hypervisor builds

On Wed, Mar 15, 2023 at 03:58:59PM +0100, Jan Beulich wrote: > With in-tree builds Config.mk includes a .config file (if present) from > the top-level directory. Similar functionality is wanted with out-of- > tree builds. Yet the concept of "top-level directory" becomes fuzzy in > that case,

Re: [PATCH 2/2] LICENSES: Remove the use of deprecated LGPL SPDX tags

On 05/05/2023 4:30 pm, Anthony PERARD wrote: > On Fri, May 05, 2023 at 02:05:33PM +0100, Andrew Cooper wrote: >> --- >> LICENSES/GPL-2.0| 12 ++-- >> LICENSES/LGPL-2.0 | 8 >> LICENSES/LGPL-2.1 | 8 >> >> diff

Re: [PATCH] 9pfs/xen: Fix segfault on shutdown

On Fri, May 5, 2023 at 6:05 AM Christian Schoenebeck wrote: > > Hi Jason, > > as this is a Xen specific change, I would like Stefano or another Xen > developer to take a look at it, just few things from my side ... > > On Tuesday, May 2, 2023 4:37:22 PM CEST Jason Andryuk wrote: > > xen_9pfs_free

Re: [PATCH v3 05/14 RESEND] xenpm: Change get-cpufreq-para output for internal

On Fri, May 5, 2023 at 3:04 AM Jan Beulich wrote: > >>> @@ -720,10 +721,15 @@ static void print_cpufreq_para(int cpuid, struct > >>> xc_get_cpufreq_para *p_cpufreq) > >>> printf(" %d", p_cpufreq->affected_cpus[i]); > >>> printf("\n"); > >>> > >>> -printf("cpuinfo frequency:

Re: [PATCH v3 04/14 RESEND] cpufreq: Add Hardware P-State (HWP) driver

On Fri, May 5, 2023 at 3:01 AM Jan Beulich wrote: > > On 04.05.2023 18:56, Jason Andryuk wrote: > > On Thu, May 4, 2023 at 9:11 AM Jan Beulich wrote: > >> On 01.05.2023 21:30, Jason Andryuk wrote: > >>> --- a/docs/misc/xen-command-line.pandoc > >>> +++ b/docs/misc/xen-command-line.pandoc > >>>

Re: [PATCH 2/2] LICENSES: Remove the use of deprecated LGPL SPDX tags

On Fri, May 05, 2023 at 02:05:33PM +0100, Andrew Cooper wrote: > --- > LICENSES/GPL-2.0| 12 ++-- > LICENSES/LGPL-2.0 | 8 > LICENSES/LGPL-2.1 | 8 > > diff --git a/LICENSES/GPL-2.0 b/LICENSES/GPL-2.0 > index

[PATCH v1 9/9] virt: Add Heki KUnit tests

This adds a new CONFIG_HEKI_TEST option to run tests at boot. Indeed, because this patch series forbids the loading of kernel modules after the boot, we need to make built-in tests. Furthermore, because we use some symbols not exported to modules (e.g., kernel_set_to_readonly) this could not

[PATCH v1 8/9] KVM: x86/mmu: Enable guests to lock themselves thanks to MBEC

This changes enable to enforce a deny-by-default execution security policy for guest kernels, leveraged by the Heki implementation. Create synthetic page faults when an access is denied by Heki. This kind of kernel page fault needs to be handled by guests, which is not currently the case, making

[PATCH v1 7/9] KVM: VMX: Add MBEC support

This changes add support for VMX_FEATURE_MODE_BASED_EPT_EXEC (named ept_mode_based_exec in /proc/cpuinfo and MBEC elsewhere), which enables to separate EPT execution bits for supervisor vs. user. It transforms the semantic of VMX_EPT_EXECUTABLE_MASK from a global execution to a kernel execution,

[PATCH v1 1/9] KVM: x86: Add kvm_x86_ops.fault_gva()

This function is needed for kvm_mmu_page_fault() to create synthetic page faults. Code originally written by Mihai Donțu and Nicușor Cîțu: https://lore.kernel.org/r/20211006173113.26445-18-ala...@bitdefender.com Renamed fault_gla() to fault_gva() and use the new EPT_VIOLATION_GVA_IS_VALID. Cc:

[PATCH v1 6/9] KVM: x86: Add Heki hypervisor support

From: Madhavan T. Venkataraman Each supported hypervisor in x86 implements a struct x86_hyper_init to define the init functions for the hypervisor. Define a new init_heki() entry point in struct x86_hyper_init. Hypervisors that support Heki must define this init_heki() function. Call

[PATCH v1 5/9] KVM: x86: Add new hypercall to lock control registers

This enables guests to lock their CR0 and CR4 registers with a subset of X86_CR0_WP, X86_CR4_SMEP, X86_CR4_SMAP, X86_CR4_UMIP, X86_CR4_FSGSBASE and X86_CR4_CET flags. The new KVM_HC_LOCK_CR_UPDATE hypercall takes two arguments. The first is to identify the control register, and the second is a

[PATCH v1 3/9] virt: Implement Heki common code

From: Madhavan T. Venkataraman Hypervisor Enforced Kernel Integrity (Heki) is a feature that will use the hypervisor to enhance guest virtual machine security. Configuration = Define the config variables for the feature. This feature depends on support from the architecture as well

[RFC PATCH v1 0/9] Hypervisor-Enforced Kernel Integrity

Hi, This patch series is a proof-of-concept that implements new KVM features (extended page tracking, MBEC support, CR pinning) and defines a new API to protect guest VMs. No VMM (e.g., Qemu) modification is required. The main idea being that kernel self-protection mechanisms should be delegated

[PATCH v1 4/9] KVM: x86: Add new hypercall to set EPT permissions

Add a new KVM_HC_LOCK_MEM_PAGE_RANGES hypercall that enables a guest to set EPT permissions on a set of page ranges. This hypercall takes three arguments. The first contains the GPA pointing to an array of struct heki_pa_range. The second argument is the size of the array, not the number of

[PATCH v1 2/9] KVM: x86/mmu: Add support for prewrite page tracking

Add a new page tracking mode to deny a page update and throw a page fault to the guest. This is useful for KVM to be able to make some pages non-writable (not read-only because it doesn't imply execution restrictions), see the next Heki commits. This kind of synthetic kernel page fault needs to

[xen-unstable test] 180537: tolerable FAIL

flight 180537 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/180537/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-i386-xl-vhd 21 guest-start/debian.repeat fail in 180528 pass in 180537

[ovmf test] 180544: all pass - PUSHED

flight 180544 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/180544/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 757f502a3b350436877102c3043744e021537c19 baseline version: ovmf

Re: [PATCH 2/2] LICENSES: Remove the use of deprecated LGPL SPDX tags

On 05/05/2023 2:31 pm, Jan Beulich wrote: > On 05.05.2023 15:22, Andrew Cooper wrote: >> On 05/05/2023 2:13 pm, Jan Beulich wrote: >>> On 05.05.2023 15:05, Andrew Cooper wrote: The SPDX forms without an explicit -only or -or-later suffix are deprecated and should not be used. >>> I guess

Re: [PATCH 2/2] LICENSES: Remove the use of deprecated LGPL SPDX tags

On 05.05.2023 15:22, Andrew Cooper wrote: > On 05/05/2023 2:13 pm, Jan Beulich wrote: >> On 05.05.2023 15:05, Andrew Cooper wrote: >>> The SPDX forms without an explicit -only or -or-later suffix are deprecated >>> and should not be used. >> I guess this wants a reference to where this is

Re: [PATCH 2/2] LICENSES: Remove the use of deprecated LGPL SPDX tags

On 05/05/2023 2:13 pm, Jan Beulich wrote: > On 05.05.2023 15:05, Andrew Cooper wrote: >> The SPDX forms without an explicit -only or -or-later suffix are deprecated >> and should not be used. > I guess this wants a reference to where this is specified. In particular ... > >> ---

Re: [PATCH 2/2] LICENSES: Remove the use of deprecated LGPL SPDX tags

On 05.05.2023 15:05, Andrew Cooper wrote: > The SPDX forms without an explicit -only or -or-later suffix are deprecated > and should not be used. I guess this wants a reference to where this is specified. In particular ... > --- a/LICENSES/LGPL-2.1 > +++ b/LICENSES/LGPL-2.1 > @@ -1,5 +1,5 @@ >

Re: [PATCH] libxl: arm: Allow grant mappings for backends running on Dom0

Hello Viresh [sorry for the possible format issues] On Fri, May 5, 2023 at 9:19 AM Viresh Kumar wrote: > On 05-04-23, 05:12, Viresh Kumar wrote: > > On 04-04-23, 21:16, Oleksandr Tyshchenko wrote: > > > ok, probably makes sense > > > > While testing both foreign and grant mappings I stumbled

Re: [PATCH 1/2] LICENSES: Improve the legibility of these files

On 05.05.2023 15:05, Andrew Cooper wrote: > A few newlines go a very long way > > Signed-off-by: Andrew Cooper Acked-by: Jan Beulich

[PATCH 2/2] LICENSES: Remove the use of deprecated LGPL SPDX tags

The SPDX forms without an explicit -only or -or-later suffix are deprecated and should not be used. The recent changes to libacpi are the only examples in tree, so fix them all up. For GPL, we have many examples using deprecated tags. For now, just identify them as such recommend that no new

[PATCH 1/2] LICENSES: Improve the legibility of these files

A few newlines go a very long way Signed-off-by: Andrew Cooper --- CC: George Dunlap CC: Jan Beulich CC: Stefano Stabellini CC: Wei Liu CC: Julien Grall --- LICENSES/BSD-2-Clause | 4 LICENSES/BSD-3-Clause | 4 LICENSES/BSD-3-Clause-Clear | 4 LICENSES/CC-BY-4.0

[PATCH 0/2] LICENSES improvements/corrections

Noticed in light of the recent LGPL changes to libacpi, but sadly only after the fact. Andrew Cooper (2): LICENSES: Improve the legibility of these files LICENSES: Remove the use of deprecated LGPL SPDX tags LICENSES/BSD-2-Clause | 4 LICENSES/BSD-3-Clause

Re: [patch V2 34/38] x86/cpu/amd; Invoke detect_extended_topology_early() on boot CPU

On Fri, May 05 2023 at 00:04, Andrew Cooper wrote: > On 04/05/2023 8:02 pm, Thomas Gleixner wrote: >> From: Thomas Gleixner >> >> The early detection stores the extended topology leaf number which is >> required for parallel hotplug. >> >> Signed-off-by: Thomas Gleixner > > It occurs to me that

Re: [PATCH v4 1/2] acpi: Make TPM version configurable.

On 05/05/2023 07:34, Jan Beulich wrote: On 04.05.2023 19:51, Jennifer Herbert wrote: This patch makes the TPM version, for which the ACPI library probes, configurable. If acpi_config.tpm_verison is set to 1, it indicates that 1.2 (TCPA) should be probed. I have also added to hvmloader an

[qemu-mainline test] 180536: tolerable FAIL - PUSHED

flight 180536 qemu-mainline real [real] flight 180543 qemu-mainline real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/180536/ http://logs.test-lab.xenproject.org/osstest/logs/180543/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking):

[xen-unstable-smoke test] 180541: tolerable all pass - PUSHED

flight 180541 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/180541/ 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

[ovmf test] 180542: all pass - PUSHED

flight 180542 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/180542/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 94c802e108a082d6f74c854bea8bd98fe7808453 baseline version: ovmf

Re: [PATCH] 9pfs/xen: Fix segfault on shutdown

Hi Jason, as this is a Xen specific change, I would like Stefano or another Xen developer to take a look at it, just few things from my side ... On Tuesday, May 2, 2023 4:37:22 PM CEST Jason Andryuk wrote: > xen_9pfs_free can't use gnttabdev since it is already closed and NULL-ed Where exactly

Re: [XEN][PATCH v6 02/19] common/device_tree: handle memory allocation failure in __unflatten_device_tree()

On 03/05/2023 01:36, Vikram Garhwal wrote: > > > Change __unflatten_device_tree() return type to integer so it can propagate > memory allocation failure. Add panic() in dt_unflatten_host_device_tree() for > memory allocation failure during boot. > > Signed-off-by: Vikram Garhwal I think we

Re: [PATCH] libxl: arm: Allow grant mappings for backends running on Dom0

Hi Anthony, On 02-05-23, 15:44, Anthony PERARD wrote: > > diff --git a/tools/libs/light/libxl_virtio.c > > b/tools/libs/light/libxl_virtio.c > > index faada49e184e..e1f15344ef97 100644 > > --- a/tools/libs/light/libxl_virtio.c > > +++ b/tools/libs/light/libxl_virtio.c > > @@ -48,11 +48,13 @@

Re: xen cache colors in ARM

Hi Oleg, Replying, so that you do not need to wait for Stefano. On 05/05/2023 10:28, Oleg Nikitenko wrote: > > > > Hello Stefano, > > I would like to try a xen cache color property from this repo  > https://xenbits.xen.org/git-http/xen.git >

[ovmf test] 180538: all pass - PUSHED

flight 180538 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/180538/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf ff7cb2d7c98f8b832180e054848459fc24a0910a baseline version: ovmf

Re: [PATCH v3 05/14 RESEND] xenpm: Change get-cpufreq-para output for internal

On 04.05.2023 19:00, Jason Andryuk wrote: > On Thu, May 4, 2023 at 10:35 AM Jan Beulich wrote: >> >> On 01.05.2023 21:30, Jason Andryuk wrote: >>> When using HWP, some of the returned data is not applicable. In that >>> case, we should just omit it to avoid confusing the user. So switch to >>>

Re: [PATCH] build: shorten macro references

Hi Jan, > On 4 May 2023, at 18:16, Jan Beulich wrote: > > Presumably by copy-and-paste we've accumulated a number of instances of > $(@D)/$(@F), which really is nothing else than $@. The split form only > needs using when we want to e.g. insert a leading . at the beginning of > the file name

Re: [PATCH v3 04/14 RESEND] cpufreq: Add Hardware P-State (HWP) driver

On 04.05.2023 18:56, Jason Andryuk wrote: > On Thu, May 4, 2023 at 9:11 AM Jan Beulich wrote: >> On 01.05.2023 21:30, Jason Andryuk wrote: >>> --- a/docs/misc/xen-command-line.pandoc >>> +++ b/docs/misc/xen-command-line.pandoc >>> @@ -499,7 +499,7 @@ If set, force use of the performance counters

Re: [PATCH v4 1/2] acpi: Make TPM version configurable.

On 04.05.2023 19:51, Jennifer Herbert wrote: > This patch makes the TPM version, for which the ACPI library probes, > configurable. > If acpi_config.tpm_verison is set to 1, it indicates that 1.2 (TCPA) should > be probed. > I have also added to hvmloader an option to allow setting this new

Re: [PATCH v1 3/6] iommu/arm: Introduce iommu_add_dt_pci_device API

On 04.05.2023 23:54, Stewart Hildebrand wrote: > On 5/2/23 03:44, Jan Beulich wrote: >> On 01.05.2023 22:03, Stewart Hildebrand wrote: >>> @@ -228,6 +229,9 @@ int iommu_release_dt_devices(struct domain *d); >>> * (IOMMU is not enabled/present or device is not connected to it). >>> */ >>>

Re: [PATCH] libxl: arm: Allow grant mappings for backends running on Dom0

On 05-04-23, 05:12, Viresh Kumar wrote: > On 04-04-23, 21:16, Oleksandr Tyshchenko wrote: > > ok, probably makes sense > > While testing both foreign and grant mappings I stumbled upon another > related problem. How do I control the creation of iommu node from > guest configuration file,

Re: [PATCH] build: shorten macro references

On 04.05.2023 19:24, Andrew Cooper wrote: > On 04/05/2023 5:16 pm, Jan Beulich wrote: >> Presumably by copy-and-paste we've accumulated a number of instances of >> $(@D)/$(@F), which really is nothing else than $@. The split form only >> needs using when we want to e.g. insert a leading . at the