Hi Juergen,
On 05/09/2022 13:47, Juergen Gross wrote:
Extend the definition of the Xenstore migration stream to cover new
features:
- per domain features
- extended watches (watch depth)
- per domain quota
Signed-off-by: Juergen Gross
---
V3:
- new patch
V4:
- add new record types instead of
On 31.08.2022 16:10, Volodymyr Babchuk wrote:
> Hello,
>
> This is yet another take to a PCI locking rework. This approach
> was suggest by Jan Beulich who proposed to use a reference
> counter to control lifetime of pci_dev objects.
>
> When I started added reference counting it quickly became
Implement an heuristic for X86 HVM guests which tries to use superpages while
populating guest physmap on live migration. This should impove memory accesses
performances for these guests.
Signed-off-by: Andrei Semenov
---
tools/include/xen-tools/libs.h | 4 ++
On 24.08.2022 16:57, Bertrand Marquis wrote:
> ...because there are some script in automation corresponding to the
> build-* filter (build-test.sh and build-each-commit.sh)
>
> Signed-off-by: Bertrand Marquis
Acked-by: Jan Beulich
From: Penny Zheng
This patch series introduces a new feature: setting up static
shared memory on a dom0less system, through device tree configuration.
This commit parses shared memory node at boot-time, and reserve it in
bootinfo.reserved_mem to avoid other use.
This commits proposes a new
From: Christophe JAILLET
Backport Linux commit 98b64741d611. This is the clean backport without
any changes
kmalloc_array()/kcalloc() should be used to avoid potential overflow
when a multiplication is needed to compute the size of the requested
memory.
So turn a devm_kzalloc()+explicit size
From: Zenghui Yu
Backport Linux commit dc898eb84b25. This is the clean backport without
any changes.
The actual size of level-1 stream table is l1size. This looks like an
oversight on commit d2e88e7c081ef ("iommu/arm-smmu: Fix LOG2SIZE setting
for 2-level stream tables") which forgot to update
Hi Leo,
> On 6 Sep 2022, at 12:31, Leo Yan wrote:
>
> On Arm64 Linux kernel prints log for Xen version number:
>
> [0.00] Xen XEN_VERSION.XEN_SUBVERSION support found
>
> Because the header file "xen/compile.h" is missed, XEN_VERSION and
> XEN_SUBVERSION are not defined, thus
On 30/08/2022 21:27, Jennifer Herbert wrote:
> This patch introduces an optional TPM 2 interface definition to the ACPI
> table,
> which is to be used as part of a vTPM 2 implementation.
> To enable the new interface - I have made the TPM interface version
> configurable in the acpi_config, with
We expose the shared memory to the domU using the "xen,shared-memory-v1"
reserved-memory binding. See
Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
in Linux for the corresponding device tree binding.
To save the cost of re-parsing shared memory device tree configuration
From: Penny Zheng
This commit introduces process_shm to cope with static shared memory in
domain construction.
DOMID_IO will be the default owner of memory pre-shared among multiple domains
at boot time, when no explicit owner is specified.
And DOMID_IO is a fake domain and is not described in
On 06/09/2022 10:52, Jan Beulich wrote:
> On 02.09.2022 04:05, Demi Marie Obenour wrote:
>> On Intel chips (Ice Lake and later) and ARM64, a bit needs to be set in
>> a CPU register to enforce constant-time execution. Linux plans to set
>> this bit by default; Xen should do the same. See
>>
On 05.09.2022 09:00, Juergen Gross wrote:
> A recent change in the hypervisor memory allocation framework led to
> crashes when unplugging host cpus.
>
> This was due to the (correct) assertion that allocating and freeing
> memory is allowed with enabled interrupts only. As the main cpu unplug
>
On 29.08.2022 17:26, Dylanger Daly wrote:
> Please see the attached iomem and meminfo text files from both Qubes under
> Xen and functional Fedora Workstation.
>
> After some investigation, I've seen that I'm able to run a few small VMs just
> fine, however as soon as I start a larger VM, PCI
From: "Gustavo A. R. Silva"
Backport Linux commit 5a1ab5c0299a. This is the clean backport without
any changes.
Fix the following fallthrough warning (arm64-randconfig with Clang):
drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c:382:2: warning: unannotated
fall-through between switch labels
Hi Penny,
On 06/09/2022 08:39, Penny Zheng wrote:
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
flight 173024 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173024/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
Hi Penny,
On 06/09/2022 09:59, Penny Zheng wrote:
static int __init early_scan_node(const void *fdt,
int node, const char *name, int depth,
u32 address_cells, u32 size_cells,
@@ -386,6 +549,8 @@ static int __init
From: Zhou Wang
Backport Linux commit a76a3f2c. Introduce __iomb() in the smmu-v3.c
file with other Linux compatibility definitions.
Reading the 'prod' MMIO register in order to determine whether or
not there is valid data beyond 'cons' for a given queue does not
provide sufficient
Use deffered bitmap only in PV guests context as it not used for HVM guests.
This allow to reduce memory pressure on domain0 while migrating very large
(memory wise) HVM guests.
Signed-off-by: Andrei Semenov
---
tools/libs/guest/xg_sr_common.h | 26 --
On 02.09.2022 15:17, Marek Marczykowski-Górecki wrote:
> Marek Marczykowski-Górecki (10):
> drivers/char: allow using both dbgp=xhci and dbgp=ehci
> console: support multiple serial console simultaneously
> IOMMU: add common API for device reserved memory
> IOMMU/VT-d: wire common device
From: Jean-Philippe Brucker
Backport Linux commit 376cdf66f624. This is the clean backport without
any changes.
When building with C=1, sparse reports some issues regarding
endianness annotations:
arm-smmu-v3.c:221:26: warning: cast to restricted __le64
arm-smmu-v3.c:221:24: warning: incorrect
From: Julien Grall
Since commit 01280dc19cf3 "evtchn: simplify port_is_valid()", the event
channels code assumes that all the buckets below d->valid_evtchns are
always allocated.
This assumption hold in most of the situation because a guest is not
allowed to chose the port. Instead, it will be
Hi Jan,
> -Original Message-
> From: Jan Beulich
> Subject: Re: Xen 4.17 release: Current status before the feature freeze
>
> On 05.09.2022 05:44, Henry Wang wrote:
> > ** x86 **:
> > 1. [v2] x86: show_hvm_stack() requires enabled interrupts
> >
commit fe8f65b018effbf473f53af3538d0c1878b8b329 upstream.
Xen blkfront advertises its support of the persistent grants feature
when it first setting up and when resuming in 'talk_to_blkback()'.
Then, blkback reads the advertised value when it connects with blkfront
and decides if it will use the
Hi Julien,
On Tue, Sep 6, 2022 at 12:25 AM Julien Grall wrote:
>
> Hi Jens,
>
> More remarks.
>
> On 18/08/2022 11:55, Jens Wiklander wrote:
> > +/* Negotiated FF-A version to use with the SPMC */
> > +static uint32_t ffa_version __read_mostly;
>
> NIT: if this is not meant to be modified after
Currently evtchn_alloc_unbound() always allocates the next available
port. Static event channel support for dom0less domains requires
allocating a specified port.
Modify the evtchn_alloc_unbound() to accept the port number as an
argument and allocate the specified port if available. If the port
On Arm64 Linux kernel prints log for Xen version number:
[0.00] Xen XEN_VERSION.XEN_SUBVERSION support found
Because the header file "xen/compile.h" is missed, XEN_VERSION and
XEN_SUBVERSION are not defined, thus compiler directly uses the
string "XEN_VERSION" and "XEN_SUBVERSION" in
On 06.09.2022 14:41, Juergen Gross wrote:
> During a suspend/resume cycle timers on all cpus but cpu 0 will be
> migrated to cpu 0, as the other cpus are taken down.
>
> This is problematic in case such a timer is related to a specific vcpu,
> as the vcpus are not migrated to another cpu during
On 06.09.2022 18:05, Marek Marczykowski-Górecki wrote:
> On Tue, Sep 06, 2022 at 05:11:24PM +0200, Jan Beulich wrote:
>> On 02.09.2022 15:17, Marek Marczykowski-Górecki wrote:
>>> Marek Marczykowski-Górecki (10):
>>> drivers/char: allow using both dbgp=xhci and dbgp=ehci
>>> console: support
In safety-critical environment, it is not considered safe to
dynamically change important configurations at runtime. Everything
should be statically defined and statically verified.
In this case, if the system configuration knows a priori that there are
only 2 VMs and they need to communicate
Hi,
> On 6 Sep 2022, at 08:54, Julien Grall wrote:
>
> Hi Bertrand,
>
> On 06/09/2022 08:24, Bertrand Marquis wrote:
>>> I agree with Julien: I prefer this proposal compared to the earlier one
>>> by Bertrand and Rahul because I think it is a lot clearer and "ENHANCED"
>>> should mean
On Tue, 06 Sep 2022 08:27:47 +0100,
Leo Yan wrote:
>
> On Tue, Sep 06, 2022 at 09:22:00AM +0200, Ard Biesheuvel wrote:
>
> [...]
>
> > > IIUC, you consider the general flow from architecture view, so you prefer
> > > to ask Xen to implement EFI stub to comply the general flow for EFI
> > >
On 03.09.2022 02:24, Stefano Stabellini wrote:
> On Thu, 1 Sep 2022, Rahul Singh wrote:
>> @@ -363,6 +373,39 @@ int __init pci_host_bridge_mappings(struct domain *d)
>> return 0;
>> }
>>
>> +static int is_bar_valid(const struct dt_device_node *dev,
>> +uint64_t
Static event channel support will be added for dom0less domains. Modify
evtchn_bind_interdomain to support static evtchn.
It is necessary to have access to the evtchn_bind_interdomain function
to do that, so make evtchn_bind_interdomain global and also make it
__must_check.
Currently
On 05.09.2022 05:44, Henry Wang wrote:
> ** Blocker List **:
> 1. Patch: x86: enable interrupts around dump_execstate()
> https://patchwork.kernel.org/project/xen-devel/patch/e717897f-980d-ad44-31d9-39f5e7e1c...@suse.com/
> Status: Waiting for review.
>[...]
> ** Arm **:
>[...]
> ** Automation **
Hi Julien,
> -Original Message-
> From: Julien Grall
> > I agree we need to require 64KB alignment, and currently we are following
> > this because we are doing 32MB alignment.
> Hmmm... I think we are talking about two different things here. What I
> am referring to is the alignment of
On 02.09.2022 15:17, Marek Marczykowski-Górecki wrote:
> All (interesting) data is in plain WB cached memory, and the few BAR
> register that are configured have a UC mapping, which orders properly
> WRT other writes on x86.
>
> Suggested-by: Andrew Cooper
> Signed-off-by: Marek
On Tue, Sep 06, 2022 at 01:09:28PM +, Bertrand Marquis wrote:
> Hi Leo,
>
> > On 6 Sep 2022, at 12:31, Leo Yan wrote:
> >
> > On Arm64 Linux kernel prints log for Xen version number:
> >
> > [0.00] Xen XEN_VERSION.XEN_SUBVERSION support found
> >
> > Because the header file
From: Penny Zheng
To add statically shared memory nodes in Dom0, user shall put according
static shared memory configuration under /chosen node.
This commit adds shm-processing function process_shm in construct_dom0
to enable statically shared memory on Dom0.
Signed-off-by: Penny Zheng
Hi Juergen,
On 05/09/2022 13:47, Juergen Gross wrote:
Drop mentioning the non-existent read-only socket in the migration
stream description document.
The related record field was removed in commit 8868a0e3f674 ("docs:
update the xenstore migration stream documentation).
Signed-off-by: Juergen
During a suspend/resume cycle timers on all cpus but cpu 0 will be
migrated to cpu 0, as the other cpus are taken down.
This is problematic in case such a timer is related to a specific vcpu,
as the vcpus are not migrated to another cpu during suspend (migrating
them would break cpupools and core
From: Jean-Philippe Brucker
Backport Linux commit e881e7839fba. Also, move Xen related struct
definition to header to get it compiled.
Allow sharing structure definitions with the upcoming SVA support for
Arm SMMUv3, by moving them to a separate header. We could surgically
extract only what is
Introduce a new sub-node under /chosen node to establish static event
channel communication between domains on dom0less systems.
An event channel will be created beforehand to allow the domains to
send notifications to each other.
Signed-off-by: Rahul Singh
---
Changes in v4:
- move
On Tue, Sep 06, 2022 at 05:07:27PM +0200, Jan Beulich wrote:
> On 02.09.2022 15:17, Marek Marczykowski-Górecki wrote:
> > This allows configuring EHCI and XHCI consoles separately,
> > simultaneously.
> >
> > This changes string_param() to custom_param() in both ehci and xhci
> > drivers. Both
From: Zhen Lei
Backport Linux commit affa909571b0. This is the clean backport without
any changes.
Fixes scripts/checkpatch.pl warning:
WARNING: Possible unnecessary 'out of memory' message
Remove it can help us save a bit of memory.
Signed-off-by: Zhen Lei
Link:
Hi Julien,
> On 6 Sep 2022, at 5:49 pm, Julien Grall wrote:
>
> Hi,
>
> On 06/09/2022 10:55, Rahul Singh wrote:
>> This patch series merge the applicable Linux fixes to Xen.
>> Bixuan Cui (1):
>> xen/arm: smmuv3: Change *array into *const array
>> Christophe JAILLET (1):
>> xen/arm:
flight 173026 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173026/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 1 build-check(1) blocked n/a
build-amd64-libvirt 6
flight 173029 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173029/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 1 build-check(1) blocked n/a
build-amd64-libvirt 6
On Tue, 6 Sep 2022, Penny Zheng wrote:
> If owner property is defined, then owner domain of a static shared memory
> region is not the default dom_io anymore, but a specific domain.
>
> This commit implements allocating static shared memory to a specific domain
> when owner property is defined.
>
Hi,
On 06/09/2022 10:55, Rahul Singh wrote:
This patch series merge the applicable Linux fixes to Xen.
Bixuan Cui (1):
xen/arm: smmuv3: Change *array into *const array
Christophe JAILLET (1):
xen/arm: smmuv3: Avoid open coded arithmetic in memory allocation
Gustavo A. R. Silva (1):
Hi Penny,
On 06/09/2022 08:39, Penny Zheng wrote:
Penny Zheng (6):
xen: do not free reserved memory into heap
xen/arm: introduce CDF_staticmem
xen: unpopulate memory when domain is static
xen: introduce prepare_staticmem_pages
xen: rename free_staticmem_pages to
On 06.09.2022 17:46, Marek Marczykowski-Górecki wrote:
> On Tue, Sep 06, 2022 at 05:07:27PM +0200, Jan Beulich wrote:
>> On 02.09.2022 15:17, Marek Marczykowski-Górecki wrote:
>>> --- a/xen/drivers/char/xhci-dbc.c
>>> +++ b/xen/drivers/char/xhci-dbc.c
>>> @@ -245,6 +245,7 @@ struct dbc {
>>>
On Tue, Sep 06, 2022 at 08:53:02AM +0100, Marc Zyngier wrote:
[...]
> > Okay, I think have two questions for you:
> >
> > - The first question is if we really need to reserve persistent memory
> > for RD pending table and configuration table when Linux kernel runs
> > in Xen domain?
>
> I
[AMD Official Use Only - General]
I am continuously getting following log when I play a file in Dom U:
06.09.22 16:16:38.071 | XenEvtchn | DBG - Notify event channel, port: 76
06.09.22 16:16:38.096 | AlsaPcm | DBG - Frame: 0, bytes: 0, state: 3
06.09.22 16:16:38.096 | RingBuffer | DBG - Send
Hi Stefano,
On 06/09/2022 01:21, Stefano Stabellini wrote:
>
> On Mon, 5 Sep 2022, Michal Orzel wrote:
>> Hi Stefano,
>>
>> On 03/09/2022 01:49, Stefano Stabellini wrote:
>>>
>>>
>>> Currently this test fails with:
>>>
>>> + fdtput binaries/virt-gicv2.dtb -p -t s /pl061@903 status disabled
On Tue, Sep 06, 2022 at 09:23:31AM +0200, Michal Hocko wrote:
> On Mon 05-09-22 19:46:49, Kent Overstreet wrote:
> > On Mon, Sep 05, 2022 at 10:49:38AM +0200, Michal Hocko wrote:
> > > This is really my main concern about this whole work. Not only it adds a
> > > considerable maintenance burden to
Hi Penny,
On 06/09/2022 09:59, Penny Zheng wrote:
+for ( i = 0; i < mem->nr_banks; i++ )
+{
+/*
+ * Meet the following check:
+ * 1) The shm ID matches and the region exactly match
+ * 2) The shm ID doesn't match and the region doesn't overlap
+ *
flight 173020 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173020/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 172123
On 27.08.2022 19:52, Dylanger Daly wrote:
> Thank you for your reply, Xen appears to crash immediately on startup and
> appears to hit the patch
Oh, yes, silly me - map_domain_page() can't be used that way. You
may want to give the replacement patch (below) a try, albeit later
replies of yours
Later, we need to add the right amount of references, which should be
the number of borrower domains, to the owner domain. Since we only have
get_page() to increment the page reference by 1, a loop is needed per
page, which is inefficient and time-consuming.
To save the loop time, this commit
On 30.08.2022 02:52, Henry Wang wrote:
>> -Original Message-
>> From: Jan Beulich
>> Subject: Re: [PATCH v2] x86/public: move XEN_ACPI_ in a new header
>>
>> On 25.08.2022 11:48, Bertrand Marquis wrote:
>>> When Xen is compiled for x86 on an arm machine, libacpi build is failing
>>> due
Borrower domain will fail to get a page ref using the owner domain
during allocation, when the owner is created after borrower.
So here, we decide to get and add the right amount of reference, which
is the number of borrowers, when the owner is allocated.
Signed-off-by: Penny Zheng
Reviewed-by:
Hi Julien,
On Tue, Sep 6, 2022 at 12:17 AM Julien Grall wrote:
>
> Hi Jens,
>
> On 18/08/2022 11:55, Jens Wiklander wrote:
> > Adds a FF-A version 1.1 [1] mediator to communicate with a Secure
> > Partition in secure world.
> >
> > This commit brings in only the parts needed to negotiate FF-A
Hi Viresh,
On Mon, Aug 22, 2022 at 02:45:13PM +0530, Viresh Kumar wrote:
> This patch adds basic support for configuring and assisting virtio-mmio
> based virtio-i2c backend (emualator) which is intended to run out of
> Qemu and could be run in any domain.
"to run out of Qemu" -> this is
On Mon, Aug 22, 2022 at 02:45:15PM +0530, Viresh Kumar wrote:
> Create a separate routine to allocate base and irq for a device as the
> same code will be required for each device type.
>
> Suggested-by: Oleksandr Tyshchenko
> Reviewed-by: Oleksandr Tyshchenko
> Signed-off-by: Viresh Kumar
>
On Mon, Aug 22, 2022 at 02:45:16PM +0530, Viresh Kumar wrote:
> make_virtio_mmio_node() creates the DT node for simple MMIO devices
> currently, i.e. the ones that don't require any additional properties.
>
> In order to allow using it for other complex device types, split the
> functionality
On Mon, Aug 22, 2022 at 02:45:18PM +0530, Viresh Kumar wrote:
> This patch allocates Virtio MMIO params (IRQ and memory region) and pass
> them to the backend, also update Guest device-tree based on Virtio GPIO
> DT bindings [1].
>
> [1]
>
On Fri, Sep 2, 2022 at 12:59 PM Bjorn Helgaas wrote:
>
> The conventional style for subject (from "git log --oneline") is:
>
> xen/pcifront: Handle ...
>
> On Mon, Aug 29, 2022 at 11:15:36AM -0400, Jason Andryuk wrote:
> > An HVM guest with linux stubdom and 2 PCI devices failed to start as
>
>
On Mon, Aug 22, 2022 at 02:45:17PM +0530, Viresh Kumar wrote:
> This also relocates the code responsible to call make_xen_iommu_node()
> towards the end of the routine, so we create the node only once.
Could you do this part in a separate patch? Then, I believe the rest of
the patch could be
On Tue, 6 Sep 2022, Rahul Singh wrote:
> Introduce a new "xen,enhanced" dom0less property value "no-xenstore" to
> disable xenstore interface for dom0less guests.
>
> Signed-off-by: Rahul Singh
> ---
> Changes in v4:
> - Implement defines for dom0less features
> Changes in v3:
> - new patch in
On Tue, 6 Sep 2022, Rahul Singh wrote:
> Introduce a new sub-node under /chosen node to establish static event
> channel communication between domains on dom0less systems.
>
> An event channel will be created beforehand to allow the domains to
> send notifications to each other.
>
>
flight 173028 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173028/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
Hi Julien
> -Original Message-
> From: Julien Grall
> Sent: Wednesday, September 7, 2022 2:01 AM
> To: Penny Zheng ; xen-devel@lists.xenproject.org
> Cc: Wei Chen ; Stefano Stabellini
> ; Bertrand Marquis ;
> Volodymyr Babchuk ; Henry Wang
>
> Subject: Re: [PATCH v7 1/9] xen/arm:
[AMD Official Use Only - General]
FYI
From: Ji, Ruili
Sent: 2022年9月6日 15:40
To: qemu-de...@nongnu.org
Cc: Liu, Aaron
Subject: [PATCH] hw/xen: set pci Atomic Ops requests for passthrough device
>From c54e0714a1e1cac7dc416bd843b9ec7162bcfc47 Mon Sep 17 00:00:00 2001
From: Ruili Ji
flight 173025 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173025/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172128
build-amd64-libvirt
Hi all,
> -Original Message-
> Subject: Xen 4.17 release: Current status before the feature freeze
>
> Hi all,
>
> As the feature freeze date is around the corner (Sep. 9, 2022) and we are
> currently summarizing the series for the release, here are the list of series
> pending in the
On Tue, 6 Sep 2022, Penny Zheng wrote:
> We expose the shared memory to the domU using the "xen,shared-memory-v1"
> reserved-memory binding. See
> Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
> in Linux for the corresponding device tree binding.
>
> To save the cost of
On Tue, 6 Sep 2022, Michal Orzel wrote:
> Introduce support for creating boot-time cpupools in the device tree and
> assigning them to dom0less domUs. Add the following options:
> - CPUPOOL[number]="cpu1_path,...,cpuN_path scheduler" to specify the
>list of cpus and the scheduler to be used
flight 173023 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173023/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-libvirt 6 libvirt-buildfail REGR. vs. 172133
build-i386-libvirt
flight 173033 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173033/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
flight 173022 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173022/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-migrupgrade broken in 173004
Tests
flight 173032 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173032/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
Hi Michal,
> -Original Message-
> From: Michal Orzel
> Subject: Re: [PATCH v2 1/4] docs, xen/arm: Introduce reserved heap memory
>
> Hi Julien,
>
> On 05/09/2022 19:24, Julien Grall wrote:
> >
> > Hi Michal,
> >
> > On 05/09/2022 13:04, Michal Orzel wrote:
> >> On 05/09/2022 09:26,
On 26.08.2022 20:15, Demi Marie Obenour wrote:
> On Fri, Aug 26, 2022 at 09:18:50AM +0200, Jan Beulich wrote:
>> On 25.08.2022 22:36, Demi Marie Obenour wrote:
>>> On Thu, Aug 25, 2022 at 09:59:56AM +0200, Jan Beulich wrote:
On 24.08.2022 23:04, Demi Marie Obenour wrote:
> Fix both of
On Tue, 6 Sept 2022 at 09:17, Leo Yan wrote:
>
> Hi Marc,
>
> On Tue, Sep 06, 2022 at 07:27:17AM +0100, Marc Zyngier wrote:
> > On Tue, 06 Sep 2022 03:52:37 +0100,
> > Leo Yan wrote:
> > >
> > > On Thu, Aug 25, 2022 at 10:40:41PM +0800, Leo Yan wrote:
> > >
> > > [...]
> > >
> > > > > > But here
On 26.08.2022 20:01, Demi Marie Obenour wrote:
> On Fri, Aug 26, 2022 at 09:53:29AM +0200, Jan Beulich wrote:
>> On 25.08.2022 23:52, Demi Marie Obenour wrote:
>>> @@ -40,6 +41,38 @@
>>>
>>> #define efi_data(op) (op.u.efi_runtime_call)
>>>
>>> +static_assert(XEN_PAGE_SHIFT ==
On 29.08.2022 13:00, Wei Chen wrote:
>> -Original Message-
>> From: Jan Beulich
>> Sent: 2022年8月25日 21:06
>>
>> Note that there's an alternative with less #ifdef-ary:
>>
>> config NR_NUMA_NODES
>> int "Maximum number of NUMA nodes supported" if NUMA
>> range 2 64 if NUMA
>>
Hi Marc,
On Tue, Sep 06, 2022 at 07:27:17AM +0100, Marc Zyngier wrote:
> On Tue, 06 Sep 2022 03:52:37 +0100,
> Leo Yan wrote:
> >
> > On Thu, Aug 25, 2022 at 10:40:41PM +0800, Leo Yan wrote:
> >
> > [...]
> >
> > > > > But here I still cannot create the concept that how GIC RD tables play
> >
On Mon 05-09-22 19:46:49, Kent Overstreet wrote:
> On Mon, Sep 05, 2022 at 10:49:38AM +0200, Michal Hocko wrote:
> > This is really my main concern about this whole work. Not only it adds a
> > considerable maintenance burden to the core MM because
>
> [citation needed]
I thought this was clear
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
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: Julien Grall
Acked-by: Jan Beulich
---
v12 changes:
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
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
The name of free_staticmem_pages is inappropriate, considering it is
the opposite of function prepare_staticmem_pages.
Rename free_staticmem_pages to unprepare_staticmem_pages.
Signed-off-by: Penny Zheng
Acked-by: Jan Beulich
---
v12 changes:
- no change
---
v11 changes:
- moved ahead of "xen:
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.
flight 173018 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173018/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
On 01.09.2022 11:29, Rahul Singh wrote:
> is_memory_hole was implemented for x86 and not for ARM when introduced.
> Replace is_memory_hole call to pci_check_bar as function should check
> if device BAR is in defined memory range. Also, add an implementation
> for ARM which is required for PCI
On 29.08.2022 12:47, Wei Chen wrote:
>> -Original Message-
>> From: Jan Beulich
>> Sent: 2022年8月25日 20:50
>>
>> On 22.08.2022 04:58, Wei Chen wrote:
>>> +bool __init numa_memblks_available(void)
>>> +{
>>> +return num_node_memblks < NR_NODE_MEMBLKS;
>>> +}
>>
>> This is kind of
1 - 100 of 164 matches
Mail list logo
