From: "Jürgen Groß" <jgross@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
iommu@lists.linux.dev,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
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>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 2/2] xen/swiotlb: don't destroy contiguous region in all cases
Date: Wed, 12 Feb 2025 12:15:07 +0100 [thread overview]
Message-ID: <b7bc43f9-47e6-4994-bba9-5c8be92a8e52@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2502111728560.619090@ubuntu-linux-20-04-desktop>
[-- Attachment #1.1.1: Type: text/plain, Size: 6262 bytes --]
On 12.02.25 02:30, Stefano Stabellini wrote:
> On Tue, 11 Feb 2025, Juergen Gross wrote:
>> In case xen_swiotlb_alloc_coherent() needed to create a contiguous
>> region only for other reason than the memory not being compliant with
>> the device's DMA mask, there is no reason why this contiguous region
>> should be destroyed by xen_swiotlb_free_coherent() later. Destroying
>> this region should be done only, if the memory of the region was
>> allocated with more stringent placement requirements than the memory
>> it did replace.
>>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> ---
>> arch/x86/include/asm/xen/swiotlb-xen.h | 5 +++--
>> arch/x86/xen/mmu_pv.c | 18 ++++++++++++------
>> drivers/xen/swiotlb-xen.c | 11 +++++++----
>> 3 files changed, 22 insertions(+), 12 deletions(-)
>>
>> diff --git a/arch/x86/include/asm/xen/swiotlb-xen.h b/arch/x86/include/asm/xen/swiotlb-xen.h
>> index abde0f44df57..a353f20c7e79 100644
>> --- a/arch/x86/include/asm/xen/swiotlb-xen.h
>> +++ b/arch/x86/include/asm/xen/swiotlb-xen.h
>> @@ -4,8 +4,9 @@
>>
>> int xen_swiotlb_fixup(void *buf, unsigned long nslabs);
>> int xen_create_contiguous_region(phys_addr_t pstart, unsigned int order,
>> - unsigned int address_bits,
>> - dma_addr_t *dma_handle);
>> + unsigned int address_bits,
>> + dma_addr_t *dma_handle,
>> + unsigned int *address_bits_in);
>> void xen_destroy_contiguous_region(phys_addr_t pstart, unsigned int order);
>>
>> #endif /* _ASM_X86_SWIOTLB_XEN_H */
>> diff --git a/arch/x86/xen/mmu_pv.c b/arch/x86/xen/mmu_pv.c
>> index 2c70cd35e72c..fb586238f7c4 100644
>> --- a/arch/x86/xen/mmu_pv.c
>> +++ b/arch/x86/xen/mmu_pv.c
>> @@ -2208,19 +2208,22 @@ void __init xen_init_mmu_ops(void)
>> static unsigned long discontig_frames[1<<MAX_CONTIG_ORDER];
>>
>> #define VOID_PTE (mfn_pte(0, __pgprot(0)))
>> -static void xen_zap_pfn_range(unsigned long vaddr, unsigned int order,
>> - unsigned long *in_frames,
>> - unsigned long *out_frames)
>> +static int xen_zap_pfn_range(unsigned long vaddr, unsigned int order,
>> + unsigned long *in_frames,
>> + unsigned long *out_frames)
>> {
>> int i;
>> + u64 address_bits = 0;
>> struct multicall_space mcs;
>>
>> xen_mc_batch();
>> for (i = 0; i < (1UL<<order); i++, vaddr += PAGE_SIZE) {
>> mcs = __xen_mc_entry(0);
>>
>> - if (in_frames)
>> + if (in_frames) {
>> in_frames[i] = virt_to_mfn((void *)vaddr);
>> + address_bits |= in_frames[i] << PAGE_SHIFT;
>> + }
>>
>> MULTI_update_va_mapping(mcs.mc, vaddr, VOID_PTE, 0);
>> __set_phys_to_machine(virt_to_pfn((void *)vaddr), INVALID_P2M_ENTRY);
>> @@ -2229,6 +2232,8 @@ static void xen_zap_pfn_range(unsigned long vaddr, unsigned int order,
>> out_frames[i] = virt_to_pfn((void *)vaddr);
>> }
>> xen_mc_issue(0);
>> +
>> + return fls64(address_bits);
>> }
>>
>> /*
>> @@ -2321,7 +2326,8 @@ static int xen_exchange_memory(unsigned long extents_in, unsigned int order_in,
>>
>> int xen_create_contiguous_region(phys_addr_t pstart, unsigned int order,
>> unsigned int address_bits,
>> - dma_addr_t *dma_handle)
>> + dma_addr_t *dma_handle,
>> + unsigned int *address_bits_in)
>> {
>> unsigned long *in_frames = discontig_frames, out_frame;
>> unsigned long flags;
>> @@ -2336,7 +2342,7 @@ int xen_create_contiguous_region(phys_addr_t pstart, unsigned int order,
>> spin_lock_irqsave(&xen_reservation_lock, flags);
>>
>> /* 1. Zap current PTEs, remembering MFNs. */
>> - xen_zap_pfn_range(vstart, order, in_frames, NULL);
>> + *address_bits_in = xen_zap_pfn_range(vstart, order, in_frames, NULL);
>>
>> /* 2. Get a new contiguous memory extent. */
>> out_frame = virt_to_pfn((void *)vstart);
>> diff --git a/drivers/xen/swiotlb-xen.c b/drivers/xen/swiotlb-xen.c
>> index 26c62e0d34e9..3f3724f53914 100644
>> --- a/drivers/xen/swiotlb-xen.c
>> +++ b/drivers/xen/swiotlb-xen.c
>> @@ -118,6 +118,7 @@ int xen_swiotlb_fixup(void *buf, unsigned long nslabs)
>> int rc;
>> unsigned int order = get_order(IO_TLB_SEGSIZE << IO_TLB_SHIFT);
>> unsigned int i, dma_bits = order + PAGE_SHIFT;
>> + unsigned int dummy;
>> dma_addr_t dma_handle;
>> phys_addr_t p = virt_to_phys(buf);
>>
>> @@ -129,7 +130,7 @@ int xen_swiotlb_fixup(void *buf, unsigned long nslabs)
>> do {
>> rc = xen_create_contiguous_region(
>> p + (i << IO_TLB_SHIFT), order,
>> - dma_bits, &dma_handle);
>> + dma_bits, &dma_handle, &dummy);
>> } while (rc && dma_bits++ < MAX_DMA_BITS);
>> if (rc)
>> return rc;
>> @@ -144,6 +145,7 @@ xen_swiotlb_alloc_coherent(struct device *dev, size_t size,
>> dma_addr_t *dma_handle, gfp_t flags, unsigned long attrs)
>> {
>> u64 dma_mask = dev->coherent_dma_mask;
>> + unsigned int address_bits = fls64(dma_mask), address_bits_in;
>> int order = get_order(size);
>> phys_addr_t phys;
>> void *ret;
>> @@ -160,10 +162,11 @@ xen_swiotlb_alloc_coherent(struct device *dev, size_t size,
>> if (*dma_handle + size - 1 > dma_mask ||
>> range_straddles_page_boundary(phys, size) ||
>> range_requires_alignment(phys, size)) {
>> - if (xen_create_contiguous_region(phys, order, fls64(dma_mask),
>> - dma_handle) != 0)
>> + if (xen_create_contiguous_region(phys, order, address_bits,
>> + dma_handle, &address_bits_in))
>> goto out_free_pages;
>> - SetPageXenRemapped(virt_to_page(ret));
>> + if (address_bits_in > address_bits)
>> + SetPageXenRemapped(virt_to_page(ret));
>
> This has the unfortunate side effect of making "PageXenRemapped"
> unreliable as an indicator of whether a page has been remapped. A page
> could still be remapped without the "PageXenRemapped" bit being set.
>
> I recommend adding an in-code comment to clarify this behavior.
The PageXenRemapped bit is used only for determining whether
xen_destroy_contiguous_region() should be called. And by not setting the bit
I'm avoiding to call xen_destroy_contiguous_region() later. So I don't see any
unfortunate side effect.
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2025-02-12 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 12:04 [PATCH 0/2] xen/swiotlb: one fix and one optimization Juergen Gross
2025-02-11 12:04 ` [PATCH 1/2] xen/swiotlb: relax alignment requirements Juergen Gross
2025-02-12 1:23 ` Stefano Stabellini
2025-02-12 6:53 ` Jan Beulich
2025-02-12 11:04 ` Jürgen Groß
2025-02-11 12:04 ` [PATCH 2/2] xen/swiotlb: don't destroy contiguous region in all cases Juergen Gross
2025-02-12 1:30 ` Stefano Stabellini
2025-02-12 11:15 ` Jürgen Groß [this message]
2025-02-12 21:14 ` Stefano Stabellini
2025-02-12 7:38 ` Jan Beulich
2025-02-12 11:11 ` Jürgen Groß
2025-02-12 11:49 ` Jan Beulich
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=b7bc43f9-47e6-4994-bba9-5c8be92a8e52@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®