From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Jan Beulich <jbeulich@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Michal Orzel <michal.orzel@amd.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Anthony PERARD <anthony.perard@vates.tech>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 0/2] xen/mm: limit in-place scrubbing
Date: Fri, 9 Jan 2026 13:31:14 +0100 [thread overview]
Message-ID: <aWD1EhFl0nGsBp2G@Mac.lan> (raw)
In-Reply-To: <b6befa76-c80c-43d1-bda3-e60e1217fa80@citrix.com>
On Fri, Jan 09, 2026 at 10:29:20AM +0000, Andrew Cooper wrote:
> On 09/01/2026 10:15 am, Jan Beulich wrote:
> > On 08.01.2026 18:55, Roger Pau Monne wrote:
> >> In XenServer we have seen the watchdog occasionally triggering during
> >> domain creation if 1GB pages are scrubbed in-place during physmap
> >> population.
> > That's pretty extreme - writing to 1Gb of memory can't really take over 5s,
> > can it?
>
> Sure it can.
>
> > Is there lock contention involved?
>
> Almost certainly, and it's probably the more relevant aspect in this case.
Possibly. I can tell Edwin to give me his reproduction. There's also
the map_domain_page() page aspect of this operation. On big enough
systems this will cause a fair amount of stress to the map cache,
since each page is mapped, scrubbed and unmapped. I don't think
however the systems on which we have seen this to be using the map
cache (it was on debug=n builds with less than 5TB of memory).
> > Or is this when very many CPUs
> > try to do the same in parallel?
>
> The scenario is reboot of a VM when Xapi is doing NUMA placement using
> per-node claims.
Not exclusively. We have reports of this also happening without any
claims or NUMA placements being used.
AFAICT it's possibly triggered when doing reboots of multiple VMs in
parallel, and all reports of it I've seen it's on multi-node NUMA
systems. I wonder if scrubbing a 1G remote page in 4K chunks is
killing the intra-node bandwidth.
Thanks, Roger.
prev parent reply other threads:[~2026-01-09 12:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 17:55 [PATCH 0/2] xen/mm: limit in-place scrubbing Roger Pau Monne
2026-01-08 17:55 ` [PATCH 1/2] xen/mm: add a NUMA node parameter to scrub_free_pages() Roger Pau Monne
2026-01-09 10:22 ` Jan Beulich
2026-01-09 14:46 ` Roger Pau Monné
2026-01-09 14:50 ` Jan Beulich
2026-01-08 17:55 ` [PATCH 2/2] xen/mm: limit non-scrubbed allocations to a specific order Roger Pau Monne
2026-01-09 11:19 ` Jan Beulich
2026-01-13 14:01 ` Roger Pau Monné
2026-01-14 8:48 ` Jan Beulich
2026-01-15 10:48 ` Roger Pau Monné
2026-01-15 10:56 ` Jan Beulich
2026-01-15 13:05 ` Roger Pau Monné
2026-01-09 10:15 ` [PATCH 0/2] xen/mm: limit in-place scrubbing Jan Beulich
2026-01-09 10:29 ` Andrew Cooper
2026-01-09 11:32 ` Jan Beulich
2026-01-09 11:34 ` Andrew Cooper
2026-01-09 12:31 ` Roger Pau Monné [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aWD1EhFl0nGsBp2G@Mac.lan \
--to=roger.pau@citrix.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=bertrand.marquis@arm.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.