From: David Woodhouse <dwmw2@infradead.org>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: Jerome Glisse <jglisse@redhat.com>,
ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Core Kernel support for Compute-Offload Devices
Date: Mon, 03 Aug 2015 22:51:16 +0100 [thread overview]
Message-ID: <1438638676.26511.457.camel@infradead.org> (raw)
In-Reply-To: <20150803213443.GE2981@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
On Mon, 2015-08-03 at 17:34 -0400, Jerome Glisse wrote:
> Note that i really would like the ASID <-> mm struct 1 to 1 match but
> i am just fearing this is not something that can be common to all
> platform.
You are quite possibly right. And we don't *have* to force it.
We probably do need to design the core IOMMU interfaces to tolerate
either.
The actual PASID allocation wants to be outside the individual IOMMU
driver anyway. The main thing we need to do is let the IOMMU know if it
can share PASID tables or not.
I'm now pondering a 'pasid_space' object which will contain an IDR or
something for allocating PASIDs, and when one of those object is
created we can also call into an IOMMU driver function for allocating a
set of PASID tables (if it needs to). You then attach a given device to
a pasid space.
I suppose it ends up looking at lot like the existing IOMMU domains
that you can map multiple devices into.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5691 bytes --]
next prev parent reply other threads:[~2015-08-03 21:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 13:00 Joerg Roedel
2015-07-30 13:31 ` David Woodhouse
2015-07-30 13:54 ` Joerg Roedel
2015-07-31 16:34 ` Jerome Glisse
2015-08-03 18:51 ` David Woodhouse
2015-08-03 19:01 ` Jerome Glisse
2015-08-03 19:07 ` Andy Lutomirski
2015-08-03 19:56 ` Jerome Glisse
2015-08-03 21:10 ` Joerg Roedel
2015-08-03 21:12 ` David Woodhouse
2015-08-03 21:31 ` Joerg Roedel
2015-08-03 21:34 ` Jerome Glisse
2015-08-03 21:51 ` David Woodhouse [this message]
2015-08-04 18:11 ` Catalin Marinas
2015-08-03 22:10 ` Benjamin Herrenschmidt
2015-07-30 22:32 ` Benjamin Herrenschmidt
2015-08-01 16:10 ` Joerg Roedel
2015-07-31 14:52 ` Rik van Riel
2015-07-31 16:13 ` Jerome Glisse
2015-08-01 15:57 ` Joerg Roedel
2015-08-01 19:08 ` Jerome Glisse
2015-08-03 16:02 ` Joerg Roedel
2015-08-03 18:28 ` Jerome Glisse
2015-08-01 20:46 ` Arnd Bergmann
2015-08-03 16:10 ` Joerg Roedel
2015-08-03 19:23 ` Arnd Bergmann
2015-08-04 15:40 ` Christoph Lameter
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=1438638676.26511.457.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=j.glisse@gmail.com \
--cc=jglisse@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.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