From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
konrad.wilk@oracle.com, jgross@suse.com
Cc: xen-devel@lists.xenproject.org, Julien.Grall@arm.com
Subject: Re: [PATCH v2] xen/swiotlb: don't initialize swiotlb twice on arm64
Date: Tue, 28 May 2019 19:50:02 -0400 [thread overview]
Message-ID: <4cfc2555-8933-b036-7068-470c388a665f@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1905281546410.16734@sstabellini-ThinkPad-T480s>
On 5/28/19 6:48 PM, Stefano Stabellini wrote:
> From: Stefano Stabellini <stefanos@xilinx.com>
>
> On arm64 swiotlb is often (not always) already initialized by mem_init.
> We don't want to initialize it twice, which would trigger a second
> memory allocation. Moreover, the second memory pool is typically made of
> high pages and ends up replacing the original memory pool of low pages.
> As a side effect of this change, it is possible to have low pages in
> swiotlb-xen on arm64.
>
> Signed-off-by: Stefano Stabellini <stefanos@xilinx.com>
Has this been tested on x86?
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
WARNING: multiple messages have this Message-ID (diff)
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
konrad.wilk@oracle.com, jgross@suse.com
Cc: xen-devel@lists.xenproject.org, Julien.Grall@arm.com
Subject: Re: [Xen-devel] [PATCH v2] xen/swiotlb: don't initialize swiotlb twice on arm64
Date: Tue, 28 May 2019 19:50:02 -0400 [thread overview]
Message-ID: <4cfc2555-8933-b036-7068-470c388a665f@oracle.com> (raw)
Message-ID: <20190528235002.XBlAr0sNC3aaHm2mI9Jkh7oaIGJ9l4YAjWKsWIAJQEE@z> (raw)
In-Reply-To: <alpine.DEB.2.21.1905281546410.16734@sstabellini-ThinkPad-T480s>
On 5/28/19 6:48 PM, Stefano Stabellini wrote:
> From: Stefano Stabellini <stefanos@xilinx.com>
>
> On arm64 swiotlb is often (not always) already initialized by mem_init.
> We don't want to initialize it twice, which would trigger a second
> memory allocation. Moreover, the second memory pool is typically made of
> high pages and ends up replacing the original memory pool of low pages.
> As a side effect of this change, it is possible to have low pages in
> swiotlb-xen on arm64.
>
> Signed-off-by: Stefano Stabellini <stefanos@xilinx.com>
Has this been tested on x86?
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-05-28 23:51 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 [this message]
2019-05-28 23:50 ` 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
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=4cfc2555-8933-b036-7068-470c388a665f@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=Julien.Grall@arm.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).