From: Andi Kleen <andi@firstfloor.org>
To: Chris Wright <chrisw@sous-sol.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] allow fallback to swiotlb on hw iommu init failures
Date: Mon, 26 Oct 2009 08:10:31 +0100 [thread overview]
Message-ID: <87hbtmy6jc.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20091023012158.177308035@sequoia.sous-sol.org> (Chris Wright's message of "Thu, 22 Oct 2009 18:21:58 -0700")
Chris Wright <chrisw@sous-sol.org> writes:
> This short series gives us the ability to allocate the swiotlb and then
> conditionally free it if we discover it isn't needed. This allows us to
> put swiotlb to use when the hw iommu fails to initialize properly.
>
> This needs some changes to the bootmem allocator to give the ability to
> free reserved bootmem directly to the page allocator after bootmem is
> torn down.
You forgot to state what motivated you to that change?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-10-26 7:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 1:21 [RFC PATCH 0/3] allow fallback to swiotlb on hw iommu init failures Chris Wright
2009-10-23 1:21 ` [RFC PATCH 1/3] [RFC PATCH] bootmem: refactor free_all_bootmem_core Chris Wright
2009-10-23 1:22 ` [RFC PATCH 2/3] [RFC PATCH] bootmem: add free_bootmem_late Chris Wright
2009-10-23 1:22 ` [RFC PATCH 3/3] [RFC PATCH] iommu: allow fallback to swiotlb upon hw iommu initialization failure Chris Wright
2009-10-23 5:51 ` [RFC PATCH 0/3] allow fallback to swiotlb on hw iommu init failures FUJITA Tomonori
2009-10-23 16:39 ` Chris Wright
2009-10-24 3:06 ` FUJITA Tomonori
2009-10-24 6:57 ` Chris Wright
2009-10-28 6:53 ` FUJITA Tomonori
2009-10-26 7:10 ` Andi Kleen [this message]
2009-10-26 16:26 ` Chris Wright
2009-10-26 21:56 ` Andi Kleen
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=87hbtmy6jc.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=chrisw@sous-sol.org \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.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.