As it is coming up basically every release cycle of Xen, add a
reference to the discussion why the current release scheme has been
selected in the release management documentation.
Signed-off-by: Juergen Gross
---
docs/process/xen-release-management.pandoc | 2 ++
1 file changed, 2
flight 171547 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/171547/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-credit1 8 xen-boot fail REGR. vs. 171277
On Fri, Jul 8, 2022 at 12:38 AM Jan Beulich wrote:
>
> On 07.07.2022 17:24, G.R. wrote:
> > On Wed, Jul 6, 2022 at 2:33 PM Jan Beulich wrote:
> >>
> >> On 06.07.2022 08:25, G.R. wrote:
> >>> On Tue, Jul 5, 2022 at 7:59 PM Jan Beulich wrote:
> Nothing useful in there. Yet independent of
On Wed, Jul 06, 2022 at 05:32:06PM +0200, Marek Marczykowski-Górecki wrote:
> diff --git a/xen/drivers/char/Kconfig b/xen/drivers/char/Kconfig
> index e5f7b1d8eb8a..d12b2205dafc 100644
> --- a/xen/drivers/char/Kconfig
> +++ b/xen/drivers/char/Kconfig
> @@ -74,3 +74,12 @@ config HAS_EHCI
>
On Thu, 7 Jul 2022, Xenia Ragiadakou wrote:
> The EXPERT config option cannot anymore be selected via the environmental
> variable XEN_CONFIG_EXPERT. Remove stale references to XEN_CONFIG_EXPERT
> from the automation code.
>
> Signed-off-by: Xenia Ragiadakou
Reviewed-by: Stefano Stabellini
>
On Thu, 7 Jul 2022, Julien Grall wrote:
> Hi Xenia,
>
> On 07/07/2022 21:38, Xenia Ragiadakou wrote:
> > Add an arm subdirectory under automation/configs for the arm specific
> > configs
> > and add a config that enables static allocation.
> >
> > Modify the build script to search for configs
flight 171545 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/171545/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 171516
test-armhf-armhf-libvirt 16
Hi Xenia,
On 07/07/2022 21:38, Xenia Ragiadakou wrote:
Add an arm subdirectory under automation/configs for the arm specific configs
and add a config that enables static allocation.
Modify the build script to search for configs also in this subdirectory and to
keep the generated xen binary,
Add an arm subdirectory under automation/configs for the arm specific configs
and add a config that enables static allocation.
Modify the build script to search for configs also in this subdirectory and to
keep the generated xen binary, suffixed with the config file name, as artifact.
Create a
This patch series
- removes all the references to the XEN_CONFIG_EXPERT environmental variable
which is not used anymore
- creates a trivial arm64 test job that boots xen on qemu with a direct mapped
dom0less domu with static memory and verifies, based on its logs, that the
domu's memory node
The EXPERT config option cannot anymore be selected via the environmental
variable XEN_CONFIG_EXPERT. Remove stale references to XEN_CONFIG_EXPERT
from the automation code.
Signed-off-by: Xenia Ragiadakou
---
automation/build/README.md | 3 ---
automation/scripts/build| 4 ++--
flight 171544 qemu-mainline real [real]
flight 171549 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/171544/
http://logs.test-lab.xenproject.org/osstest/logs/171549/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not
Hi Jan,
As discussed in [1], I think it would good to revive this patch.
AFAICT, this patch was dropped because the performance was thought to be
minimal. However, I think it would be a better way to resolve the
problem that one is trying to address [1].
So I will do another review of this
On 07.07.2022 17:24, G.R. wrote:
> On Wed, Jul 6, 2022 at 2:33 PM Jan Beulich wrote:
>>
>> On 06.07.2022 08:25, G.R. wrote:
>>> On Tue, Jul 5, 2022 at 7:59 PM Jan Beulich wrote:
Nothing useful in there. Yet independent of that I guess we need to
separate the issues you're seeing.
On 07.07.2022 17:36, G.R. wrote:
> On Thu, Jul 7, 2022 at 11:24 PM G.R. wrote:
>>
>> On Wed, Jul 6, 2022 at 2:33 PM Jan Beulich wrote:
>>>
Should I expect a debug build of XEN hypervisor to give better
diagnose messages, without the debug patch that Roger mentioned?
>>>
>>> Well,
On 17.05.2022 17:31, Roger Pau Monne wrote:
> Roger Pau Monne (3):
> amd/msr: implement VIRT_SPEC_CTRL for HVM guests on top of SPEC_CTRL
> amd/msr: allow passthrough of VIRT_SPEC_CTRL for HVM guests
> amd/msr: implement VIRT_SPEC_CTRL for HVM guests using legacy SSBD
While, somewhat
On Wed, Jul 6, 2022 at 12:22 PM Christopher Clark
wrote:
>
> On Tue, Jun 28, 2022 at 11:24 PM Juergen Gross wrote:
> >
> > On 24.03.22 15:01, Juergen Gross wrote:
> > > Today most hypercall handlers have a return type of long, while the
> > > compat ones return an int. There are a few exceptions
Andrew,
On 24.03.2022 15:01, Juergen Gross wrote:
> Juergen Gross (9):
> xen: move do_vcpu_op() to arch specific code
> xen: harmonize return types of hypercall handlers
> xen: don't include asm/hypercall.h from C sources
> xen: include compat/platform.h from hypercall.h
> xen: generate
On Thu, Jul 7, 2022 at 11:24 PM G.R. wrote:
>
> On Wed, Jul 6, 2022 at 2:33 PM Jan Beulich wrote:
> >
> > > Should I expect a debug build of XEN hypervisor to give better
> > > diagnose messages, without the debug patch that Roger mentioned?
> >
> > Well, "expect" is perhaps too much to say, but
Hi Julien,
> On 7 Jul 2022, at 16:33, Julien Grall wrote:
>
> Hi Jiamei,
>
> On 06/07/2022 09:25, Jiamei Xie wrote:
>> virt_vtimer_save() will calculate the next deadline when the vCPU is
>> scheduled out. At the moment, Xen will use the following equation:
>> virt_timer.cval +
Hi Jiamei,
On 06/07/2022 09:25, Jiamei Xie wrote:
virt_vtimer_save() will calculate the next deadline when the vCPU is
scheduled out. At the moment, Xen will use the following equation:
virt_timer.cval + virt_time_base.offset - boot_count
The three values are 64-bit and one (cval) is
On Wed, Jul 6, 2022 at 2:33 PM Jan Beulich wrote:
>
> On 06.07.2022 08:25, G.R. wrote:
> > On Tue, Jul 5, 2022 at 7:59 PM Jan Beulich wrote:
> >> Nothing useful in there. Yet independent of that I guess we need to
> >> separate the issues you're seeing. Otherwise it'll be impossible to
> >> know
flight 171542 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/171542/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-credit1 8 xen-boot fail REGR. vs. 171277
> On 13 Apr 2022, at 12:21, Jane Malalane wrote:
>
> Introduce a new per-domain creation x86 specific flag to
> select whether hardware assisted virtualization should be used for
> x{2}APIC.
>
> A per-domain option is added to xl in order to select the usage of
> x{2}APIC hardware assisted
> On 13 Apr 2022, at 12:21, Jane Malalane wrote:
>
> Add XEN_SYSCTL_PHYSCAP_X86_ASSISTED_XAPIC and
> XEN_SYSCTL_PHYSCAP_X86_ASSISTED_X2APIC to report accelerated xAPIC and
> x2APIC, on x86 hardware. This is so that xAPIC and x2APIC virtualization
> can subsequently be enabled on a per-domain
On 07.07.22 16:45, Anthony PERARD wrote:
On Fri, Jun 24, 2022 at 11:28:06AM +0200, Juergen Gross wrote:
In case of maxmem != memsize the E820 map of the PVH stubdom is wrong,
as it is missing the RAM above memsize.
Additionally the MMIO area should only cover the HVM special pages.
On Fri, Jun 24, 2022 at 11:28:06AM +0200, Juergen Gross wrote:
> In case of maxmem != memsize the E820 map of the PVH stubdom is wrong,
> as it is missing the RAM above memsize.
>
> Additionally the MMIO area should only cover the HVM special pages.
>
> Signed-off-by: Juergen Gross
> ---
>
flight 171546 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/171546/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 5496c763aaddc4a47639d4652abe23aa3419263a
baseline version:
ovmf
Hi Juergen,
> On 6 Jul 2022, at 12:33 pm, Juergen Gross wrote:
>
> On 06.07.22 13:04, Julien Grall wrote:
>> (+ Juergen for the Linux question)
>> On 06/07/2022 11:42, Rahul Singh wrote:
>>> Hi Julien,
>>>
On 5 Jul 2022, at 2:56 pm, Julien Grall wrote:
On
On Thu, Jul 7, 2022 at 6:14 AM Daniel P. Smith
wrote:
>
> On 7/6/22 15:13, Jason Andryuk wrote:
> > flask_domain_alloc_security and flask_domain_create has special code to
> > magically label dom0 as dom0_t. This can all be streamlined by making
> > create_dom0 set ssidref before creating dom0.
Hi Jan,
On Thu, Jul 07, 2022 at 01:55:30PM +0200, Jan Beulich wrote:
> On 07.07.2022 12:35, Oleksii Moisieiev wrote:
> > # Synopsis
> > This document is intended to describe the design of the thermal based cpu
> > throttling in virtualized environments. The goal is to provide generic
> > thermal
On 07.07.2022 13:58, Wei Chen wrote:
> Hi Jan,
>
> On 2022/7/6 13:44, Henry Wang wrote:
>> Hi Jan,
>>
>>> -Original Message-
>>> Subject: Re: [PATCH] EFI: strip xen.efi when putting it on the EFI partition
>>>
>>> On 09.06.2022 17:52, Jan Beulich wrote:
With debug info retained,
Hi Jan,
On 2022/7/6 13:44, Henry Wang wrote:
Hi Jan,
-Original Message-
Subject: Re: [PATCH] EFI: strip xen.efi when putting it on the EFI partition
On 09.06.2022 17:52, Jan Beulich wrote:
With debug info retained, xen.efi can be quite large. Unlike for xen.gz
there's no
On 07.07.2022 12:35, Oleksii Moisieiev wrote:
> # Synopsis
> This document is intended to describe the design of the thermal based cpu
> throttling in virtualized environments. The goal is to provide generic thermal
> management subsystem, which should work with existing cpufreq subsystem in XEN
>
On 07.07.2022 11:22, 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
Acked-by:
On 07.07.2022 11:39, Juergen Gross wrote:
> Switch to use the newest Mini-OS commit in order to get the recent
> fixes.
>
> Signed-off-by: Juergen Gross
Acked-by: Jan Beulich
On Thu, Jul 07, 2022 at 09:22:26AM +0100, Marc Zyngier wrote:
> On Tue, 05 Jul 2022 14:52:43 +0100,
> Serge Semin wrote:
> >
> > Hi Samuel
> >
> > On Fri, Jul 01, 2022 at 03:00:49PM -0500, Samuel Holland wrote:
> > > The MIPS GIC irqchip driver may be selected in a uniprocessor
> > >
# Synopsis
This document is intended to describe the design of the thermal based cpu
throttling in virtualized environments. The goal is to provide generic thermal
management subsystem, which should work with existing cpufreq subsystem in XEN
and could be used on various architectures and
flight 171541 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/171541/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-arm64-libvirt
On 7/6/22 15:13, Jason Andryuk wrote:
flask_domain_alloc_security and flask_domain_create has special code to
magically label dom0 as dom0_t. This can all be streamlined by making
create_dom0 set ssidref before creating dom0.
Hmm, I wouldn't call it magical, it is the initialization policy
flight 171538 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/171538/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-pair broken in 171536
Tests
On 07.07.22 11:39, Marc Zyngier wrote:
Hello Marc
> On Sun, 03 Jul 2022 16:22:03 +0100,
> Oleksandr wrote:
>>
>> On 01.07.22 23:00, Samuel Holland wrote:
>>
>>
>> Hello Samuel
>>
>>> Some architectures and irqchip drivers modify the cpumask returned by
>>> irq_data_get_affinity_mask, usually
Switch to use the newest Mini-OS commit in order to get the recent
fixes.
Signed-off-by: Juergen Gross
---
Config.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Config.mk b/Config.mk
index a806ef0afb..e56844d964 100644
--- a/Config.mk
+++ b/Config.mk
@@ -230,7 +230,7 @@
Later, we want to use acquire_domstatic_pages() for populating memory
for static domain on runtime, however, there are a lot of pointless work
(checking mfn_valid(), scrubbing the free part, cleaning the cache...)
considering we know the page is valid and belong to the guest.
This commit splits
Ping?
On 24.06.22 11:28, Juergen Gross wrote:
In case of maxmem != memsize the E820 map of the PVH stubdom is wrong,
as it is missing the RAM above memsize.
Additionally the MMIO area should only cover the HVM special pages.
Signed-off-by: Juergen Gross
---
When a static domain populates memory through populate_physmap at runtime,
it shall retrieve reserved pages from resv_page_list to make sure that
guest RAM is still restricted in statically configured memory regions.
This commit also introduces a new helper acquire_reserved_page to make it work.
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
---
v8 changes:
- #ifdef-ary around is_domain_using_staticmem()
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 be used for any other purposes, so they shall never
With more and more CDF_xxx internal flags in and to save the space, this
commit introduces a new field "flags" in struct domain to store CDF_*
internal flags directly.
Another new CDF_xxx will be introduced in the next patch.
Signed-off-by: Penny Zheng
Acked-by: Julien Grall
---
v8 changes:
-
The code in free_heap_pages() will try to merge pages with the
successor/predecessor if pages are suitably aligned. So if the pages
reserved are right next to the pages given to the heap allocator,
free_heap_pages() will merge them, and give the reserved pages to heap
allocator accidently as a
PGC_reserved could be ambiguous, and we have to tell what the pages are
reserved for, so this commit intends to rename PGC_reserved to
PGC_static, which clearly indicates the page is reserved for static
memory.
Signed-off-by: Penny Zheng
Acked-by: Jan Beulich
---
v8 changes
- no change
---
v7
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
Reviewed-by: Stefano Stabellini
---
v8 changes:
- no change
---
v7 changes:
- no change
---
v6
Pages used as guest RAM for static domain, shall be reserved to this
domain only.
So in case reserved pages being used for other purpose, users
shall not free them back to heap, even when last ref gets dropped.
This commit introduces a new helper free_domstatic_page to free
static page in
Today when a domain unpopulates the memory on runtime, they will always
hand the memory over to the heap allocator. And it will be a problem if it
is a static domain.
Pages used as guest RAM for static domain shall always be reserved to this
domain only, and not be used for any other purposes, so
On Sun, 03 Jul 2022 16:22:03 +0100,
Oleksandr wrote:
>
>
> On 01.07.22 23:00, Samuel Holland wrote:
>
>
> Hello Samuel
>
> > Some architectures and irqchip drivers modify the cpumask returned by
> > irq_data_get_affinity_mask, usually by copying in to it. This is
> > problematic for
flight 171539 qemu-mainline real [real]
flight 171543 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/171539/
http://logs.test-lab.xenproject.org/osstest/logs/171543/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
On Tue, 05 Jul 2022 14:52:43 +0100,
Serge Semin wrote:
>
> Hi Samuel
>
> On Fri, Jul 01, 2022 at 03:00:49PM -0500, Samuel Holland wrote:
> > The MIPS GIC irqchip driver may be selected in a uniprocessor
> > configuration, but it unconditionally registers an IPI domain.
> >
> > Limit the part
On 07.07.2022 09:27, Xenia Ragiadakou wrote:
> On 7/6/22 11:51, Jan Beulich wrote:
>> On 06.07.2022 10:43, Xenia Ragiadakou wrote:
>>> On 7/6/22 10:10, Jan Beulich wrote:
On 05.07.2022 23:02, Xenia Ragiadakou wrote:
> The function idle_loop() is referenced only in domain.c.
> Change
Hi Jan,
On 7/6/22 11:51, Jan Beulich wrote:
On 06.07.2022 10:43, Xenia Ragiadakou wrote:
On 7/6/22 10:10, Jan Beulich wrote:
On 05.07.2022 23:02, Xenia Ragiadakou wrote:
The function idle_loop() is referenced only in domain.c.
Change its linkage from external to internal by adding the
flight 171540 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/171540/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf f193b945eac58ca379d3d21c77d5550b063580d6
baseline version:
ovmf
On 06.07.2022 19:01, Borislav Petkov wrote:
> On Wed, Jul 06, 2022 at 08:17:41AM +0200, Jan Beulich wrote:
>> Sure, but that alone won't help.
>
> Well, the MTRR code looks at X86_FEATURE_MTRR. If Xen doesn't expose the
> MTRRs, then that bit should be clear in the CPUID the guest sees.
>
> So
On 05.07.2022 14:41, Jan Beulich wrote:
> For a long time we've been rather inefficient with IOMMU page table
> management when not sharing page tables, i.e. in particular for PV (and
> further specifically also for PV Dom0) and AMD (where nowadays we never
> share page tables). While up to about
62 matches
Mail list logo
