mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luming Yu <luming.yu@gmail.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: dwmw2@infradead.org, fenghua.yu@intel.com, tony.luck@intel.com,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [RFC patch] init default dma_ops to prepare intel_iommu_init  failure
Date: Thu, 13 Aug 2009 10:24:20 +0800	[thread overview]
Message-ID: <3877989d0908121924t1589941fmcd45d3669b78bba4@mail.gmail.com> (raw)
In-Reply-To: <20090813110948V.fujita.tomonori@lab.ntt.co.jp>

On Thu, Aug 13, 2009 at 10:11 AM, FUJITA
Tomonori<fujita.tomonori@lab.ntt.co.jp> wrote:
> On Wed, 12 Aug 2009 17:20:11 +0800
> Luming Yu <luming.yu@gmail.com> wrote:
>
>> Hi there,
>>
>> On ia64 platform with dmar table and new upstream
>> kernel(config_dmar_default_on enabled),
>> if intel_iommu_init ends up without dma_ops initialized or other iommu
>> failures.
>> We got nothing to fall back. The following patch fixes it.
>
> Hmm, I think that the current code should work.

Without the patch, I encounters boot failure with the following .config

162-CONFIG_IA64_GENERIC=y
163-# CONFIG_IA64_DIG is not set
164:# CONFIG_IA64_DIG_VTD is not set

> Note that IA64_DIG_VTD doesn't enable SWIOTLB so there is fall
> back. That's kinda the IA64 policy about non IA64_GENERIC kernel.
>
how comes?

  reply	other threads:[~2009-08-13  2:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-12  9:20 Luming Yu
2009-08-12  9:36 ` David Woodhouse
2009-08-12 18:17 ` Fenghua Yu
2009-08-12 18:20   ` David Woodhouse
2009-08-13  4:49   ` FUJITA Tomonori
2009-08-13  5:48     ` Luming Yu
2009-08-13  6:30       ` FUJITA Tomonori
2009-08-13  6:52       ` FUJITA Tomonori
2009-08-13  7:03         ` Luming Yu
2009-08-13  7:14           ` FUJITA Tomonori
2009-08-13  7:37             ` Luming Yu
2009-08-13  8:03               ` FUJITA Tomonori
2009-08-13  8:11                 ` Luming Yu
2009-08-13  8:49                   ` David Woodhouse
2009-08-13  9:00                     ` FUJITA Tomonori
2009-08-13  9:00                     ` Luming Yu
2009-08-13 17:08                       ` David Woodhouse
2009-08-13 17:30                         ` Yu, Fenghua
2009-08-14  5:44                           ` Luming Yu
2009-08-13  2:11 ` FUJITA Tomonori
2009-08-13  2:24   ` Luming Yu [this message]
2009-08-13  3:15     ` FUJITA Tomonori
2009-08-13  3:18       ` FUJITA Tomonori
2009-08-13  8:26         ` David Woodhouse
2009-08-13  8:35           ` FUJITA Tomonori

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=3877989d0908121924t1589941fmcd45d3669b78bba4@mail.gmail.com \
    --to=luming.yu@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=fenghua.yu@intel.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --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

all inboxes | Powered by JetHome®