Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: "Teddy Astie" <teddy.astie@vates.tech>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: xen-devel@lists.xenproject.org, stable@vger.kernel.org,
	"Juergen Gross" <jgross@suse.com>,
	"kernel test robot" <lkp@intel.com>,
	"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Anthoine Bourgeois" <anthoine.bourgeois@vates.tech>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Borislav Petkov" <bp@alien8.de>,
	"Dave Hansen" <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Jiri Slaby" <jirislaby@kernel.org>
Subject: Re: [PATCH v5.10.y] xen: replace xen_remap() with memremap()
Date: Tue, 02 Sep 2025 16:24:33 +0000	[thread overview]
Message-ID: <d4d5ce1f-8bcf-46c3-a1a5-f509375e80e9@vates.tech> (raw)
In-Reply-To: <2025090203-clothes-bullish-a21f@gregkh>

Le 02/09/2025 à 13:18, Greg Kroah-Hartman a écrit :
> On Tue, Sep 02, 2025 at 09:28:32AM +0000, Teddy Astie wrote:
>> From: Juergen Gross <jgross@suse.com>
>>
>> From: Juergen Gross <jgross@suse.com>
>>
>> [ upstream commit 41925b105e345ebc84cedb64f59d20cb14a62613 ]
>>
>> xen_remap() is used to establish mappings for frames not under direct
>> control of the kernel: for Xenstore and console ring pages, and for
>> grant pages of non-PV guests.
>>
>> Today xen_remap() is defined to use ioremap() on x86 (doing uncached
>> mappings), and ioremap_cache() on Arm (doing cached mappings).
>>
>> Uncached mappings for those use cases are bad for performance, so they
>> should be avoided if possible. As all use cases of xen_remap() don't
>> require uncached mappings (the mapped area is always physical RAM),
>> a mapping using the standard WB cache mode is fine.
>>
>> As sparse is flagging some of the xen_remap() use cases to be not
>> appropriate for iomem(), as the result is not annotated with the
>> __iomem modifier, eliminate xen_remap() completely and replace all
>> use cases with memremap() specifying the MEMREMAP_WB caching mode.
>>
>> xen_unmap() can be replaced with memunmap().
>>
>> Reported-by: kernel test robot <lkp@intel.com>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>> Acked-by: Stefano Stabellini <sstabellini@kernel.org>
>> Link: https://lore.kernel.org/r/20220530082634.6339-1-jgross@suse.com
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> Signed-off-by: Teddy Astie <teddy.astie@vates.tech> [backport to 5.10.y]
>> ---
>
> Why is this needed for 5.10.y at all?  What bug does it fix?  And why
> are you still using Xen on a 5.10.y kernel?  What prevents you from
> moving to a newer one?
>

This patch is only useful for virtual machines (DomU) that runs this
Linux version (a notable Linux distribution with this kernel branch is
Debian 11); it's not useful for Dom0 kernels.

On AMD platforms (and future Intel ones with TME); this patch along with
[1] makes the caching attribute for access as WB instead of falling back
to UC due to ioremap (within xen_remap) being used improving the
performance as explained in the commit.

[1] x86/hvmloader: select xen platform pci MMIO BAR UC or WB MTRR cache
attribute
https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=22650d6054625be10172fe0c78b9cadd1a39bd63

> thanks,
>
> greg k-h
>

Teddy


--
Teddy Astie | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech



  reply	other threads:[~2025-09-02 16:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02  9:28 [PATCH v5.10.y] xen: replace xen_remap() with memremap() Teddy Astie
2025-09-02 11:16 ` Greg Kroah-Hartman
2025-09-02 16:24   ` Teddy Astie [this message]
2025-09-03  5:34     ` Greg Kroah-Hartman

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=d4d5ce1f-8bcf-46c3-a1a5-f509375e80e9@vates.tech \
    --to=teddy.astie@vates.tech \
    --cc=anthoine.bourgeois@vates.tech \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=jirislaby@kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@redhat.com \
    --cc=sstabellini@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox