From: "Leonardo Chiquitto" <lchiquitto@novell.com>
To: tony.luck@intel.com,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
linux-ia64@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ia64: fix SBA IOMMU to handle allocation failure
Date: Wed, 21 Oct 2009 13:29:17 +0000 [thread overview]
Message-ID: <4ADEF08D020000860004410B@sinclair.provo.novell.com> (raw)
In-Reply-To: <20091018140631K.fujita.tomonori@lab.ntt.co.jp>
> This is an updated patch of the patch that I've posted one year
> ago. Shehjar reported the problem and confirmed that the patch fixes
> it:
>
> http://lkml.indiana.edu/hypermail/linux/kernel/0811.0/01562.html
>
> Leonardo told me that he hit the same problem and confirmed that the
> patch fixes it.
>
> > From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> Subject: [PATCH] ia64: fix SBA IOMMU to handle allocation failure properly
>
> It's possible that SBA IOMMU might fail to find I/O space under heavy
> I/Os. SBA IOMMU panics on allocation failure but it shouldn't; drivers
> can handle the failure. The majority of other IOMMU drivers don't
> panic on allocation failure.
>
> This patch fixes SBA IOMMU path to handle allocation failure properly.
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Thanks for refreshing and resubmitting this. I just received feedback
confirming that the patch resolves the problem.
Kind regards,
Leonardo
next prev parent reply other threads:[~2009-10-21 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-18 5:07 [PATCH] ia64: fix SBA IOMMU to handle allocation failure properly FUJITA Tomonori
2009-10-21 13:29 ` Leonardo Chiquitto [this message]
2009-12-15 10:36 ` [PATCH] ia64: fix SBA IOMMU to handle allocation failure Leonardo Chiquitto
2009-12-15 19:23 ` Luck, Tony
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=4ADEF08D020000860004410B@sinclair.provo.novell.com \
--to=lchiquitto@novell.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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