On Tue, 2024-02-06 at 10:24 +0100, Jan Beulich wrote:
> On 05.02.2024 20:23, Oleksii Kurochko wrote:
> > Hello everyone,
> > 
> > I would like to share with you a list for status tracking based on
> > Xen ML:
> > 
> > Arm:
> >   * [PATCH v5 00/13] Arm cache coloring [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> >   * [PATCH v1 repost 0/4] xen/arm64: Rework the MMU-off code
> > (idmap)
> > so it is self-contained [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> >   * [PATCH v13 00/14] PCI devices passthrough on Arm, part 3 [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> > 
> > PPC:
> >   *  [PATCH v2 0/7] Early Boot Allocation on Power [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> > 
> > RISC-V:
> >   *  [PATCH v4 00/30]  Enable build of full Xen for RISC-V [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> > 
> > x86:
> >   * [PATCH 0/4] iommu/x86: fixes/improvements for unity range
> > checks [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> >   * [PATCH 0/8] x86: support AVX10.1 [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> >   * [PATCH v13 00/35] x86: enable FRED for x86-64 [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> 
> This is a kernel series. I don't expect FRED support is in scope for
> 4.19.
Thanks, overlooked that. I will drop it in the next status tracking
mail.

> 
> >   * [PATCH v4 0/8] x86emul: misc additions
> > https://lore.kernel.org/xen-devel/[email protected]/
> >   * [PATCH 0/7] VT-d: SATC handling and ATS tidying [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> >   * [XEN PATCH 0/9] x86: parallelize AP bring-up during boot [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> >   * [PATCH v2 00/12] x86: memcpy() / memset() (non-)ERMS flavors
> > plus
> > fallout [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> > 
> > common:
> >   * annotate entry points with type and size" series [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> 
> The bulk of this has gone in, but there'll want to be follow-ups.
> 
> >   * [PATCH v2 0/8] limit passing around of cpu_user_regs [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> >   * [PATCH v2 (resend) 00/27] Remove the directmap [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> >   * [PATCH v4 00/32] tools: enable xenstore-stubdom to use 9pfs [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> >   * [PATCH v7 0/7] Introduce generic headers [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> >   * [PATCH] move __read_mostly to xen/cache.h
> > [
> > https://lore.kernel.org/xen-devel/[email protected]
> > /]
> >   * [PATCH v2] NUMA: no need for asm/numa.h when !NUMA [
> > https://lore.kernel.org/xen-devel/[email protected]/
> > ]
> 
> This went in already.
I just pulled staging today, so missed that it was merged.

> 
> >   * [XEN PATCH v2 1/3] xen: introduce STATIC_ASSERT_UNREACHABLE() [
> > https://lore.kernel.org/xen-devel/42fc6ae8d3eb802429d29c774502ff232340dc84.1706259490.git.federico.seraf...@bugseng.com/
> > ]
> >   * [PATCH] xen: move BUG_ON(), WARN_ON(), ASSERT(),
> > ASSERT_UNREACHABLE() to xen/bug.h [
> > https://lore.kernel.org/xen-devel/4887b2d91a4bf2e8b4b66f03964259651981403b.1706897023.git.oleksii.kuroc...@gmail.com/
> > ]
> >   * [PATCH] xen/lib: introduce generic find next bit operations [
> > https://lore.kernel.org/xen-devel/52730e6314210ba4164a9934a720c4fda201447b.1706266854.git.oleksii.kuroc...@gmail.com/
> > ]
> > 
> > Please reply with items you would like to see in 4.19 so that
> > people
> > know what is happening and prioritize accordingly.
> 
> Beyond (on x86) AVX10 I'd like to see whether we can also make some
> progress towards supporting APX. That'll be quite a bit of work,
> though,
> including quite a bit of reviews that are likely to end up on the
> backburner (as has been commonly happening for, especially, more
> involved emulator changes).
> 
> Jan


Reply via email to