From: Christoph Hellwig <hch@infradead.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Julien.Grall@arm.com, xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [PATCH v2] xen/swiotlb: don't initialize swiotlb twice on arm64
Date: Mon, 17 Jun 2019 01:21:08 -0700 [thread overview]
Message-ID: <20190617082108.GB11274@infradead.org> (raw)
In-Reply-To: <20190613210057.GE11920@char.us.oracle.com>
On Thu, Jun 13, 2019 at 05:00:57PM -0400, Konrad Rzeszutek Wilk wrote:
> > As Christoph didn't react when I posted possible solutions I think I'll
> > just modify patch 3 according to Jan's comment and post V3.
>
> OK, will await that patchset. Thank you!
>
> BTW, your patch #1 should be upstream now.
Still not a big fan of the page flags in the common header, but please
go ahead for now if the mm folks are fine with it.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-06-17 8:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 22:48 [PATCH v2] xen/swiotlb: don't initialize swiotlb twice on arm64 Stefano Stabellini
2019-05-28 22:48 ` [Xen-devel] " Stefano Stabellini
2019-05-28 23:50 ` Boris Ostrovsky
2019-05-28 23:50 ` [Xen-devel] " Boris Ostrovsky
2019-06-03 18:25 ` Stefano Stabellini
2019-06-03 18:25 ` [Xen-devel] " Stefano Stabellini
2019-06-03 23:16 ` Boris Ostrovsky
2019-06-03 23:16 ` [Xen-devel] " Boris Ostrovsky
2019-06-04 16:51 ` Stefano Stabellini
2019-06-04 19:41 ` Boris Ostrovsky
2019-06-05 14:13 ` Konrad Rzeszutek Wilk
2019-06-05 14:24 ` Juergen Gross
2019-06-13 14:23 ` Konrad Rzeszutek Wilk
2019-06-13 15:04 ` Juergen Gross
2019-06-13 21:00 ` Konrad Rzeszutek Wilk
2019-06-17 8:21 ` Christoph Hellwig [this message]
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=20190617082108.GB11274@infradead.org \
--to=hch@infradead.org \
--cc=Julien.Grall@arm.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).