Linux IOMMU Development
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	xen-devel <xen-devel@lists.xenproject.org>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [PATCH v2 3/3] xen/swiotlb: remember having called xen_create_contiguous_region()
Date: Wed, 29 May 2019 12:21:41 +0200	[thread overview]
Message-ID: <55b35087-064d-8188-2373-0dd94ffef2b6@suse.com> (raw)
In-Reply-To: <5CEE57910200007800233571@prv1-mh.provo.novell.com>

On 29/05/2019 11:57, Jan Beulich wrote:
>>>> On 29.05.19 at 11:04, <jgross@suse.com> wrote:
>> @@ -345,8 +346,11 @@ xen_swiotlb_free_coherent(struct device *hwdev, size_t size, void *vaddr,
>>  	size = 1UL << (order + XEN_PAGE_SHIFT);
>>  
>>  	if (!WARN_ON((dev_addr + size - 1 > dma_mask) ||
>> -		     range_straddles_page_boundary(phys, size)))
>> +		     range_straddles_page_boundary(phys, size)) &&
>> +	    PageXenRemapped(virt_to_page(vaddr))) {
>>  		xen_destroy_contiguous_region(phys, order);
>> +		ClearPageXenRemapped(virt_to_page(vaddr));
>> +	}
> 
> To be symmetric with setting the flag only after having made the region
> contiguous, and to avoid (perhaps just theoretical) races, wouldn't it be
> better to clear the flag before calling xen_destroy_contiguous_region()?
> Even better would be a TestAndClear...() operation.

I like that idea.


Juergen
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

  reply	other threads:[~2019-05-29 10:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-29  9:04 [PATCH v2 0/3] xen/swiotlb: fix an issue and improve swiotlb-xen Juergen Gross
2019-05-29  9:04 ` [PATCH v2 1/3] xen/swiotlb: fix condition for calling xen_destroy_contiguous_region() Juergen Gross
2019-05-29  9:52   ` [Xen-devel] " Jan Beulich
2019-05-29  9:04 ` [PATCH v2 2/3] xen/swiotlb: simplify range_straddles_page_boundary() Juergen Gross
2019-05-29  9:04 ` [PATCH v2 3/3] xen/swiotlb: remember having called xen_create_contiguous_region() Juergen Gross
2019-05-29  9:57   ` [Xen-devel] " Jan Beulich
2019-05-29 10:21     ` Juergen Gross [this message]
2019-05-30  9:04   ` Christoph Hellwig
2019-05-30 12:46     ` Boris Ostrovsky
2019-05-31 11:38       ` Juergen Gross
2019-06-05  8:37         ` Juergen Gross

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=55b35087-064d-8188-2373-0dd94ffef2b6@suse.com \
    --to=jgross@suse.com \
    --cc=JBeulich@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox