From: Juergen Gross <jgross@suse.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Christoph Hellwig <hch@infradead.org>
Cc: xen-devel@lists.xenproject.org, iommu@lists.linux-foundation.org,
Stefano Stabellini <sstabellini@kernel.org>,
linux-kernel@vger.kernel.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH v2 3/3] xen/swiotlb: remember having called xen_create_contiguous_region()
Date: Fri, 31 May 2019 13:38:11 +0200 [thread overview]
Message-ID: <2fbfc6a7-572c-1ce2-3323-802f9a77500e@suse.com> (raw)
In-Reply-To: <eebb0275-9418-717f-97d7-5e55917f46fd@oracle.com>
On 30/05/2019 14:46, Boris Ostrovsky wrote:
> On 5/30/19 5:04 AM, Christoph Hellwig wrote:
>> Please don't add your private flag to page-flags.h. The whole point of
>> the private flag is that you can use it in any way you want withou
>> touching the common code.
>
>
> There is already a bunch of aliases for various sub-components
> (including Xen) in page-flags.h for private flags, which is why I
> suggested we do the same for the new use case. Adding this new alias
> will keep flag usage consistent.
What about me adding another patch moving those Xen private aliases
into arch/x86/include/asm/xen/page.h ?
Juergen
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2019-05-31 11:38 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
2019-05-30 9:04 ` Christoph Hellwig
2019-05-30 12:46 ` Boris Ostrovsky
2019-05-31 11:38 ` Juergen Gross [this message]
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=2fbfc6a7-572c-1ce2-3323-802f9a77500e@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hch@infradead.org \
--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