From: Andi Kleen <andi@firstfloor.org>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
muli@il.ibm.com, alexisb@us.ibm.com
Subject: Re: [PATCH 0/2] x86: per-device dma_mapping_ops
Date: Fri, 16 May 2008 07:24:33 +0200 [thread overview]
Message-ID: <482D1A91.3050803@firstfloor.org> (raw)
In-Reply-To: <20080516124446B.tomof@acm.org>
FUJITA Tomonori wrote:
> On Thu, 15 May 2008 12:48:04 +0200
> Andi Kleen <andi@firstfloor.org> wrote:
>
>>> I thought that KVM people want to do it per device (in the first
>>> case). So with my patchse, they can replace the dma_ops pointer in
>>> dev_archdata with what they want.
>> But where would they save the original pointer?
>
> Yeah, we need an extra mechanism for that but it's same for the
> system-wide dma_ops pointer (i.e. without my patches), isn't it?
>
> I'm still not sure how this patchset make it impossible to have stack
> dma_ops. These people need per-device dma_ops and we can do stack
> per-device dma_ops?
Anybody who does stack ops in your scheme would need to hook into new
device creation and an own per device saving pointer. Also there
are livetime issues when to wrap.
It's certainly possible, but likely complicated
-Andi
next prev parent reply other threads:[~2008-05-16 5:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 6:04 [PATCH 0/2] x86: per-device dma_mapping_ops FUJITA Tomonori
2008-05-13 6:04 ` [PATCH 1/2] add the device argument to dma_mapping_error FUJITA Tomonori
2008-05-13 6:04 ` [PATCH 2/2] x86: per-device dma_mapping_ops support FUJITA Tomonori
2008-05-14 5:55 ` Muli Ben-Yehuda
2008-05-15 20:45 ` Yinghai Lu
2008-05-16 3:44 ` FUJITA Tomonori
2008-05-13 15:39 ` [PATCH 1/2] add the device argument to dma_mapping_error Randy Dunlap
2008-05-15 1:12 ` FUJITA Tomonori
2008-05-14 5:49 ` [PATCH 0/2] x86: per-device dma_mapping_ops Muli Ben-Yehuda
2008-05-15 1:12 ` FUJITA Tomonori
2008-05-15 2:00 ` Alexis Bruemmer
2008-05-15 2:30 ` FUJITA Tomonori
2008-05-15 18:21 ` Alexis Bruemmer
2008-05-15 15:17 ` Muli Ben-Yehuda
2008-05-15 15:15 ` Muli Ben-Yehuda
2008-05-15 9:01 ` Andi Kleen
2008-05-15 9:16 ` FUJITA Tomonori
2008-05-15 9:30 ` Andi Kleen
2008-05-15 9:41 ` FUJITA Tomonori
2008-05-15 10:48 ` Andi Kleen
2008-05-15 15:32 ` Muli Ben-Yehuda
2008-05-16 3:44 ` FUJITA Tomonori
2008-05-16 5:24 ` Andi Kleen [this message]
2008-05-19 6:32 ` FUJITA Tomonori
2008-05-15 15:26 ` Muli Ben-Yehuda
2008-05-15 21:03 ` Andi Kleen
2008-05-15 21:39 ` Muli Ben-Yehuda
2008-05-15 21:45 ` Andi Kleen
2008-05-15 21:53 ` Muli Ben-Yehuda
2008-05-15 22:05 ` Muli Ben-Yehuda
2008-05-15 18:25 ` Alexis Bruemmer
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=482D1A91.3050803@firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=alexisb@us.ibm.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.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;
as well as URLs for NNTP newsgroup(s).