Re: [PATCH 1/2] rangeset: add RANGESETF_no_print flag

On 23.11.2021 08:49, Oleksandr Andrushchenko wrote: > > > On 23.11.21 09:38, Jan Beulich wrote: >> On 22.11.2021 10:28, Oleksandr Andrushchenko wrote: >>> --- a/xen/include/xen/rangeset.h >>> +++ b/xen/include/xen/rangeset.h >>> @@ -51,6 +51,9 @@ void rangeset_limit( >>>/* Pretty-print range

Re: [PATCH 1/2] rangeset: add RANGESETF_no_print flag

On 23.11.21 10:01, Jan Beulich wrote: > On 23.11.2021 08:49, Oleksandr Andrushchenko wrote: >> >> On 23.11.21 09:38, Jan Beulich wrote: >>> On 22.11.2021 10:28, Oleksandr Andrushchenko wrote: --- a/xen/include/xen/rangeset.h +++ b/xen/include/xen/rangeset.h @@ -51,6 +51,9 @@ void r

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

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

Re: [PATCH v3] xen: detect uninitialized xenbus in xenbus_init

On 23.11.2021 06:42, Juergen Gross wrote: > On 22.11.21 23:16, Stefano Stabellini wrote: >> From: Stefano Stabellini >> >> If the xenstore page hasn't been allocated properly, reading the value >> of the related hvm_param (HVM_PARAM_STORE_PFN) won't actually return >> error. Instead, it will succe

Re: [RFC PATCH] Added the logic to decode 32 bit ldr/str post-indexing instructions

Hi Stefano, > On 23 Nov 2021, at 04:13, Stefano Stabellini wrote: > > On Mon, 22 Nov 2021, Julien Grall wrote: >> On Mon, 22 Nov 2021 at 19:59, Stefano Stabellini >> wrote: >>> >>> On Mon, 22 Nov 2021, Ayan Kumar Halder wrote: Stefano > It doesn't look like we are setting dabt->write any

Re: [PATCH 4/5] x86/traps: Drop exception_table[] and use if/else dispatching

On 19.11.2021 19:21, Andrew Cooper wrote: > There is also a lot of redundancy in the table. 8 vectors head to do_trap(), > 3 are handled in the IST logic, and that only leaves 7 others not heading to > the do_reserved_trap() catch-all. This also removes the fragility that any > accidental NULL en

Re: [RFC PATCH] Added the logic to decode 32 bit ldr/str post-indexing instructions

Hi, > On 23 Nov 2021, at 08:53, Bertrand Marquis wrote: > > Hi Stefano, > >> On 23 Nov 2021, at 04:13, Stefano Stabellini wrote: >> >> On Mon, 22 Nov 2021, Julien Grall wrote: >>> On Mon, 22 Nov 2021 at 19:59, Stefano Stabellini >>> wrote: On Mon, 22 Nov 2021, Ayan Kumar Halder w

[xen-unstable test] 166304: tolerable FAIL

flight 166304 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/166304/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 166263 test-armhf-armhf-libvirt 16 save

Xen Security Advisory 389 v3 (CVE-2021-28705,CVE-2021-28709) - issues with partially successful P2M updates on x86

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Xen Security Advisory CVE-2021-28705,CVE-2021-28709 / XSA-389 version 3 issues with partially successful P2M updates on x86 UPDATES IN VERSION 3 Add CVE numbers to patches. Public

Xen Security Advisory 387 v2 (CVE-2021-28703) - grant table v2 status pages may remain accessible after de-allocation (take two)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Xen Security Advisory CVE-2021-28703 / XSA-387 version 2 grant table v2 status pages may remain accessible after de-allocation (take two) UPDATES IN VERSION 2 Public release. ISSUE

Xen Security Advisory 385 v2 (CVE-2021-28706) - guests may exceed their designated memory limit

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Xen Security Advisory CVE-2021-28706 / XSA-385 version 2 guests may exceed their designated memory limit UPDATES IN VERSION 2 Add CVE numbers to patches. Public release.

Xen Security Advisory 388 v3 (CVE-2021-28704,CVE-2021-28707,CVE-2021-28708) - PoD operations on misaligned GFNs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Xen Security Advisory CVE-2021-28704,CVE-2021-28707,CVE-2021-28708 / XSA-388 version 3 PoD operations on misaligned GFNs UPDATES IN VERSION 3 Correct affected versions ran

Re: [PATCH 01/10] vpci: move lock

Hi, Roger, Jan! I think the below work will help with solving issues brought up by [1]. So, after thinking a bit more I concluded that indeed we do not actually need a per-domain vPCI lock, but instead we just want to protect pdev->vpci which is done in this patch. At the moment I see four entit

Re: [RFC PATCH] Added the logic to decode 32 bit ldr/str post-indexing instructions

On 22/11/2021 14:19, Ayan Kumar Halder wrote: Hi Julien/Stefano/Wei/Jan, Hi, As some of the comments were inter-related, I have consolidated my response to all the comments below. On 19/11/2021 17:26, Julien Grall wrote: Hi Ayan, On 19/11/2021 16:52, Ayan Kumar Halder wrote: At presen

[PATCH v7 0/3] xen, usb: support pvUSB frontend driver

This series adds XEN guest pvUSB support. With pvUSB it is possible to use physical USB devices from a XEN domain. Since V4 a lot of time (several years) has passed. This is a revived attempt to get the frontend into the kernel. The support consists of a frontend in form of a virtual hcd driver i

[PATCH v7 2/3] usb: Introduce Xen pvUSB frontend (xen hcd)

Introduces the Xen pvUSB frontend. With pvUSB it is possible for a Xen domU to communicate with a USB device assigned to that domU. The communication is all done via the pvUSB backend in a driver domain (usually Dom0) which is owner of the physical device. The pvUSB frontend is a USB hcd for a vir

[PATCH v7 3/3] xen: add Xen pvUSB maintainer

Add myself as maintainer for the Xen pvUSB stuff. Signed-off-by: Juergen Gross Acked-by: Konrad Rzeszutek Wilk --- MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 5250298d2817..da7fd3d32dc4 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -20

[PATCH v7 1/3] usb: Add Xen pvUSB protocol description

Add the definition of pvUSB protocol used between the pvUSB frontend in a Xen domU and the pvUSB backend in a Xen driver domain (usually Dom0). This header was originally provided by Fujitsu for Xen based on Linux 2.6.18. Changes are: - adapt to Linux kernel style guide - use Xen namespace - add

[PATCH 0/3] VT-d: further small corrections

1: prune SAGAW recognition 2: correct off-by-1 in fault register range check 3: conditionalize IOTLB register offset check Jan

[PATCH 1/3] VT-d: prune SAGAW recognition

Bit 0 of the capability register field has become reserved at or before spec version 2.2. Treat it as such. Replace the effective open-coding of find_first_set_bit(). Adjust local variable types. Signed-off-by: Jan Beulich --- Strictly speaking IOMMUs supporting only 3-level tables ought to resul

[PATCH 2/3] VT-d: correct off-by-1 in fault register range check

All our present implementation requires is that the range fully fits in a single page. No need to exclude the case of the last register extending right to the end of that page. Signed-off-by: Jan Beulich --- a/xen/drivers/passthrough/vtd/iommu.c +++ b/xen/drivers/passthrough/vtd/iommu.c @@ -1229

[PATCH 3/3] VT-d: conditionalize IOTLB register offset check

As of commit 6773b1a7584a ("VT-d: Don't assume register-based invalidation is always supported") we don't (try to) use register based invalidation anymore when that's not supported by hardware. Hence there's also no point in the respective check, avoiding pointless IOMMU initialization failure. Aft

Re: [RFC PATCH 0/2] Boot time cpupools

Hi Stefano, On 19/11/2021 18:55, Stefano Stabellini wrote: On Fri, 19 Nov 2021, Julien Grall wrote: I like better Juergen's version. But before agreeing on the command line , I would like to understand how Linux is dealing with big.LITTLE today (see my question above). I also like Juergen's v

[PATCH V2 0/6] x86/Hyper-V: Add Hyper-V Isolation VM support(Second part)

From: Tianyu Lan Hyper-V provides two kinds of Isolation VMs. VBS(Virtualization-based security) and AMD SEV-SNP unenlightened Isolation VMs. This patchset is to add support for these Isolation VM support in Linux. The memory of these vms are encrypted and host can't access guest memory directly

[PATCH V2 1/6] Swiotlb: Add Swiotlb bounce buffer remap function for HV IVM

From: Tianyu Lan In Isolation VM with AMD SEV, bounce buffer needs to be accessed via extra address space which is above shared_gpa_boundary (E.G 39 bit address line) reported by Hyper-V CPUID ISOLATION_CONFIG. The access physical address will be original physical address + shared_gpa_boundary. T

[PATCH V2 2/6] dma-mapping: Add vmap/vunmap_noncontiguous() callback in dma ops

From: Tianyu Lan Hyper-V netvsc driver needs to allocate noncontiguous DMA memory and remap it into unencrypted address space before sharing with host. Add vmap/vunmap_noncontiguous() callback and handle the remap in the Hyper-V dma ops callback. Signed-off-by: Tianyu Lan --- include/linux/dma

[PATCH V2 3/6] x86/hyper-v: Add hyperv Isolation VM check in the cc_platform_has()

From: Tianyu Lan Hyper-V provides Isolation VM which has memory encrypt support. Add hyperv_cc_platform_has() and return true for check of GUEST_MEM_ENCRYPT attribute. Signed-off-by: Tianyu Lan --- arch/x86/kernel/cc_platform.c | 15 +++ 1 file changed, 15 insertions(+) diff --git

[PATCH V2 4/6] hyperv/IOMMU: Enable swiotlb bounce buffer for Isolation VM

From: Tianyu Lan hyperv Isolation VM requires bounce buffer support to copy data from/to encrypted memory and so enable swiotlb force mode to use swiotlb bounce buffer for DMA transaction. In Isolation VM with AMD SEV, the bounce buffer needs to be accessed via extra address space which is above

[PATCH V2 5/6] net: netvsc: Add Isolation VM support for netvsc driver

From: Tianyu Lan In Isolation VM, all shared memory with host needs to mark visible to host via hvcall. vmbus_establish_gpadl() has already done it for netvsc rx/tx ring buffer. The page buffer used by vmbus_sendpacket_ pagebuffer() stills need to be handled. Use DMA API to map/umap these memory

[PATCH V2 6/6] scsi: storvsc: Add Isolation VM support for storvsc driver

From: Tianyu Lan In Isolation VM, all shared memory with host needs to mark visible to host via hvcall. vmbus_establish_gpadl() has already done it for storvsc rx/tx ring buffer. The page buffer used by vmbus_sendpacket_ mpb_desc() still needs to be handled. Use DMA API(scsi_dma_map/unmap) to map

Re: [RFC PATCH 0/2] Boot time cpupools

Hi Julien, > On 23 Nov 2021, at 13:54, Julien Grall wrote: > > Hi Stefano, > > On 19/11/2021 18:55, Stefano Stabellini wrote: >> On Fri, 19 Nov 2021, Julien Grall wrote: >>> I like better Juergen's version. But before agreeing on the command line , I >>> would like to understand how Linux is de

Re: [PATCH v4 05/11] vpci/header: implement guest BAR register handlers

Hi, Roger! On 19.11.21 15:02, Jan Beulich wrote: > On 19.11.2021 13:54, Oleksandr Andrushchenko wrote: >> On 19.11.21 14:49, Jan Beulich wrote: >>> On 19.11.2021 13:46, Oleksandr Andrushchenko wrote: On 19.11.21 14:37, Jan Beulich wrote: > On 19.11.2021 13:10, Oleksandr Andrushchenko wrot

Re: [PATCH v6 2/7] xen/arm: add pci-domain for disabled devices

Hi Oleksandr, On 23/11/2021 06:31, Oleksandr Andrushchenko wrote: On 22.11.21 19:17, Julien Grall wrote: Hi, On 22/11/2021 16:23, Oleksandr Andrushchenko wrote: On 22.11.21 17:29, Julien Grall wrote: I would prefer to go with my way. This can be refined in the future if we find Device-Tre

Re: [PATCH v6 3/7] xen/arm: setup MMIO range trap handlers for hardware domain

On 23/11/2021 06:58, Oleksandr Andrushchenko wrote: Hi, Julien! Hi Oleksandr, On 22.11.21 19:36, Julien Grall wrote: On 18/11/2021 10:46, Oleksandr Andrushchenko wrote: On 18.11.21 09:27, Oleksandr Andrushchenko wrote: +    unsigned int count; + +    if ( is_hardware_domain(d) ) +  

Xen 4.16 RC4

Xen 4.16 RC4 is now available. It is available from git: git clone https://xenbits.xenproject.org/git-http/xen.git -b 4.16.0-rc4 For your convenience a tarball is available: https://downloads.xenproject.org/release/xen/4.16.0-rc4/xen-4.16.0-rc4.tar.gz https://downloads.xenproject.org/relea

[PATCH for-4.16 v3] CHANGELOG: add missing entries for work during the 4.16 release cycle

Document some of the relevant changes during the 4.16 release cycle. Signed-off-by: Roger Pau Monné Release-Acked-by: Ian Jackson --- Changes since v2: - Reword the x86 page table API change. Changes since v1: - Add qemu-traditional and pvgrub notes. - Expand vPMU support to note it's limite

Re: [PATCH v6 3/7] xen/arm: setup MMIO range trap handlers for hardware domain

Hi, Julien! On 23.11.21 18:12, Julien Grall wrote: > > > On 23/11/2021 06:58, Oleksandr Andrushchenko wrote: >> Hi, Julien! > > Hi Oleksandr, > >> On 22.11.21 19:36, Julien Grall wrote: >>> On 18/11/2021 10:46, Oleksandr Andrushchenko wrote: On 18.11.21 09:27, Oleksandr Andrushchenko wrote: >

Re: [PATCH v6 4/7] xen/arm: do not map PCI ECAM and MMIO space to Domain-0's p2m

Hi Oleksandr, On 05/11/2021 06:33, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko PCI host bridges are special devices in terms of implementing PCI passthrough. According to [1] the current implementation depends on Domain-0 to perform the initialization of the relevant PCI host

Re: [PATCH v6 2/7] xen/arm: add pci-domain for disabled devices

Hi, Julien! On 23.11.21 18:05, Julien Grall wrote: > Hi Oleksandr, > > On 23/11/2021 06:31, Oleksandr Andrushchenko wrote: >> >> >> On 22.11.21 19:17, Julien Grall wrote: >>> Hi, >>> >>> On 22/11/2021 16:23, Oleksandr Andrushchenko wrote: On 22.11.21 17:29, Julien Grall wrote: > I would p

Re: [PATCH V2 3/4] xen/unpopulated-alloc: Add mechanism to use Xen resource

On 20.11.21 04:19, Stefano Stabellini wrote: Hi Stefano, Juergen, all Juergen please see the bottom of the email On Fri, 19 Nov 2021, Oleksandr wrote: On 19.11.21 02:59, Stefano Stabellini wrote: On Tue, 9 Nov 2021, Oleksandr wrote: On 28.10.21 19:37, Stefano Stabellini wrote: Hi Stefan

[PATCH for-4.16 0/3] Changes from release technician checklist

I am about to push these to xen.git#staging-4.16. Roger, I have not messed with the furniture in CHANGELOG.md on either staging-4.16 or staging. Ian. Ian Jackson (3): Config.mk: switch to named tags (for stable branch) SUPPORT.md: Set Release Notes link Turn off debug by default Config.m

[PATCH for-4.16 2/3] SUPPORT.md: Set Release Notes link

Signed-off-by: Ian Jackson --- SUPPORT.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/SUPPORT.md b/SUPPORT.md index 3a34933c89..b1367e2b22 100644 --- a/SUPPORT.md +++ b/SUPPORT.md @@ -9,13 +9,13 @@ for the definitions of the support status levels etc. # Release Supp

[PATCH for-4.16 1/3] Config.mk: switch to named tags (for stable branch)

Signed-off-by: Ian Jackson --- Config.mk | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/Config.mk b/Config.mk index 6be010c7ce..b32a185efc 100644 --- a/Config.mk +++ b/Config.mk @@ -239,17 +239,15 @@ SEABIOS_UPSTREAM_URL ?= git://xenbits.xen.org/seabios.git MINIOS_UP

[PATCH for-4.16 3/3] Turn off debug by default

Signed-off-by: Ian Jackson --- tools/Rules.mk| 2 +- xen/Kconfig.debug | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/Rules.mk b/tools/Rules.mk index b022da3336..051a5d3555 100644 --- a/tools/Rules.mk +++ b/tools/Rules.mk @@ -25,7 +25,7 @@ CFLAGS_xeninclude = -I$

[PATCH for-4.17 2/3] Set version to 4.17; 4.16 has branched

Signed-off-by: Ian Jackson --- README | 10 +- xen/Makefile | 4 ++-- 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/README b/README index a626e56436..562b808080 100644 --- a/README +++ b/README @@ -1,9 +1,9 @@ ##

[PATCH for-4.17 3/3] Set version to 4.17: rerun autogen.sh

Signed-off-by: Ian Jackson --- configure | 18 +- docs/configure| 18 +- stubdom/configure | 18 +- tools/configure | 18 +- 4 files changed, 36 insertions(+), 36 deletions(-) diff --git a/configure b/configure index 6

[PATCH for-4.17 1/3] Revert "Config.mk: pin QEMU_UPSTREAM_REVISION (prep for Xen 4.16 RC1)"

This branch is unstable again now. This reverts commit c9ce6afbf2d7772f47fc572bb7fc9555724927ed. --- Config.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Config.mk b/Config.mk index 6be010c7ce..6587c7d626 100644 --- a/Config.mk +++ b/Config.mk @@ -239,7 +239,7 @@ SEABIOS_

Re: [PATCH v6 3/7] xen/arm: setup MMIO range trap handlers for hardware domain

Hi, On 23/11/2021 16:41, Oleksandr Andrushchenko wrote: On 23.11.21 18:12, Julien Grall wrote: On 23/11/2021 06:58, Oleksandr Andrushchenko wrote: unsigned int domain_vpci_get_num_mmio_handlers(struct domain *d) {       if ( !has_vpci(d) )       return 0;       if ( is_hardware_domain(

Xen 4.16 branched, commit moratorium lifted, freeze still in force

Xen 4.16 has now branched. The staging-4.16 branch et al exists. The commit moratorium is lifted. However: * 4.16 is in deep freeze now. Nothing should be committed without a release ack. Roger, you have a blanket release ack for your CHANGELOG update(s). * Until 4.16 is released, please

[qemu-mainline test] 166307: regressions - FAIL

flight 166307 qemu-mainline real [real] flight 166316 qemu-mainline real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/166307/ http://logs.test-lab.xenproject.org/osstest/logs/166316/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be

RE: [PATCH V2 1/6] Swiotlb: Add Swiotlb bounce buffer remap function for HV IVM

From: Tianyu Lan Sent: Tuesday, November 23, 2021 6:31 AM > > In Isolation VM with AMD SEV, bounce buffer needs to be accessed via > extra address space which is above shared_gpa_boundary (E.G 39 bit > address line) reported by Hyper-V CPUID ISOLATION_CONFIG. The access > physical address will be

Re: [PATCH v6 2/7] xen/arm: add pci-domain for disabled devices

Hi, On 23/11/2021 16:44, Oleksandr Andrushchenko wrote: On 23.11.21 18:05, Julien Grall wrote: Hi Oleksandr, On 23/11/2021 06:31, Oleksandr Andrushchenko wrote: On 22.11.21 19:17, Julien Grall wrote: Hi, On 22/11/2021 16:23, Oleksandr Andrushchenko wrote: On 22.11.21 17:29, Julien Grall

Re: [PATCH v3 02/10] xen/arm: avoid setting XEN_DOMCTL_CDF_iommu when IOMMU off

Hi Penny, On 16/11/2021 06:31, Penny Zheng wrote: From: Stefano Stabellini This commit avoids setting XEN_DOMCTL_CDF_iommu when the IOMMU is absent/disabled, otherwise xen will fail later when handling device assignment. I would explain briefly in the commit message why you want to do device

Re: [PATCH v3 03/10] xen/arm: introduce new helper parse_static_mem_prop and acquire_static_memory_bank

Hi Penny, On 16/11/2021 06:31, Penny Zheng wrote: Later, we will introduce allocate_static_memory_11 for allocating static memory for direct-map domains, and it will share a lot common codes with the existing allocate_static_memory. In order not to bring a lot of duplicate codes, and also to ma

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

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

RE: [PATCH V2 4/6] hyperv/IOMMU: Enable swiotlb bounce buffer for Isolation VM

From: Tianyu Lan Sent: Tuesday, November 23, 2021 6:31 AM > > hyperv Isolation VM requires bounce buffer support to copy > data from/to encrypted memory and so enable swiotlb force > mode to use swiotlb bounce buffer for DMA transaction. > > In Isolation VM with AMD SEV, the bounce buffer needs

RE: [PATCH V2 5/6] net: netvsc: Add Isolation VM support for netvsc driver

From: Tianyu Lan Sent: Tuesday, November 23, 2021 6:31 AM > > In Isolation VM, all shared memory with host needs to mark visible > to host via hvcall. vmbus_establish_gpadl() has already done it for > netvsc rx/tx ring buffer. The page buffer used by vmbus_sendpacket_ > pagebuffer() stills need t

Re: [PATCH 0/5] xen: cleanup detection of non-essential pv devices

On 11/22/21 3:20 AM, Juergen Gross wrote: On 22.10.21 08:47, Juergen Gross wrote: Today the non-essential pv devices are hard coded in the xenbus driver and this list is lacking multiple entries. This series reworks the detection logic of non-essential devices by adding a flag for that purpos

[PATCH v4] xen: detect uninitialized xenbus in xenbus_init

From: Stefano Stabellini If the xenstore page hasn't been allocated properly, reading the value of the related hvm_param (HVM_PARAM_STORE_PFN) won't actually return error. Instead, it will succeed and return zero. Instead of attempting to xen_remap a bad guest physical address, detect this condit

Re: [PATCH] cpu/hotplug: Allow the CPU in CPU_UP_PREPARE state to be brought up again.

Tested-by: Dongli Zhang The bug fixed by commit 53fafdbb8b21 ("KVM: x86: switch KVMCLOCK base to monotonic raw clock") may leave the cpu_hotplug_state at CPU_UP_PREPARE. As a result, to online this CPU again (even after removal) is always failed. I have tested that this patch works well to work

Re: [PATCH V2 3/4] xen/unpopulated-alloc: Add mechanism to use Xen resource

On Tue, 23 Nov 2021, Oleksandr wrote: > > Actually after reading your replies and explanation I changed opinion: I > > think we do need the fallback because Linux cannot really assume that > > it is running on "new Xen" so it definitely needs to keep working if > > CONFIG_XEN_UNPOPULATED_ALLOC is e

Re: [RFC PATCH 0/2] Boot time cpupools

On Tue, 23 Nov 2021, Bertrand Marquis wrote: > Hi Julien, > > > On 23 Nov 2021, at 13:54, Julien Grall wrote: > > > > Hi Stefano, > > > > On 19/11/2021 18:55, Stefano Stabellini wrote: > >> On Fri, 19 Nov 2021, Julien Grall wrote: > >>> I like better Juergen's version. But before agreeing on th

[xen-unstable-smoke test] 166326: regressions - FAIL

flight 166326 xen-unstable-smoke real [real] flight 166330 xen-unstable-smoke real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/166326/ http://logs.test-lab.xenproject.org/osstest/logs/166330/ Regressions :-( Tests which did not succeed and are blocking, including tests which co

RE: [PATCH 1/3] VT-d: prune SAGAW recognition

> From: Jan Beulich > Sent: Tuesday, November 23, 2021 9:40 PM > > Bit 0 of the capability register field has become reserved at or before Bit 0 of 'SAGAW' in the capability register ... > spec version 2.2. Treat it as such. Replace the effective open-coding of > find_first_set_bit(). Adjust lo

RE: [PATCH 2/3] VT-d: correct off-by-1 in fault register range check

> From: Jan Beulich > Sent: Tuesday, November 23, 2021 9:40 PM > > All our present implementation requires is that the range fully fits > in a single page. No need to exclude the case of the last register > extending right to the end of that page. > > Signed-off-by: Jan Beulich Reviewed-by: Ke

RE: [PATCH 3/3] VT-d: conditionalize IOTLB register offset check

> From: Jan Beulich > Sent: Tuesday, November 23, 2021 9:40 PM > > As of commit 6773b1a7584a ("VT-d: Don't assume register-based > invalidation is always supported") we don't (try to) use register based > invalidation anymore when that's not supported by hardware. Hence > there's also no point in

[xen-4.16-testing baseline test] 166322: FAIL

"Old" tested version had not actually been tested; therefore in this flight we test it, rather than a new candidate. The baseline, if any, is the most recent actually tested revision. flight 166322 xen-4.16-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/166322/ Failures and

[xen-4.15-testing test] 166311: regressions - FAIL

flight 166311 xen-4.15-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/166311/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-debianhvm-amd64 12 debian-hvm-install fail REGR. vs. 166198 test-a

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

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

Re: [PATCH] cpu/hotplug: Allow the CPU in CPU_UP_PREPARE state to be brought up again.

On 22/11/21 16:47, Sebastian Andrzej Siewior wrote: > From: "Longpeng(Mike)" > > A CPU will not show up in virtualized environment which includes an > Enclave. The VM splits its resources into a primary VM and a Enclave > VM. While the Enclave is active, the hypervisor will ignore all requests > t

About support for memory event on AMD CPUs

Dear developers, Short version: is memory event supported on AMD CPUs or is it going to be supported? Long version: Environment: LibVMI 0.15.0 + Xen 4.14.3 on an **AMD CPU** (5950x), 64-bit Debian 11 Dom0. What I am trying to accomplish: register a **memory event** handler, so that I can captur

Re: [PATCH v4] xen: detect uninitialized xenbus in xenbus_init

On 23.11.21 22:07, Stefano Stabellini wrote: From: Stefano Stabellini If the xenstore page hasn't been allocated properly, reading the value of the related hvm_param (HVM_PARAM_STORE_PFN) won't actually return error. Instead, it will succeed and return zero. Instead of attempting to xen_remap a

Re: [PATCH V2 3/4] xen/unpopulated-alloc: Add mechanism to use Xen resource

On 23.11.21 17:46, Oleksandr wrote: On 20.11.21 04:19, Stefano Stabellini wrote: Hi Stefano, Juergen, all Juergen please see the bottom of the email On Fri, 19 Nov 2021, Oleksandr wrote: On 19.11.21 02:59, Stefano Stabellini wrote: On Tue, 9 Nov 2021, Oleksandr wrote: On 28.10.21 19:37,

Re: [PATCH] cpu/hotplug: Allow the CPU in CPU_UP_PREPARE state to be brought up again.

On 11/23/21 3:50 PM, Longpeng (Mike, Cloud Infrastructure Service Product Dept.) wrote: > > >> -Original Message- >> From: Dongli Zhang [mailto:dongli.zh...@oracle.com] >> Sent: Wednesday, November 24, 2021 5:22 AM >> To: Sebastian Andrzej Siewior ; Longpeng (Mike, Cloud >> Infrastruct

RE: [PATCH] cpu/hotplug: Allow the CPU in CPU_UP_PREPARE state to be brought up again.

Hi, > -Original Message- > From: Xen-devel On Behalf Of > Sebastian Andrzej Siewior > Sent: Monday, November 22, 2021 11:47 PM > To: Longpeng (Mike, Cloud Infrastructure Service Product Dept.) > > Cc: linux-ker...@vger.kernel.org; Gonglei (Arei) ; > x...@kernel.org; xen-devel@lists.xenpr

Re: [PATCH v6 2/7] xen/arm: add pci-domain for disabled devices

Hi, Julien! On 23.11.21 19:15, Julien Grall wrote: > Hi, > > On 23/11/2021 16:44, Oleksandr Andrushchenko wrote: >> On 23.11.21 18:05, Julien Grall wrote: >>> Hi Oleksandr, >>> >>> On 23/11/2021 06:31, Oleksandr Andrushchenko wrote: On 22.11.21 19:17, Julien Grall wrote: > Hi, >

Re: [PATCH v4] xenbus: support large messages

Ping? On 04.10.21 11:40, Juergen Gross wrote: Today the implementation of the xenbus protocol in Mini-OS will only allow to transfer the complete message to or from the ring page buffer. This is limiting the maximum message size to lower values as the xenbus protocol normally would allow. Chang

Re: [PATCH 1/3] VT-d: prune SAGAW recognition

On 24.11.2021 02:22, Tian, Kevin wrote: >> From: Jan Beulich >> Sent: Tuesday, November 23, 2021 9:40 PM >> >> Bit 0 of the capability register field has become reserved at or before > > Bit 0 of 'SAGAW' in the capability register ... I've changed it, but I thought the use of "field" in the sent

Re: [PATCH v6 3/7] xen/arm: setup MMIO range trap handlers for hardware domain

Hi, Julien! On 23.11.21 18:58, Julien Grall wrote: > Hi, > > On 23/11/2021 16:41, Oleksandr Andrushchenko wrote: >> On 23.11.21 18:12, Julien Grall wrote: >>> On 23/11/2021 06:58, Oleksandr Andrushchenko wrote: unsigned int domain_vpci_get_num_mmio_handlers(struct domain *d) {      

Re: [PATCH v4] xen: detect uninitialized xenbus in xenbus_init

On 23.11.2021 22:07, Stefano Stabellini wrote: > From: Stefano Stabellini > > If the xenstore page hasn't been allocated properly, reading the value > of the related hvm_param (HVM_PARAM_STORE_PFN) won't actually return > error. Instead, it will succeed and return zero. Instead of attempting > to

Re: [xen-4.15-testing test] 166311: regressions - FAIL

On 24.11.2021 03:00, osstest service owner wrote: > flight 166311 xen-4.15-testing real [real] > http://logs.test-lab.xenproject.org/osstest/logs/166311/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-amd64-xl-qemuu-de

Re: [PATCH v6 4/7] xen/arm: do not map PCI ECAM and MMIO space to Domain-0's p2m

Hi, Julien! On 23.11.21 18:42, Julien Grall wrote: > Hi Oleksandr, > > On 05/11/2021 06:33, Oleksandr Andrushchenko wrote: >> From: Oleksandr Andrushchenko >> >> PCI host bridges are special devices in terms of implementing PCI >> passthrough. According to [1] the current implementation depends o

Re: About support for memory event on AMD CPUs

On 23.11.2021 18:14, YAN Untitled wrote: > Dear developers, > > Short version: is memory event supported on AMD CPUs or is it going to be > supported? > > Long version: > > Environment: LibVMI 0.15.0 + Xen 4.14.3 on an **AMD CPU** (5950x), 64-bit > Debian 11 Dom0. > > What I am trying to accomp

[PATCH v7 1/7] xen/arm: rename DEVICE_PCI to DEVICE_PCI_HOSTBRIDGE

From: Oleksandr Andrushchenko To better reflect the nature of the device type and not to make any confusion rename DEVICE_PCI to DEVICE_PCI_HOSTBRIDGE which it really is. Suggested-by: Julien Grall Signed-off-by: Oleksandr Andrushchenko Reviewed-by: Julien Grall --- New in v6 --- xen/arch/ar

[PATCH v7 0/7] PCI devices passthrough on Arm, part 2

From: Oleksandr Andrushchenko Hi, all! This is an assorted series of patches which aim is to make some further basis for PCI passthrough on Arm support. The series continues the work published earlier by Arm [1] and adds new helpers and clears the way for vPCI changes which will follow. RFC is

[PATCH v7 2/7] xen/arm: add pci-domain for disabled devices

From: Oleksandr Andrushchenko If a PCI host bridge device is present in the device tree, but is disabled, then its PCI host bridge driver was not instantiated. This results in the failure of the pci_get_host_bridge_segment() and the following panic during Xen start: (XEN) Device tree generation

[PATCH v7 3/7] xen/arm: setup MMIO range trap handlers for hardware domain

From: Oleksandr Andrushchenko In order for vPCI to work it needs to maintain guest and hardware domain's views of the configuration space. For example, BARs and COMMAND registers require emulation for guests and the guest view of the registers needs to be in sync with the real contents of the rel

[PATCH v7 4/7] xen/arm: account IO handler for emulated PCI host bridge

From: Oleksandr Andrushchenko At the moment, we always allocate an extra 16 slots for IO handlers (see MAX_IO_HANDLER). So while adding an IO trap handler for the emulated PCI host bridge we are not breaking anything, but we have a latent bug as the maximum number of IOs may be exceeded. Fix this

[PATCH v7 6/7] xen/arm: process pending vPCI map/unmap operations

From: Oleksandr Andrushchenko vPCI may map and unmap PCI device memory (BARs) being passed through which may take a lot of time. For this those operations may be deferred to be performed later, so that they can be safely preempted. Currently this deferred processing is happening in common IOREQ

[PATCH v7 5/7] xen/arm: do not map PCI ECAM and MMIO space to Domain-0's p2m

From: Oleksandr Andrushchenko PCI host bridges are special devices in terms of implementing PCI passthrough. According to [1] the current implementation depends on Domain-0 to perform the initialization of the relevant PCI host bridge hardware and perform PCI device enumeration. In order to achie