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
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
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
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
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
On Mon, 5 Sep 2022 11:44:55 -0700
Nadav Amit wrote:
> I would note that I have a solution in the making (which pretty much works)
> for this matter, and does not require any kernel changes. It produces a
> call stack that leads to the code that lead to syscall failure.
>
> The way it works is
flight 173000 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173000/
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
From: Zhou Wang
Backport Linux commit a76a3f2c. Rename __iomb to iomb() while
merging to get in sync with other Xen 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 dependency
Hi,
On 05/09/2022 14:36, Rahul Singh wrote:
Please have a look once if this looks okay.
/*
* List of possible features for dom0less domUs
*
* DOM0LESS_ENHANCED_BASIC:Notify the OS it is running on top of Xen. All
the
*
Hi Julien,
> On 5 Sep 2022, at 5:40 pm, Julien Grall wrote:
>
> Hi,
>
> On 05/09/2022 14:36, Rahul Singh wrote:
>> Please have a look once if this looks okay.
>> /*
>> * List of possible features for dom0less domUs
>> *
>> * DOM0LESS_ENHANCED_BASIC: Notify the OS it is running on top of
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 commit a76a3f2c. Rename __iomb to iomb() while
merging to get in sync with other Xen definitions.
On Aug 31, 2022, at 3:19 AM, Mel Gorman wrote:
> On Wed, Aug 31, 2022 at 04:42:30AM -0400, Kent Overstreet wrote:
>> On Wed, Aug 31, 2022 at 09:38:27AM +0200, Peter Zijlstra wrote:
>>> On Tue, Aug 30, 2022 at 02:48:49PM -0700, Suren Baghdasaryan wrote:
===
Code
On Mon, Sep 05, 2022 at 11:08:21AM -0700, Suren Baghdasaryan wrote:
> On Mon, Sep 5, 2022 at 8:06 AM Steven Rostedt wrote:
> >
> > On Sun, 4 Sep 2022 18:32:58 -0700
> > Suren Baghdasaryan wrote:
> >
> > > Page allocations (overheads are compared to get_free_pages() duration):
> > > 6.8% Codetag
flight 173003 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173003/
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
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 Julien,
> 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 commit a76a3f2c. Rename __iomb to iomb() while
>> merging to get in sync with other Xen definitions.
>> Reading the 'prod' MMIO register in
Hi Michal,
On 05/09/2022 13:04, Michal Orzel wrote:
On 05/09/2022 09:26, Henry Wang wrote:
diff --git a/xen/arch/arm/include/asm/setup.h b/xen/arch/arm/include/asm/setup.h
index 5815ccf8c5..d0cc556833 100644
--- a/xen/arch/arm/include/asm/setup.h
+++ b/xen/arch/arm/include/asm/setup.h
@@
Hi Jan,
I've managed to finangle a very unstable environment together
What I'm seeing is the following:
1. All appVMs including dom0 must have 1 core assigned
2. This means I'm able to launch 4 appVMs, as soon as I launch a 5th, it puts
all PCIe devices into a bad state
3. If I shut the 5th VM
flight 172994 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172994/
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
[AMD Official Use Only - General]
Hi Oleksandr,
Thank you for your input. I tried matching the hardware parameter (i.e. buffer
size) in the HVM config file, but still no luck with audio from HVM guest.
Here is the complete vsnd config:
vsnd = [[ 'card, backend=Domain-0, buffer-size=22050,
On 05/09/2022 17:30, Rahul Singh wrote:
From: Zhou Wang
Backport Linux commit a76a3f2c. Rename __iomb to iomb() while
merging to get in sync with other Xen definitions.
Reading the 'prod' MMIO register in order to determine whether or
not there is valid data beyond 'cons' for a given
flight 172997 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172997/
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
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: 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:
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 Henry,
On 05/09/2022 08:26, Henry Wang wrote:
This commit introduces the reserved heap memory, which is parts of RAM
reserved in the beginning of the boot time for heap.
Firstly, since a new type of memory bank is needed for marking the
memory bank solely as the heap, this commit defines
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. The question
> > > is whether this is really prohibitively
On Mon, Sep 5, 2022 at 8:06 AM Steven Rostedt wrote:
>
> On Sun, 4 Sep 2022 18:32:58 -0700
> Suren Baghdasaryan wrote:
>
> > Page allocations (overheads are compared to get_free_pages() duration):
> > 6.8% Codetag counter manipulations (__lazy_percpu_counter_add +
> > __alloc_tag_add)
> > 8.8%
On Mon, Sep 5, 2022 at 1:58 AM Marco Elver wrote:
>
> On Mon, 5 Sept 2022 at 10:12, 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,
On 05/09/2022 08:26, Henry Wang wrote:
This commit firstly adds a bool field `reserved_heap` to bootinfo.
This newly introduced field is set at the device tree parsing time
if the reserved heap ranges are defined in the device tree chosen
node.
For Arm32, In `setup_mm`, if the
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
> > + [[ boot-cpupools == \b\o\o\t\-\c\p\u\p\o\o\l\s ]]
> > ++
flight 173004 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173004/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-migrupgrade broken
test-amd64-amd64-migrupgrade 6
flight 173007 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173007/
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 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
> > > roles to support the para virtualization or passthrough mode.
> >
> > I am not sure what you are actually asking. The pending tables are just
> >
On Mon, 5 Sep 2022, Rahul Singh wrote:
> 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
On Mon, 5 Sep 2022, Rahul Singh wrote:
> 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
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, Bertrand Marquis wrote:
> >>> Hi Julien,
> On 5 Sep 2022, at 12:43,
flight 173012 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173012/
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 173009 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173009/
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 Mon, 5 Sep 2022 16:42:29 -0400
Kent Overstreet wrote:
> > Haven't tried that yet but will do. Thanks for the reference code!
>
> Is it really worth the effort of benchmarking tracing API overhead here?
>
> The main cost of a tracing based approach is going to to be the data structure
>
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]
> it adds on top of
> our existing allocator layers complexity but it would need to
Hi Anthony,
> -Original Message-
> From: Anthony PERARD
> Subject: Re: Xen 4.17 release: Current status before the feature freeze
>
> On Mon, Sep 05, 2022 at 03:44:33AM +, Henry Wang wrote:
> > ** Blocker List **:
> > 2. The fix of libvirt after the virtio support in toolstack
> >
flight 173014 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173014/
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
From: Jiangshan Yi
Fix spelling typo in comment.
Reported-by: k2ci
Signed-off-by: Jiangshan Yi
---
drivers/block/xen-blkback/common.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/xen-blkback/common.h
b/drivers/block/xen-blkback/common.h
index
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 version
number with guest and SPMC.
A guest configuration variable "ffa_enabled" is
On Mon, 5 Sep 2022, Julien Grall wrote:
> On 05/09/2022 11:23, Bertrand Marquis wrote:
> > > On 5 Sep 2022, at 10:31, Julien Grall wrote:
> > > On 05/09/2022 10:18, Rahul Singh wrote:
> > > > > On 3 Sep 2022, at 12:21 am, Stefano Stabellini
> > > > > wrote:
> > > > >
> > > > > On Fri, 2 Sep
On Mon, 5 Sep 2022, Henry Wang wrote:
> This commit introduces the reserved heap memory, which is parts of RAM
> reserved in the beginning of the boot time for heap.
>
> Firstly, since a new type of memory bank is needed for marking the
> memory bank solely as the heap, this commit defines `enum
Hi Julien,
> -Original Message-
> From: Julien Grall
> Subject: Re: [PATCH v2 1/4] docs, xen/arm: Introduce reserved heap memory
>
> Hi Henry,
>
> On 05/09/2022 08:26, Henry Wang wrote:
> > This commit introduces the reserved heap memory, which is parts of RAM
> > reserved in the
Hi Julien,
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 region
> with
>
> There
flight 173008 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173008/
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 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 boot, then I would
suggest to use __ro_after_init. This was introduced recently
On Mon, Sep 05, 2022 at 06:16:50PM -0400, Steven Rostedt wrote:
> On Mon, 5 Sep 2022 16:42:29 -0400
> Kent Overstreet wrote:
>
> > > Haven't tried that yet but will do. Thanks for the reference code!
> >
> > Is it really worth the effort of benchmarking tracing API overhead here?
> >
> > The
Hi Stefano,
> -Original Message-
> From: Stefano Stabellini
> Subject: Re: [PATCH v2 1/4] docs, xen/arm: Introduce reserved heap memory
>
> On Mon, 5 Sep 2022, Henry Wang wrote:
> > This commit introduces the reserved heap memory, which is parts of RAM
> > reserved in the beginning of
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
> + [[ boot-cpupools == \b\o\o\t\-\c\p\u\p\o\o\l\s ]]
> ++ fdtget binaries/virt-gicv2.dtb -t x /cpus/cpu@1 phandle
>
On Thu 01-09-22 16:15:02, Kent Overstreet wrote:
> On Thu, Sep 01, 2022 at 12:39:11PM -0700, Suren Baghdasaryan wrote:
> > kmemleak is known to be slow and it's even documented [1], so I hope I
> > can skip that part. For page_owner to provide the comparable
> > information we would have to
On Mon, 5 Sept 2022 at 10:12, 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. The question
> > > is whether this is really prohibitively
Hi Stefano,
> On 3 Sep 2022, at 12:29 am, Stefano Stabellini wrote:
>
> On Fri, 2 Sep 2022, Rahul Singh wrote:
>> From: Jean-Philippe Brucker
>>
>> Backport Linux commit e881e7839fba. This is the clean backport without
>> any changes.
>
> I don't think we can say that this is a clean
Hi Henry,
On 05/09/2022 09:26, Henry Wang wrote:
>
> At the boot time, it is saner to stop booting early if an error occurs
> when parsing the device tree chosen node, rather than seeing random
> behavior afterwards. Therefore, this commit changes the return type of
> the process_chosen_node()
Hi Stefano,
> On 3 Sep 2022, at 12:21 am, Stefano Stabellini wrote:
>
> On Fri, 2 Sep 2022, Rahul Singh wrote:
>> From: Zhou Wang
>>
>> Backport Linux commit a76a3f2c. This is the clean backport without
>> any changes.
>>
>> Reading the 'prod' MMIO register in order to determine whether
On 05/09/2022 10:18, Rahul Singh wrote:
On 3 Sep 2022, at 12:21 am, Stefano Stabellini wrote:
On Fri, 2 Sep 2022, Rahul Singh wrote:
From: Zhou Wang
Backport Linux commit a76a3f2c. This is the clean backport without
any changes.
Reading the 'prod' MMIO register in order to determine
Hi Bertrand,
On 05/09/2022 11:23, Bertrand Marquis wrote:
Hi,
On 5 Sep 2022, at 10:31, Julien Grall wrote:
On 05/09/2022 10:18, Rahul Singh wrote:
On 3 Sep 2022, at 12:21 am, Stefano Stabellini wrote:
On Fri, 2 Sep 2022, Rahul Singh wrote:
From: Zhou Wang
Backport Linux commit
Hi Stefano,
> On 3 Sep 2022, at 12:17 am, Stefano Stabellini wrote:
>
> On Fri, 2 Sep 2022, Rahul Singh wrote:
>> 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
Hi Stefano,
> On 3 Sep 2022, at 12:31 am, Stefano Stabellini wrote:
>
> I checked all the patches against the originals.
>
> I had comments on patches 3,4,5.
>
> You can add:
>
> Acked-by: Stefano Stabellini
>
> to all the others (1,2,6,7,8,9,10).
>
Thanks for reviewing the patches. I
On 05/09/2022 10:16, Michal Orzel wrote:
Hi Henry,
On 05/09/2022 09:26, Henry Wang wrote:
At the boot time, it is saner to stop booting early if an error occurs
when parsing the device tree chosen node, rather than seeing random
behavior afterwards. Therefore, this commit changes the
Hi Julien and Michal,
> -Original Message-
> From: Julien Grall
> >> Changes from v1 to v2:
> >> - New commit.
> >> ---
> >
> > The patch looks good but I think it should be put as the first one in the
> series
> > as this is a natural prerequisite for the introduction of the reserved
flight 172998 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172998/
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,
> On 5 Sep 2022, at 10:31, Julien Grall wrote:
>
>
>
> On 05/09/2022 10:18, Rahul Singh wrote:
>>> On 3 Sep 2022, at 12:21 am, Stefano Stabellini
>>> wrote:
>>>
>>> On Fri, 2 Sep 2022, Rahul Singh wrote:
From: Zhou Wang
Backport Linux commit a76a3f2c. This is the
On 05/09/2022 08:00, Juergen Gross wrote:
> @@ -3312,17 +3325,18 @@ void free_cpu_rm_data(struct cpu_rm_data *mem,
> unsigned int cpu)
> * The cpu is already marked as "free" and not valid any longer for its
> * cpupool.
> */
> -int schedule_cpu_rm(unsigned int cpu)
> +int
On 05.09.22 12:36, Andrew Cooper wrote:
On 05/09/2022 08:00, Juergen Gross wrote:
@@ -3312,17 +3325,18 @@ void free_cpu_rm_data(struct cpu_rm_data *mem, unsigned
int cpu)
* The cpu is already marked as "free" and not valid any longer for its
* cpupool.
*/
-int schedule_cpu_rm(unsigned
Hi Henry,
On 05/09/2022 05:44, Henry Wang wrote:
>
> 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 mailing list. Please add the ones that I probably missed.
>
Hi Michal,
> -Original Message-
> From: Michal Orzel
> > 2. automation: Test a pv network interface under dom0less enhanced
> >
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatc
> hwork.kernel.org%2Fproject%2Fxen-
>
Hi jan
> -Original Message-
> From: Jan Beulich
> Sent: Wednesday, August 17, 2022 6:05 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
This commit firstly adds a bool field `reserved_heap` to bootinfo.
This newly introduced field is set at the device tree parsing time
if the reserved heap ranges are defined in the device tree chosen
node.
For Arm32, In `setup_mm`, if the reserved heap is enabled, we use
the reserved heap region
At the boot time, it is saner to stop booting early if an error occurs
when parsing the device tree chosen node, rather than seeing random
behavior afterwards. Therefore, this commit changes the return type of
the process_chosen_node() from void to int, and return correct errno
based on the error
flight 172995 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172995/
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
For updating the node affinities of all domains in a cpupool add a new
function cpupool_update_node_affinity().
In order to avoid multiple allocations of cpumasks carve out memory
allocation and freeing from domain_update_node_affinity() into new
helpers, which can be used by
Cpu unplugging is calling schedule_cpu_rm() via stop_machine_run() with
interrupts disabled, thus any memory allocation or freeing must be
avoided.
Since commit 5047cd1d5dea ("xen/common: Use enhanced
ASSERT_ALLOC_CONTEXT in xmalloc()") this restriction is being enforced
via an assertion, which
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
operation is done in stop-machine context, this
In order to prepare not allocating or freeing memory from
schedule_cpu_rm(), move this functionality to dedicated functions.
For now call those functions from schedule_cpu_rm().
No change of behavior expected.
Signed-off-by: Juergen Gross
---
V2:
- add const (Jan Beulich)
- use "unsigned int"
The reserved heap, or statically configured heap, refers to parts
of RAM reserved in the beginning for heap. Like the static memory
allocation, such reserved heap regions are reserved by configuration
in the device tree using physical address ranges.
This feature is useful to run Xen on Arm MPU
This commit introduces the reserved heap memory, which is parts of RAM
reserved in the beginning of the boot time for heap.
Firstly, since a new type of memory bank is needed for marking the
memory bank solely as the heap, this commit defines `enum membank_type`
and use this enum in function
With the reserved heap setup, keep using xenheap_* in the function
setup_xenheap_mappings() will make the code confusing to read,
because we always need to map the full RAM on Arm64. Therefore,
renaming all "xenheap_*" variables to "directmap_*" to make clear
the area is used to access the RAM
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. The question
> > is whether this is really prohibitively expensive. How much overhead are
> > we talking about? There is no
flight 172991 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172991/
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 Tue, Aug 30, 2022 at 01:06:11PM +0100, Paul Durrant wrote:
> On 29/08/2022 10:03, Matias Ezequiel Vara Larsen wrote:
> > This commit creates a new doc to document the acquire resource interface.
> > This
> > is a reference document.
> >
> > Signed-off-by: Matias Ezequiel Vara Larsen
> > ---
>
Hi Julien,
> 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, Bertrand Marquis wrote:
>>> Hi Julien,
On 5 Sep 2022, at 12:43, Julien Grall wrote:
On 05/09/2022
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 timeout.
Solve the issue by sending in-band connect marker. Whenever server
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 startup, it can result in error like this:
libxl:
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 modifying the existing ones
(Julien Grall)
---
Add documentation for an extension of the WATCH command used to limit
the scope of watched paths. Additionally it enables to receive more
information in the events related to special watches (@introduceDomain
or @releaseDomain).
Signed-off-by: Juergen Gross
Reviewed-by: Julien Grall
---
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 Gross
---
V3:
- new patch
---
Add documentation for two new Xenstore wire commands SET_QUOTA and
GET_QUOTA used to set or query the global Xenstore quota or those of
a given domain.
Signed-off-by: Juergen Gross
Reviewed-by: Julien Grall
---
V2:
- remove feature bit (Julien Grall)
- add possibility to access global quota and
In the past there have been spotted some shortcomings in the Xenstore
interface, which should be repaired. Those are in detail:
- Using driver domains for large number of domains needs per domain
Xenstore quota [1]. The feedback sent was rather slim (one reply),
but it was preferring a new
Hi Julien,
> On 5 Sep 2022, at 13:08, Julien Grall wrote:
>
>
>
> On 05/09/2022 12:54, Bertrand Marquis wrote:
>> Hi Julien,
>>> On 5 Sep 2022, at 12:43, Julien Grall wrote:
>>>
>>>
>>>
>>> On 05/09/2022 12:12, Rahul Singh wrote:
Hi Julien,
>>>
>>> Hi Rahul,
>>>
> On 2 Sep
flight 173001 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/173001/
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 172993 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172993/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-freebsd10-i386 17 guest-localmigrate fail in 172972 pass in
172993
test-amd64-i386-pair
On 05/09/2022 12:12, Rahul Singh wrote:
Hi Julien,
Hi Rahul,
On 2 Sep 2022, at 5:20 pm, Julien Grall wrote:
On 02/09/2022 16:54, Rahul Singh wrote:
Hi Julien,
Hi Rahul,
On 2 Sep 2022, at 4:05 pm, Julien Grall wrote:
Hi Bertrand,
On 02/09/2022 15:51, Bertrand Marquis wrote:
Hi Julien,
> On 5 Sep 2022, at 12:43, Julien Grall wrote:
>
>
>
> On 05/09/2022 12:12, Rahul Singh wrote:
>> Hi Julien,
>
> Hi Rahul,
>
>>> On 2 Sep 2022, at 5:20 pm, Julien Grall wrote:
>>>
>>>
>>>
>>> On 02/09/2022 16:54, Rahul Singh wrote:
Hi Julien,
>>>
>>> Hi Rahul,
>>>
Hi Henry,
On 05/09/2022 09:26, Henry Wang wrote:
>
> diff --git a/xen/arch/arm/include/asm/setup.h
> b/xen/arch/arm/include/asm/setup.h
> index 5815ccf8c5..d0cc556833 100644
> --- a/xen/arch/arm/include/asm/setup.h
> +++ b/xen/arch/arm/include/asm/setup.h
> @@ -22,11 +22,16 @@ typedef enum {
>
On 05/09/2022 12:54, Bertrand Marquis wrote:
Hi Julien,
On 5 Sep 2022, at 12:43, Julien Grall wrote:
On 05/09/2022 12:12, Rahul Singh wrote:
Hi Julien,
Hi Rahul,
On 2 Sep 2022, at 5:20 pm, Julien Grall wrote:
On 02/09/2022 16:54, Rahul Singh wrote:
Hi Julien,
Hi Rahul,
On
1 - 100 of 107 matches
Mail list logo
