On 29.08.2022 11:49, Wei Chen wrote:
>> -Original Message-
>> From: Jan Beulich
>> Sent: 2022年8月25日 18:58
>>
>> On 22.08.2022 04:58, Wei Chen wrote:
>>> +nodemask_t __read_mostly node_online_map = { { [0] = 1UL } };
>>> +
>>> +bool __read_mostly numa_off;
>>
>> This, otoh, can be, or have
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 clumsy,
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 Jan
> -Original Message-
> From: Jan Beulich
> Sent: Tuesday, September 6, 2022 2:34 PM
> To: Penny Zheng
> Cc: Wei Chen ; Andrew Cooper
> ; George Dunlap ;
> Julien Grall ; Stefano Stabellini ;
> Wei Liu ; xen-devel@lists.xenproject.org
> Subject: Re: [PATCH v10 8/9] xen: retrieve re
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 06.09.2022 09:14, Penny Zheng wrote:
> Hi Jan
>
>> -Original Message-
>> From: Jan Beulich
>> Sent: Tuesday, September 6, 2022 2:34 PM
>> To: Penny Zheng
>> Cc: Wei Chen ; Andrew Cooper
>> ; George Dunlap ;
>> Julien Grall ; Stefano Stabellini ;
>> Wei Liu ; xen-devel@lists.xenproject
Hi Julien,
> On 5 Sep 2022, at 17:55, Julien Grall wrote:
>
>
>
> On 05/09/2022 17:49, Rahul Singh wrote:
>> Hi Julien,
>
> Hi Rahul,
>
>>> On 5 Sep 2022, at 5:37 pm, Julien Grall wrote:
>>>
>>>
>>>
>>> On 05/09/2022 17:30, Rahul Singh wrote:
From: Zhou Wang
Backport Linux com
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 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 f
Hi Stefano,
> On 5 Sep 2022, at 23:41, Stefano Stabellini wrote:
>
> On Mon, 5 Sep 2022, Rahul Singh wrote:
>>> On 5 Sep 2022, at 1:59 pm, Bertrand Marquis
>>> wrote:
>>>
>>> Hi Julien,
>>>
On 5 Sep 2022, at 13:08, Julien Grall wrote:
On 05/09/2022 12:54, Bertran
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
> > booting sequence, right?
> >
> > If the conclusion is to change Xen for s
During boot-time there are many PCI config reads, these could be performed
either using Port IO instructions (PIO) or memory mapped I/O (MMIO).
PIO are less efficient than MMIO, they require twice as many PCI accesses
and PIO instructions are serializing. As a result, MMIO should be preferred
when
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 runtime,
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 t
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 g
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 ac
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.
S
On Tue, Sep 06, 2022 at 03:27:47PM +0800, 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
> > > bo
On Tue, 06 Sep 2022 08:17:14 +0100,
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:
> > >
> > > [...]
> > >
> > > > >
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 everything. Also, it makes it easier from a compatibility
perspective because it
On Mon 05-09-22 11:03:35, Suren Baghdasaryan wrote:
> On Mon, Sep 5, 2022 at 1:12 AM Michal Hocko wrote:
> >
> > On Sun 04-09-22 18:32:58, Suren Baghdasaryan wrote:
> > > On Thu, Sep 1, 2022 at 12:15 PM Michal Hocko wrote:
> > [...]
> > > > Yes, tracking back the call trace would be really needed
Hi Henry and Michal,
On 06/09/2022 07:41, Henry Wang wrote:
-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
flight 173011 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173011/
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
build-i386-libvir
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 passt
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 over
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 Kcon
Hi Henry
On 06/09/2022 02:53, Henry Wang wrote:
Thanks for your comments, I added my reply and some of the questions
that I am not 100% sure inline below.
-Original Message-
From: Julien Grall
Hi Henry,
+
+/*
+ * Find the contiguous xenheap region that fits in the reserved heap regio
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.
Coding flow for dealing borrower domain will be in
This commit sets up shared memory foreign mapping for borrower domain.
If owner domain is the default dom_io, all shared domain are treated as
borrower domain.
Signed-off-by: Penny Zheng
Reviewed-by: Stefano Stabellini
---
v7 change:
- no changes
---
v6 change:
- no change
---
v5 change:
- no c
on ARM, static memory sharing is tech preview, which shall be documented
in SUPPORT.md
Signed-off-by: Penny Zheng
---
v7 changes:
- doc refinement
---
v6 change:
- new commit
---
SUPPORT.md | 7 +++
1 file changed, 7 insertions(+)
diff --git a/SUPPORT.md b/SUPPORT.md
index 8e040d1c1e..19798
On 02.09.2022 15:17, Marek Marczykowski-Górecki wrote:
> When cable is unplugged, dbc_ensure_running() correctly detects this
> situation (DBC_CTRL_DCR flag is clear), and prevent sending data
> immediately to the device. It gets only queued in work ring buffers.
> When cable is plugged in again, s
Hi Julien,
> On 3 Sep 2022, at 8:18 am, Julien Grall wrote:
>
> Hi Rahul,
>
> On 01/09/2022 10: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 define
Hi Jens,
On Thu, Aug 18, 2022 at 12:55:55PM +0200, Jens Wiklander wrote:
> diff --git a/tools/libs/light/libxl_arm.c b/tools/libs/light/libxl_arm.c
> index eef1de093914..a985609861c7 100644
> --- a/tools/libs/light/libxl_arm.c
> +++ b/tools/libs/light/libxl_arm.c
> @@ -101,6 +101,9 @@ int libxl__a
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
> https://lore.kernel.org/lkml/ywgcrqutxmx0w...@gmail
On 06/09/2022 10:39, Rahul Singh wrote:
Hi Julien,
On 3 Sep 2022, at 8:18 am, Julien Grall wrote:
Hi Rahul,
On 01/09/2022 10: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 chec
This 2 patches implement some optimisations for guests live migraiton.
Andrei Semenov (2):
live migration: do not use deffered bitmap when inappropriate
live migration: use superpages for physmap population on restore when
possible
tools/include/xen-tools/libs.h | 4 ++
tools
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):
xen/arm: smmuv3: Fix fall-through warning for Clang
From: Robin Murphy
Backport Linux commit 86d2d9214880. This is the clean backport without
any changes.
Since we now keep track of page 1 via a separate pointer that
already encapsulates aliasing to page 0 as necessary, we can remove
the clunky fixup routine and simply use the relevant bases dire
From: Zenghui Yu
Backport Linux commit e0bb4b735404. This is the clean backport without
any changes.
Per SMMUv3 spec, there is no Size and Addr field in the
PREFETCH_CONFIG command and they're not used by the driver.
Remove them.
We can add them back if we're going to use PREFETCH_ADDR in the
f
From: Bixuan Cui
Backport Linux commit d56d5162e317. This is the clean backport without
any changes.
Fix checkpatch warning in arm-smmu-v3.c:
static const char * array should probably be static const char
* const
Signed-off-by: Bixuan Cui
Signed-off-by: Will Deacon
Origin: git://git.kernel.or
(shortening Cc list)
On 05.09.2022 16:59, Anthony PERARD wrote:
> On Mon, Sep 05, 2022 at 03:44:33AM +, Henry Wang wrote:
>> ** Common **:
>> 10. [XEN,v2] build: Fix x86 out-of-tree build without EFI
>> https://patchwork.kernel.org/project/xen-devel/list/?series=668331
>> Status: Reviewed but
On 06.09.2022 09: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 a new
On 01.09.2022 00:12, Dylanger Daly wrote:
> I think I've narrowed the issue down to a PCI device, if I start 2 large VM,
> then simply run lspci in dom0, it'll trigger a crash.
>
> This makes sense as sys-net works fine until I start a larger VM, then I see
> a 'chip reset' error in the appVM's
Hi Julien,
Thanks for the clarification and your patience. For the
populate_boot_allocator() change, I attached my change in the end,
and personally I would like to hear your opinion before sending v3
since we now have limited time.
> -Original Message-
> From: Julien Grall
> >>> +
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 to create cpupool
- NUM_CPUPOOLS to specify the n
On 22.08.22 17:34, Juergen Gross wrote:
On 21.08.22 18:14, Marek Marczykowski-Górecki wrote:
On Sat, Oct 09, 2021 at 06:28:17PM +0200, Marek Marczykowski-Górecki wrote:
On Sun, Jan 31, 2021 at 03:15:30AM +0100, Marek Marczykowski-Górecki wrote:
On Tue, Sep 29, 2020 at 05:27:48PM +0200, Jürgen
Hi Penny,
On 06/09/2022 10:59, Penny Zheng wrote:
>
> on ARM, static memory sharing is tech preview, which shall be documented
> in SUPPORT.md
>
> Signed-off-by: Penny Zheng
Reviewed-by: Michal Orzel
~Michal
flight 173013 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173013/
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 whi
On Tue, Sep 06, 2022 at 01:46:55PM +0200, Juergen Gross wrote:
> On 22.08.22 17:34, Juergen Gross wrote:
> > On 21.08.22 18:14, Marek Marczykowski-Górecki wrote:
> > > On Sat, Oct 09, 2021 at 06:28:17PM +0200, Marek Marczykowski-Górecki
> > > wrote:
> > > > On Sun, Jan 31, 2021 at 03:15:30AM +0100
Hi Henry,
On 06/09/2022 12:11, Henry Wang wrote:
-Original Message-
From: Julien Grall
+{
+bank_start = bootinfo.reserved_mem.bank[i].start;
+bank_size = bootinfo.reserved_mem.bank[i].size;
+bank_end = bank_start + bank_size;
+
+i
On Mon, Sep 5, 2022 at 9:50 AM Marek Marczykowski-Górecki
wrote:
>
> When vchan client reconnect quickly, the server may not notice it. This
> means, it won't reconnect the UNIX socket either. For QMP, it will
> prevent the client to see the QMP protocol handshake, and the
> communication will tim
On Mon, Sep 5, 2022 at 9:50 AM Marek Marczykowski-Górecki
wrote:
>
> This enables stubdom reliably detect when it needs to reconnect QMP
> socket. It is critical, as otherwise QEMU will not send its handshake,
> and so libxl will timeout while waiting on one. When it happens during
> domain startu
flight 173017 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173017/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-armhf-libvirt
flight 173015 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173015/
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
On 9/1/22 08:55, Jason Andryuk wrote:
> On Tue, Aug 30, 2022 at 4:30 PM 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 TP
The purpose of this patch series is to add the static event channel signaling
support to Xen on Arm based on design doc [1].
[1] https://lists.xenproject.org/archives/html/xen-devel/2022-05/msg01160.html
Julien Grall (1):
xen/evtchn: Make sure all buckets below d->valid_evtchns are allocated
R
From: Stanislav Kinsburskii
In a follow-up patch we will want to either reserve or allocate a port
for various event channel helpers.
A new wrapper is introduced to either reserve a given port or allocate
a fresh one if zero.
Take the opportunity to replace the open-coded version in
evtchn_bind
Restrict the maximum number of evtchn supported for domUs to avoid
allocating a large amount of memory in Xen.
Set the default value of max_evtchn_port to 1023. The value of 1023
should be sufficient for domUs guests because on ARM we don't bind
physical interrupts to event channels. The only use
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 this version
---
docs/misc/arm/device-tree/booting.txt |
On 06.09.2022 15:40, Rahul Singh wrote:
> 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 i
flight 173021 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173021/
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 Jan,
> -Original Message-
> From: Jan Beulich
> > Acked-by: Henry Wang # For the 4.17 release
>
> I've translated this to Release-acked-by: (as was used for earlier releases).
Thanks for letting me know this! I will keep in mind and use this in the future.
Kind regards,
Henry
>
flight 173016 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173016/
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 Andrew,
(+ Anthony as I believe he is the toolstack maintainer)
> -Original Message-
> From: Andrew Cooper
> Subject: Re: [for-4.17 PATCH] acpi: Add TPM2 interface definition and make
> the TPM version configurable.
>
> On 30/08/2022 21:27, Jennifer Herbert wrote:
> > This patch intr
Hi Rahul,
> On 6 Sep 2022, at 10:55, Rahul Singh wrote:
>
> 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
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 drivers parse only values applicable to them.
>
> While at it, drop unneces
On Tue, 06 Sep 2022 16:13:25 +0100,
Leo Yan wrote:
>
> 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 c
On Tue, Sep 6, 2022 at 1:01 AM Michal Hocko wrote:
>
> On Mon 05-09-22 11:03:35, Suren Baghdasaryan wrote:
> > On Mon, Sep 5, 2022 at 1:12 AM Michal Hocko wrote:
> > >
> > > On Sun 04-09-22 18:32:58, Suren Baghdasaryan wrote:
> > > > On Thu, Sep 1, 2022 at 12:15 PM Michal Hocko 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 multiple serial console simultaneously
> > IOMMU: add comm
On Mon, Aug 22, 2022 at 02:45:14PM +0530, Viresh Kumar wrote:
> This patch adds basic support for configuring and assisting virtio-mmio
> based virtio-gpio backend (emualator) which is intended to run out of
> Qemu and could be run in any domain.
>
> An example of domain configuration for Virtio G
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):
x
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 a
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 unprepare_staticme
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
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: smmuv3:
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
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:
+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
+ *
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 early_sca
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
build-i386-libvir
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 lib
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 ambiguou
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 squas
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 into
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]
> https://www.kernel.org/doc/Documentation/devicetree/bindi
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 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 ha
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 intr
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 to
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 ver
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
nu
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 th
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 su
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 t
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
> > https://patchwork.kernel.org/project/xen-
1 - 100 of 159 matches
Mail list logo
