[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080922195059.008de827@infradead.org>
Date: Mon, 22 Sep 2008 19:50:59 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: Joerg Roedel <joerg.roedel@....com>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, iommu@...ts.linux-foundation.org,
David Woodhouse <dwmw2@...radead.org>,
Muli Ben-Yehuda <muli@...ibm.com>,
Amit Shah <amit.shah@...ranet.com>,
Ingo Molnar <mingo@...hat.com>,
FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Subject: Re: [PATCH 0/9][RFC] stackable dma_ops for x86
On Mon, 22 Sep 2008 19:41:28 -0700
Jeremy Fitzhardinge <jeremy@...p.org> wrote:
> Joerg Roedel wrote:
> > Its implemented using the per-device dma-ops already there. With
> > this patches there is a list of available dma_ops implementations
> > which are asked in a particular order if they can handle the
> > device. The first implementation which returns true is assigned to
> > the device as the per-device dma_ops structure.
> >
> > (Hmm, maybe the name stackable is misleading, is "dma_ops
> > multiplexing" better?)
>
> Is per-device the right level? Wouldn't per-bus make more sense?
not really; all DMA functions get a device as argument already anyway;
just going to bus makes no sense there.
Even if you set it the same for the whole bus almost all of the time...
the APIs just work per device.
(and device assignment clearly is per device as well)
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists