From: Yuhong Bao <yuhongbao_386@hotmail.com>
To: <konrad.wilk@oracle.com>, <fujita.tomonori@lab.ntt.co.jp>
Cc: <sa212+lkml@cyconix.com>, <linux-kernel@vger.kernel.org>,
<x86@kernel.org>
Subject: RE: Driver: PCIe: 'pci_map_sg' returning invalid bus address?
Date: Thu, 12 Aug 2010 18:35:59 -0700 [thread overview]
Message-ID: <SNT125-W54B7AF8536BAFB36EB0118C3980@phx.gbl> (raw)
In-Reply-To: <20100804145154.GC23544@phenom.dumpdata.com>
> > - add swiotlb support to x86_32 (I don't think that it's difficult but
> > I might miss something).
>
> I think the highmem support might be a bit tricky. The PowerPC folks
> did some work in there, so it _ought_ to work.
>
> Evan, you could edit arch/x86/Kconfig and change:
> config SWIOTLB
> def_bool y if X86_64
>
> to say
> def_bool y if X86
>
> and see how it works? FYI, it might wreak havoc on your machine thought,
> so be sure you have a fail-safe kernel and backup your root/home
> directory.
>
> (FYI, I made Xen-SWIOTLB be capable of running under X86_32 and so far
> no trouble.. but that is not baremetal obviously).
In fact, if you are going to port swiotlb, why not port the entire iommu support to x86_32 with PAE too?
In fact, I am really irritated at how the x86-64 port was developed completely separate from mainline, when
it is just a variant of the same x86 arch. For another example of this, look at the history of ACPI SRAT support
in Linux.
Yuhong Bao
next prev parent reply other threads:[~2010-08-13 1:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-28 10:13 Evan Lavelle
2010-08-04 9:26 ` Evan Lavelle
2010-08-04 10:08 ` FUJITA Tomonori
2010-08-04 11:22 ` Evan Lavelle
2010-08-04 12:03 ` FUJITA Tomonori
2010-08-04 14:51 ` Konrad Rzeszutek Wilk
2010-08-13 1:35 ` Yuhong Bao [this message]
2010-08-14 15:25 ` Evan Lavelle
2010-08-16 3:31 ` Robert Hancock
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=SNT125-W54B7AF8536BAFB36EB0118C3980@phx.gbl \
--to=yuhongbao_386@hotmail.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sa212+lkml@cyconix.com \
--cc=x86@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 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®