From: Ingo Molnar <mingo@elte.hu>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: jeremy@goop.org, beckyb@kernel.crashing.org, jj@chaosbits.net,
weiyi.huang@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: swiotlb: remove duplicated #include
Date: Sun, 4 Jan 2009 14:01:13 +0100 [thread overview]
Message-ID: <20090104130113.GA24506@elte.hu> (raw)
In-Reply-To: <20090104214109A.fujita.tomonori@lab.ntt.co.jp>
* FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
> > In a few days, but wanted to hear back from either Jeremy or Becky
> > first about how well they actually work in their usecases.
>
> Well, you don't need to wait, I think.
>
> All Jeremy and Becky need is adding highmem support to swiotlb. How we
> support it doesn't matter. We can choose better one.
>
> We all (including Jeremy) agreed that Becky's physical address scheme is
> better (simpler) than Jeremy's struct page and offset scheme. Surely,
> Becky's scheme works for Xen and him (Jeremy said that he tested it
> lightly).
Jeremy said, when he submitted this series, shortly before Christmas:
>> Here's a work in progress series [...]
>>
>> Quick testing showed no problems, but I haven't had the chance to do
>> anything extensive.
Jeremy, did you have a chance to do more testing with the current
tip/master bits on Xen, so that we can push it to Linus?
> One remaining issue is how to support map_page/unmap_page. As we
> discussed, we can add some workarounds for it but it's better to unify
> dma_mapping_ops. I send patches to do it after testing them on an IA64
> box tomorrow.
ok.
Ingo
next prev parent reply other threads:[~2009-01-04 13:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 3:13 swiotlb: remove duplicated #include Huang Weiyi
2009-01-04 9:59 ` Jesper Juhl
2009-01-04 11:25 ` Ingo Molnar
2009-01-04 12:04 ` FUJITA Tomonori
2009-01-04 12:19 ` Ingo Molnar
2009-01-04 12:41 ` FUJITA Tomonori
2009-01-04 13:01 ` Ingo Molnar [this message]
2009-01-04 22:48 ` Jeremy Fitzhardinge
2009-01-05 2:40 ` FUJITA Tomonori
2009-01-05 13:16 ` Ingo Molnar
2009-01-09 16:37 ` Ian Campbell
2009-01-09 17:36 ` Becky Bruce
2009-01-09 18:10 ` Ian Campbell
2009-01-09 18:32 ` [PATCH 0/2] " Ian Campbell
2009-01-09 18:32 ` [PATCH 1/2] swiotlb: range_needs_mapping should take a physical address Ian Campbell
2009-01-09 18:32 ` [PATCH 2/2] swiotlb: do not use sg_virt() Ian Campbell
2009-01-11 3:58 ` FUJITA Tomonori
2009-01-11 3:58 ` [PATCH 1/2] swiotlb: range_needs_mapping should take a physical address FUJITA Tomonori
2009-01-11 3:55 ` [PATCH 0/2] Re: swiotlb: remove duplicated #include Ingo Molnar
2009-01-11 4:00 ` FUJITA Tomonori
2009-01-11 4:04 ` Ingo Molnar
2009-01-11 4:22 ` FUJITA Tomonori
2009-01-11 4:32 ` Ingo Molnar
2009-01-11 4:46 ` 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=20090104130113.GA24506@elte.hu \
--to=mingo@elte.hu \
--cc=beckyb@kernel.crashing.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jeremy@goop.org \
--cc=jj@chaosbits.net \
--cc=linux-kernel@vger.kernel.org \
--cc=weiyi.huang@gmail.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