flight 170810 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170810/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt 8 xen-boot fail REGR. vs. 170714
test-amd64-amd64-li
On Tue, 31 May 2022, Penny Zheng wrote:
> Today when a domain unpopulates the memory on runtime, they will always
> hand the memory back to the heap allocator. And it will be a problem if domain
> is static.
>
> Pages as guest RAM for static domain shall be reserved to only this domain
> and not b
On Tue, 31 May 2022, Penny Zheng wrote:
> In order to have an easy and quick way to find out whether this domain memory
> is statically configured, this commit introduces a new flag CDF_staticmem and
> a
> new helper is_domain_using_staticmem() to tell.
>
> Signed-off-by: Penny Zheng
I realize
On Tue, 31 May 2022, Penny Zheng wrote:
> SUPPORT.md doesn't seem to explicitly say whether static memory is
> supported, so this commit updates SUPPORT.md to add feature static
> allocation tech preview for now.
>
> Signed-off-by: Penny Zheng
> ---
> v5 changes:
> - new commit
> ---
> SUPPORT.m
I reviewed patches #1 and #3. Julien had already started reviewing the
other patches in details so it is probably better if he continues his
reviews on those. So I skipped them for now. Let me know if you'd like
me to review them.
On Tue, 31 May 2022, Bertrand Marquis wrote:
> Following up the han
On Tue, 31 May 2022, Bertrand Marquis wrote:
> Sync existing ID registers sanitization with the status of Linux kernel
> version 5.18-rc3 and add sanitization of ISAR2 registers.
>
> Sync sysregs.h bit shift defintions with the status of Linux kernel
> version 5.18-rc3.
>
> Changes in this patch
On Tue, 31 May 2022, Bertrand Marquis wrote:
> Complete AA64ISAR2 and AA64MMFR[0-1] with more fields.
> While there add a comment for MMFR bitfields as for other registers in
> the cpuinfo structure definition.
>
> Signed-off-by: Bertrand Marquis
> ---
> Changes in v2:
> - patch introduced to iso
flight 170809 qemu-mainline real [real]
flight 170811 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/170809/
http://logs.test-lab.xenproject.org/osstest/logs/170811/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-am
On Wed, 1 Jun 2022, Oleksandr Tyshchenko wrote:
> From: Julien Grall
>
> This patch introduces helpers to allocate Virtio MMIO params
> (IRQ and memory region) and create specific device node in
> the Guest device-tree with allocated params. In order to deal
> with multiple Virtio devices, reserv
unmap_grant_pages() currently waits for the pages to no longer be used.
In https://github.com/QubesOS/qubes-issues/issues/7481, this lead to a
deadlock against i915: i915 was waiting for gntdev's MMU notifier to
finish, while gntdev was waiting for i915 to free its pages. I also
believe this is re
flight 170808 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170808/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-dom0pvh-xl-amd 14 guest-start fail REGR. vs. 170714
test-amd64-amd64-do
On Saturday, May 28, 2022, Bernhard Beschow wrote:
> Am 13. Mai 2022 18:09:54 UTC schrieb Bernhard Beschow :
>>v2:
>>* Have pci_xen_ide_unplug() return void (Paul Durrant)
>>* CC Xen maintainers (Michael S. Tsirkin)
>>
>>v1:
>>This patch series first removes the redundant "piix3-ide-xen" device
cl
On 6/2/22 16:32, Daniel P. Smith wrote:
> On 5/31/22 10:56, Daniel P. Smith wrote:
>> This commit implements full support for starting the idle domain privileged
>> by
>> introducing a new flask label xenboot_t which the idle domain is labeled with
>> at creation. It then provides the implementat
On 5/31/22 10:56, Daniel P. Smith wrote:
> This commit implements full support for starting the idle domain privileged by
> introducing a new flask label xenboot_t which the idle domain is labeled with
> at creation. It then provides the implementation for the XSM hook
> xsm_set_system_active to r
On 01.06.22 23:39, Stefano Stabellini wrote:
Hello Stefano
On Wed, 1 Jun 2022, Oleksandr wrote:
On 01.06.22 04:04, Stefano Stabellini wrote:
On Tue, 31 May 2022, Oleksandr Tyshchenko wrote:
From: Oleksandr Tyshchenko
Reuse generic IOMMU device tree bindings to communicate Xen specific
in
From: Oleksandr Tyshchenko
Use the presence of "iommus" property pointed to the IOMMU node with
recently introduced "xen,grant-dma" compatible as a clear indicator
of enabling Xen grant mappings scheme for that device and read the ID
of Xen domain where the corresponding backend is running. The d
From: Oleksandr Tyshchenko
The main purpose of this binding is to communicate Xen specific
information using generic IOMMU device tree bindings (which is
a good fit here) rather than introducing a custom property.
Introduce Xen specific IOMMU for the virtualized device (e.g. virtio)
to be used b
From: Oleksandr Tyshchenko
By assigning xen-grant DMA ops we will restrict memory access for
passed device using Xen grant mappings. This is needed for using any
virtualized device (e.g. virtio) in Xen guests in a safe manner.
Please note, for the virtio devices the XEN_VIRTIO config should
be e
From: Juergen Gross
Introduce Xen grant DMA-mapping layer which contains special DMA-mapping
routines for providing grant references as DMA addresses to be used by
frontends (e.g. virtio) in Xen guests.
Add the needed functionality by providing a special set of DMA ops
handling the needed grant
From: Juergen Gross
In order to support virtio in Xen guests add a config option XEN_VIRTIO
enabling the user to specify whether in all Xen guests virtio should
be able to access memory via Xen grant mappings only on the host side.
Also set PLATFORM_VIRTIO_RESTRICTED_MEM_ACCESS feature from the
From: Oleksandr Tyshchenko
Hello all.
The purpose of this patch series is to add support for restricting memory
access under Xen using specific
grant table [1] based DMA-mapping layer. Patch series is based on Juergen
Gross’ initial work [2] which implies
using grant references instead of raw
From: Oleksandr Tyshchenko
In order to reuse generic IOMMU device tree bindings by Xen grant
DMA-mapping layer we need to add this stub driver from a fw_devlink
perspective (grant-dma-ops cannot be converted into the proper
IOMMU driver).
Otherwise, just reusing IOMMU bindings (without having a
From: Oleksandr Tyshchenko
This patch introduces new helper and places it in new header.
The helper's purpose is to assign any Xen specific DMA ops in
a single place. For now, we deal with xen-swiotlb DMA ops only.
The one of the subsequent commits in current series will add
xen-grant DMA ops cas
From: Juergen Gross
For support of virtio via grant mappings in rare cases larger mappings
using consecutive grants are needed. Support those by adding a bitmap
of free grants.
As consecutive grants will be needed only in very rare cases (e.g. when
configuring a virtio device with a multi-page r
On 6/2/22 8:49 AM, Oleksandr wrote:
On 31.05.22 00:00, Oleksandr Tyshchenko wrote:
Hello all.
From: Juergen Gross
In order to support virtio in Xen guests add a config option XEN_VIRTIO
enabling the user to specify whether in all Xen guests virtio should
be able to access memory via Xen g
flight 170806 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170806/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-examine-uefi 6 xen-installfail pass in 170801
Tests which did not succeed, but
flight 170805 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170805/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-dom0pvh-xl-amd 14 guest-start fail REGR. vs. 170714
test-amd64-amd64-do
On 31.05.22 00:00, Oleksandr Tyshchenko wrote:
Hello all.
From: Juergen Gross
In order to support virtio in Xen guests add a config option XEN_VIRTIO
enabling the user to specify whether in all Xen guests virtio should
be able to access memory via Xen grant mappings only on the host side.
On 01.06.22 21:53, Jason Andryuk wrote:
When a VBD is not fully created and then closed, the kernel can have a
NULL pointer dereference:
The reproducer is trivial:
[user@dom0 ~]$ sudo xl block-attach work backend=sys-usb vdev=xvdi
target=/dev/sdz
[user@dom0 ~]$ xl block-list work
Vdev BE han
On Thu, Jun 2, 2022 at 2:02 AM Christoph Hellwig wrote:
>
> On Wed, Jun 01, 2022 at 03:53:41PM -0400, Jason Andryuk wrote:
> > When a VBD is not fully created and then closed, the kernel can have a
> > NULL pointer dereference:
> >
> >
> > info->rq and info->gd are only set in blkfront_connect(),
flight 170807 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170807/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 64706ef761273ba403f9cb3b7a986bfb804c0a87
baseline version:
ovmf 62044aa99bcf0a7b1581b
On 02.06.2022 12:07, Penny Zheng wrote:
>> From: Jan Beulich
>> Sent: Tuesday, May 31, 2022 4:41 PM
>>
>> On 31.05.2022 05:12, Penny Zheng wrote:
>>> --- a/xen/arch/arm/include/asm/domain.h
>>> +++ b/xen/arch/arm/include/asm/domain.h
>>> @@ -31,6 +31,10 @@ enum domain_type {
>>>
>>> #define is_do
On Thu, Jun 02, 2022 at 11:58:48AM +0200, Jan Beulich wrote:
> On 02.06.2022 11:35, Roger Pau Monné wrote:
> > On Fri, May 27, 2022 at 01:19:55PM +0200, Jan Beulich wrote:
> >> When a page table ends up with all contiguous entries (including all
> >> identical attributes), it can be replaced by a s
For one it was an oversight to leave dup_{hi,lo}() undefined for 512-bit
vector size. And then in FMA testing we can also arrange for the
compiler to (hopefully) recognize broadcasting potential.
Signed-off-by: Jan Beulich
--- a/tools/tests/x86_emulator/simd.c
+++ b/tools/tests/x86_emulator/simd
From: Artem Bityutskiy
Add a Sapphire Rapids Xeon C6 optimization, similar to what we have for Sky Lake
Xeon: if package C6 is disabled, adjust C6 exit latency and target residency to
match core C6 values, instead of using the default package C6 values.
Signed-off-by: Artem Bityutskiy
Signed-of
From: Artem Bityutskiy
On Sapphire Rapids Xeon (SPR) the C1 and C1E states are basically mutually
exclusive - only one of them can be enabled. By default, 'intel_idle' driver
enables C1 and disables C1E. However, some users prefer to use C1E instead of
C1, because it saves more energy.
This patc
Still pretty fresh from Linux 5.18 (and with adjustments to address issues
noticed while porting.
1: add 'preferred_cstates' module argument
2: add core C6 optimization for SPR
Jan
Hi Jan
> -Original Message-
> From: Jan Beulich
> Sent: Tuesday, May 31, 2022 4:41 PM
> To: Penny Zheng
> Cc: Wei Chen ; Stefano Stabellini
> ; Julien Grall ; Bertrand Marquis
> ; Volodymyr Babchuk
> ; Andrew Cooper
> ; George Dunlap ;
> Wei Liu ; xen-devel@lists.xenproject.org
> Subject
On 02.06.2022 11:35, Roger Pau Monné wrote:
> On Fri, May 27, 2022 at 01:19:55PM +0200, Jan Beulich wrote:
>> When a page table ends up with all contiguous entries (including all
>> identical attributes), it can be replaced by a superpage entry at the
>> next higher level. The page table itself can
On 30.05.22 19:50, Demi Marie Obenour wrote:
On Mon, May 30, 2022 at 08:41:20AM +0200, Juergen Gross wrote:
On 25.05.22 20:41, Demi Marie Obenour wrote:
unmap_grant_pages() currently waits for the pages to no longer be used.
In https://github.com/QubesOS/qubes-issues/issues/7481, this lead to a
On 31.05.2022 20:20, Daniel P. Smith wrote:
> Previously, initializing the policy buffer was split between two functions,
> xsm_{multiboot,dt}_policy_init() and xsm_core_init(). The latter for loading
> the policy from boot modules and the former for falling back to built-in
> policy.
>
> This pat
On Fri, May 27, 2022 at 01:19:55PM +0200, Jan Beulich wrote:
> When a page table ends up with all contiguous entries (including all
> identical attributes), it can be replaced by a superpage entry at the
> next higher level. The page table itself can then be scheduled for
> freeing.
>
> The adjust
On 31.05.2022 20:20, Daniel P. Smith wrote:
> It is possible to select a few different build configurations that results in
> the unnecessary walking of the boot module list looking for a policy module.
> This specifically occurs when the flask policy is enabled but either the dummy
> or the SILO p
On 02.06.2022 04:18, Penny Zheng wrote:
>> From: Jan Beulich
>> Sent: Tuesday, May 31, 2022 4:37 PM
>>
>> On 31.05.2022 05:12, Penny Zheng wrote:
>>> --- a/xen/common/page_alloc.c
>>> +++ b/xen/common/page_alloc.c
>>> @@ -151,10 +151,6 @@
>>> #define p2m_pod_offline_or_broken_replace(pg) BUG_ON(p
On 01.06.2022 18:59, Anthony PERARD wrote:
> Now that the command line generating "xlat.h" is check on rebuild, the
> header will be regenerated whenever the list of xlat headers changes
> due to change in ".config". We don't need to force a regeneration for
> every changes in ".config".
This look
On 01.06.2022 18:59, Anthony PERARD wrote:
> Use "define" for the headers*_chk commands as otherwise the "#"
> is interpreted as a comment and make can't find the end of
> $(foreach,).
In cmd_xlat_lst you use $(pound) - any reason this doesn't work in
these rules? Note that I don't mind the use of
On 01.06.2022 18:59, Anthony PERARD wrote:
> --- a/xen/Makefile
> +++ b/xen/Makefile
> @@ -22,6 +22,7 @@ PYTHON_INTERPRETER := $(word 1,$(shell which python3
> python python2 2>/dev/null)
> export PYTHON?= $(PYTHON_INTERPRETER)
>
> export CHECKPOLICY ?= checkpolicy
> +export
On Wed, Jun 01, 2022 at 05:25:16PM +0200, Jan Beulich wrote:
> On 01.06.2022 11:24, Roger Pau Monné wrote:
> > On Wed, Jun 01, 2022 at 09:32:44AM +0200, Jan Beulich wrote:
> >> On 31.05.2022 18:25, Roger Pau Monné wrote:
> >>> On Fri, May 27, 2022 at 01:13:09PM +0200, Jan Beulich wrote:
> @@ -
On 01.06.2022 19:35, Julien Grall wrote:
>
>
> On 31/05/2022 11:53, Daniel P. Smith wrote:
>> On 5/31/22 05:25, Julien Grall wrote:
>>> Hi,
>>>
>>> On 31/05/2022 03:41, Daniel P. Smith wrote:
diff --git a/xen/arch/Kconfig b/xen/arch/Kconfig
index f16eb0df43..57b14e22c9 100644
--- a
c49ee0329ff3 ("SUPPORT.md: limit security support for hosts with very
much memory"), as a result of XSA-385, restricted security support to
8 TiB of host memory. While subsequently further restricted for Arm,
extend this to 12 TiB on x86, putting in place a guest restriction to
8 TiB (or yet less f
On 01.06.2022 22:27, Stefano Stabellini wrote:
> Reducing CC and adding fusa-sig
>
> Actually Jun 9 at 8AM California / 4PM UK doesn't work for some of you,
> so it is either:
> 1) Jun 9 at 7AM California / 3PM UK
> 2) Jun 14 at 8AM California / 4PM UK
>
> My preference is the first option becaus
On 02.06.2022 06:10, Wei Chen wrote:
> Hi Jan,
>
> On 2022/5/31 21:21, Jan Beulich wrote:
>> On 23.05.2022 08:25, Wei Chen wrote:
>>> @@ -119,20 +125,45 @@ int valid_numa_range(paddr_t start, paddr_t end,
>>> nodeid_t node)
>>> return 0;
>
>>
>> To limit indentation depth, on of the two side
flight 170803 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170803/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-amd64-libvirt
flight 170802 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170802/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-win7-amd64 19 guest-stopfail like 170783
test-armhf-armhf-libvirt 16 sav
flight 170801 xen-unstable real [real]
flight 170804 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/170801/
http://logs.test-lab.xenproject.org/osstest/logs/170804/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd6
55 matches
Mail list logo
