From: Jon Mason <jdmason@us.ibm.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Muli Ben-Yehuda <muli@il.ibm.com>,
linux-kernel@vger.kernel.org, ak@suse.de,
linux-ia64@vger.kernel.org, mulix@mulix.org
Subject: Re: [PATCH 2/3] swiotlb: create __alloc_bootmem_low_nopanic and add support in SWIOTLB
Date: Tue, 9 May 2006 16:26:03 -0500 [thread overview]
Message-ID: <20060509212602.GD22385@us.ibm.com> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F0670403C@scsmsx401.amr.corp.intel.com>
On Tue, May 09, 2006 at 02:04:08PM -0700, Luck, Tony wrote:
> > I "fixed" it with the hack below. Please let me know if this is not
> > palatable for you.
>
> Not really. The only use of platform_dma_init() that I can see is in
> arch/ia64/mm/init.c:mem_init() ...
>
> platform_dma_init();
>
> so "void" looks to be the right return value. Why did it get changed to
> be "int" (here's where I admit that I've only looked superficially at your
> patch).
Ah, then I better describe it. The patch makes it possible to recover
from an insufficient amount of bootmem during swiotlb_init (instead of
panicing). For x86_64, I have it bailing out (via the returned int from
swiotlb_init and using the non-iommu DMA routines from
arch/x86_64/kernel/pci-nommu.c). For ia64, its not that simple.
There are no alternative DMA routines to switch to incase of an error.
Also, There is no way to "bail-out" from its mem_init. I could add a
panic there, if that is more palatable.
Thanks,
Jon
>
> -Tony
next prev parent reply other threads:[~2006-05-09 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 21:04 [PATCH 2/3] swiotlb: create __alloc_bootmem_low_nopanic and add support in SWIOTLB Luck, Tony
2006-05-09 21:26 ` Jon Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-09 22:08 Luck, Tony
2006-05-08 23:28 Luck, Tony
2006-05-09 20:29 ` Jon Mason
2006-05-04 20:59 Jon Mason
2006-05-07 8:50 ` Muli Ben-Yehuda
2006-05-08 4:58 ` Jon Mason
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=20060509212602.GD22385@us.ibm.com \
--to=jdmason@us.ibm.com \
--cc=ak@suse.de \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=mulix@mulix.org \
--cc=tony.luck@intel.com \
/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