All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Juergen Gross <jgross@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@lists.xenproject.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v2 3/3] xen/swiotlb: remember having called xen_create_contiguous_region()
Date: Thu, 30 May 2019 02:04:09 -0700	[thread overview]
Message-ID: <20190530090409.GB30428__3986.34224418259$1559207127$gmane$org@infradead.org> (raw)
In-Reply-To: <20190529090407.1225-4-jgross@suse.com>

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.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2019-05-30  9:04 UTC|newest]

Thread overview: 42+ 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 ` [Xen-devel] " Juergen Gross
2019-05-29  9:04 ` 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:04   ` [Xen-devel] " Juergen Gross
2019-05-29  9:04   ` Juergen Gross
2019-05-29  9:52   ` Jan Beulich
2019-05-29  9:52   ` [Xen-devel] " Jan Beulich
2019-05-29  9:52     ` Jan Beulich
2019-05-29  9:52     ` Jan Beulich
2019-05-29  9:04 ` Juergen Gross
2019-05-29  9:04 ` [PATCH v2 2/3] xen/swiotlb: simplify range_straddles_page_boundary() Juergen Gross
2019-05-29  9:04 ` Juergen Gross
2019-05-29  9:04   ` [Xen-devel] " Juergen Gross
2019-05-29  9:04   ` 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:04 ` Juergen Gross
2019-05-29  9:04   ` [Xen-devel] " Juergen Gross
2019-05-29  9:04   ` Juergen Gross
2019-05-29  9:57   ` [Xen-devel] " Jan Beulich
2019-05-29  9:57     ` Jan Beulich
2019-05-29  9:57     ` Jan Beulich
2019-05-29 10:21     ` Juergen Gross
2019-05-29 10:21     ` [Xen-devel] " Juergen Gross
2019-05-29 10:21       ` Juergen Gross
2019-05-29 10:21       ` Juergen Gross
2019-05-29  9:57   ` Jan Beulich
2019-05-30  9:04   ` Christoph Hellwig [this message]
2019-05-30  9:04   ` Christoph Hellwig
2019-05-30  9:04     ` [Xen-devel] " Christoph Hellwig
2019-05-30  9:04     ` Christoph Hellwig
2019-05-30 12:46     ` Boris Ostrovsky
2019-05-30 12:46       ` [Xen-devel] " Boris Ostrovsky
2019-05-30 12:46       ` Boris Ostrovsky
2019-05-31 11:38       ` Juergen Gross
2019-05-31 11:38         ` [Xen-devel] " Juergen Gross
2019-05-31 11:38         ` Juergen Gross
2019-06-05  8:37         ` Juergen Gross
2019-06-05  8:37           ` [Xen-devel] " Juergen Gross
2019-06-05  8:37           ` Juergen Gross
2019-05-31 11:38       ` Juergen Gross
2019-05-30 12:46     ` Boris Ostrovsky

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='20190530090409.GB30428__3986.34224418259$1559207127$gmane$org@infradead.org' \
    --to=hch@infradead.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jgross@suse.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.