- Linaro-mm-sig - lists.linaro.org

[PATCHv5 00/13] Integration of videobuf2 with dmabuf

by Tomasz Stanislawski

Hello everyone, This patchset adds support for DMABUF [2] importing to V4L2 stack. The support for DMABUF exporting was moved to separate patchset due to dependency on patches for DMA mapping redesign by Marek Szyprowski [4]. v5: - removed change of importer/exporter behaviour - fixes vb2_dc_pages_to_sgt basing on Laurent's hints - changed pin/unpin words to lock/unlock in Doc v4: - rebased on mainline 3.4-rc2 - included missing importing support for s5p-fimc and s5p-tv - added patch for changing map/unmap for importers - fixes to Documentation part - coding style fixes - pairing {map/unmap}_dmabuf in vb2-core - fixing variable types and semantic of arguments in videobufb2-dma-contig.c v3: - rebased on mainline 3.4-rc1 - split 'code refactor' patch to multiple smaller patches - squashed fixes to Sumit's patches - patchset is no longer dependant on 'DMA mapping redesign' - separated path for handling IO and non-IO mappings - add documentation for DMABUF importing to V4L - removed all DMABUF exporter related code - removed usage of dma_get_pages extension v2: - extended VIDIOC_EXPBUF argument from integer memoffset to struct v4l2_exportbuffer - added patch that breaks DMABUF spec on (un)map_atachment callcacks but allows to work with existing implementation of DMABUF prime in DRM - all dma-contig code refactoring patches were squashed - bugfixes v1: List of changes since [1]. - support for DMA api extension dma_get_pages, the function is used to retrieve pages used to create DMA mapping. - small fixes/code cleanup to videobuf2 - added prepare and finish callbacks to vb2 allocators, it is used keep consistency between dma-cpu acess to the memory (by Marek Szyprowski) - support for exporting of DMABUF buffer in V4L2 and Videobuf2, originated from [3]. - support for dma-buf exporting in vb2-dma-contig allocator - support for DMABUF for s5p-tv and s5p-fimc (capture interface) drivers, originated from [3] - changed handling for userptr buffers (by Marek Szyprowski, Andrzej Pietrasiewicz) - let mmap method to use dma_mmap_writecombine call (by Marek Szyprowski) [1] http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/4296… [2] https://lkml.org/lkml/2011/12/26/29 [3] http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/3635… [4] http://thread.gmane.org/gmane.linux.kernel.cross-arch/12819 Andrzej Pietrasiewicz (1): v4l: vb2-dma-contig: add support for scatterlist in userptr mode Laurent Pinchart (2): v4l: vb2-dma-contig: Shorten vb2_dma_contig prefix to vb2_dc v4l: vb2-dma-contig: Reorder functions Marek Szyprowski (2): v4l: vb2: add prepare/finish callbacks to allocators v4l: vb2-dma-contig: add prepare/finish to dma-contig allocator Sumit Semwal (4): v4l: Add DMABUF as a memory type v4l: vb2: add support for shared buffer (dma_buf) v4l: vb: remove warnings about MEMORY_DMABUF v4l: vb2-dma-contig: add support for dma_buf importing Tomasz Stanislawski (4): Documentation: media: description of DMABUF importing in V4L2 v4l: vb2-dma-contig: Remove unneeded allocation context structure v4l: s5p-tv: mixer: support for dmabuf importing v4l: s5p-fimc: support for dmabuf importing Documentation/DocBook/media/v4l/compat.xml | 4 + Documentation/DocBook/media/v4l/io.xml | 179 +++++++ .../DocBook/media/v4l/vidioc-create-bufs.xml | 1 + Documentation/DocBook/media/v4l/vidioc-qbuf.xml | 15 + Documentation/DocBook/media/v4l/vidioc-reqbufs.xml | 47 +- drivers/media/video/Kconfig | 1 + drivers/media/video/s5p-fimc/fimc-capture.c | 2 +- drivers/media/video/s5p-tv/Kconfig | 1 + drivers/media/video/s5p-tv/mixer_video.c | 2 +- drivers/media/video/videobuf-core.c | 4 + drivers/media/video/videobuf2-core.c | 207 ++++++++- drivers/media/video/videobuf2-dma-contig.c | 529 +++++++++++++++++--- include/linux/videodev2.h | 7 + include/media/videobuf2-core.h | 34 ++ 14 files changed, 932 insertions(+), 101 deletions(-) -- 1.7.5.4

13 years, 7 months

4
22
0 0

Minutes from V4L2 update call

by Christian Robottom Reis

Hey there, We ran a call today on the topics of V4L2/dmabuf integration and the DMA mapping changes; I've included minutes and actions below. In summary: - We're not going to see the V4L2 patches in 3.4; they haven't had enough review or testing and Mauro is very busy this merge window. - We're going to put in effort to validate the work on Exynos4 and OMAP4 using test applications that Rob and Tomasz are maintaining. - Sumit's maintaining an up-to-date branch containing all the in-flight DRM/V4L2/dmabuf-dependent work that we can carry meanwhile: http://git.linaro.org/gitweb?p=people/sumitsemwal/linux-3.x.git;a=shortlog;… Laurent, I missed one thing that you mentioned in the call and it's included in an XXX: below; if you could note what it was it would be great. Please feel free to correct my possibly wild misunderstandings in the minutes and summary above. Thanks! Attendees are all on the To: line. Tomasz: At the moment, have PoC support for import/export dma-buf for V4L2 Modified patches by Sumit Supporting importer of dma-buf Exynos DRM and drm-prime Test application worked fine for V4L capture and DRM output Test application between two V4L devices Laurent has sent in review comments Tomasz: proposed extension to DMA Mapping -- dma_get_pages Currently difficult to change the camera address into list of pages DMA framework has the knowledge of this list and could do this Depends on dma_get_pages Needs to be merged first Test application posted to dri-devel with dependencies to run demo Many dependencies Topic: dmabuf importer from V4L2 For sharing with DRM do not need exporter Need some patches added to DRM prime prime for Exynos drm-prime ACTION: Tomasz to check with Inki Dae and David A. on status Will send request to Mauro? Doesn't think so, won't have enough time for testing RC is already open -- not enough time for that API details needs consideration Depends on how much time current project 2-3 weeks after the merge window closes 1 month to actually review Would like to see Exynos working Mauro has a Samsung V310/Exynos4 dev board Also wants to see tested with V4L driver virtual drivers also supporting dma-buf wants both importer and exporter? ACTION: Sumit to look into VV driver used for v4l2 testing needs importer and exporter Laurent has work that he can push forward in parallel API change ioctl addition that could be reviewed Rob: the demo had V4L importer and DRM exporter (?) There are some changes for prime changes Laurent: needs to implement importer/exporter camera piece With drm-prime-dmabuf patches drivers can be simplified Sumit: we have a new 3.3-WIP branch Rob could use that as a base and put DRM updates on it ACTION: Rob to pull in changes and update demonstration Rob: what camera does Mauro have? On the Samsung SDK, M5MOLS Mauro does have a Pandaboard with ov5650 camera but needs setting up and potential hardware mod ACTION: Mauro to take picture of setup for Sumit As a backup Rob could add a Tested-By for the changes Mauro essentially wants a test on With CPU access in dmabuf can use vmalloc Without dependency on dma mapping at all Without Russell's acceptance can't go forward with ARM-related pieces ACTION: Kiko to check with Nicolas on this piece, see if he can review or help Marek with the ARM-related pieces Tomasz could use the 3.3-WIP branch Sumit: rebasing not a good idea, but could pull in for-next Suggests Tomasz bases work on Linus' mainline Had problems with Tomasz' branch that is based on -next His branch includes Tomasz RFCv2 patches as well Laurent: agree with Sumit ACTION: Sumit to email Tomasz and CC: Inki Dae ACTION: send around latest drm-prime branch Tomasz: so no XXX: exporter support for V4L? Laurent: doesn't have time to update XXX at the moment Needs porting to videobuf2 Rob: Looks like Daniel V. has also replied to the V4L patches so it's going to be hard for 3.4 Mauro's lack of time makes 3.4 not possible anyway mmap support also likely to miss 3.4 EGLImage extension needs sorting out Can be carried in our WIP branch meanwhile Mauro: what are the test applications being used for dmabuf? Rob: using Panda with camera adapter board (omap-drm) Would like others to have similar setups Requires YUV sensor, but there are patches that support the RAW YUV conversion which allows other sensors to be used Mauro: but what software app are you using? Rob: has test code in github: https://github.com/robclark/omapdrmtest Tomasz: Have posted one test application on dri-devel (March 6th) http://www.spinics.net/lists/dri-devel/msg19634.html Second application posted to linux-media As a reply to RFCv1 dma-buf V4L2 patches (Jan 26th) http://www.mail-archive.com/linux-media@vger.kernel.org/msg42522.html Mauro: include both applications together with patches when posting Sumit: could ask Inki to provide similar exynos-drm test application in parallel to Rob's omap-drm; same interface will simplify testing Marek: device-to-device coordinate will be needed Will start next week ideally For a device-to-device operation, need this to avoid touching CPU cache Not sure about ARM stuff for 3.4; need review If they don't go in, will keep on dma-mapping-next Konrad's comments are addressed and Reviewed-bys added Take care, -- Christian Robottom Reis, Engineering VP Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935 Linaro.org: Open Source Software for ARM SoCs

13 years, 7 months

11
31
0 0

[PATCH] drm: pass dev to drm_vm_{open, close}_locked()

by Rob Clark

From: Rob Clark <rob(a)ti.com> Previously these functions would assume that vma->vm_file was the drm_file. Although if in some cases if the drm driver needs to use something else for the backing file (such as the tmpfs filp) then this assumption is no longer true. But vma->vm_private_data is still the GEM object. With this change, now the drm_device comes from the GEM object rather than the drm_file so the driver is more free to play with vma->vm_file. The scenario where this comes up is for mmap'ing of cached dmabuf's for non-coherent systems, where the driver needs to use fault handling and PTE shootdown to simulate coherency. We can't use the vma->vm_file of the dmabuf, which is using anon_inode's address_space. The most straightforward thing to do is to use the GEM object's obj->filp for vma->vm_file in all cases, for which we need this patch. Signed-off-by: Rob Clark <rob(a)ti.com> --- drivers/gpu/drm/drm_gem.c | 6 +++--- drivers/gpu/drm/drm_vm.c | 18 ++++++++---------- include/drm/drmP.h | 4 ++-- 3 files changed, 13 insertions(+), 15 deletions(-) diff --git a/drivers/gpu/drm/drm_gem.c b/drivers/gpu/drm/drm_gem.c index 83114b5..475b300 100644 --- a/drivers/gpu/drm/drm_gem.c +++ b/drivers/gpu/drm/drm_gem.c @@ -628,7 +628,7 @@ void drm_gem_vm_open(struct vm_area_struct *vma) drm_gem_object_reference(obj); mutex_lock(&obj->dev->struct_mutex); - drm_vm_open_locked(vma); + drm_vm_open_locked(obj->dev, vma); mutex_unlock(&obj->dev->struct_mutex); } EXPORT_SYMBOL(drm_gem_vm_open); @@ -639,7 +639,7 @@ void drm_gem_vm_close(struct vm_area_struct *vma) struct drm_device *dev = obj->dev; mutex_lock(&dev->struct_mutex); - drm_vm_close_locked(vma); + drm_vm_close_locked(obj->dev, vma); drm_gem_object_unreference(obj); mutex_unlock(&dev->struct_mutex); } @@ -712,7 +712,7 @@ int drm_gem_mmap(struct file *filp, struct vm_area_struct *vma) */ drm_gem_object_reference(obj); - drm_vm_open_locked(vma); + drm_vm_open_locked(dev, vma); out_unlock: mutex_unlock(&dev->struct_mutex); diff --git a/drivers/gpu/drm/drm_vm.c b/drivers/gpu/drm/drm_vm.c index 1495618..961ee08 100644 --- a/drivers/gpu/drm/drm_vm.c +++ b/drivers/gpu/drm/drm_vm.c @@ -406,10 +406,9 @@ static const struct vm_operations_struct drm_vm_sg_ops = { * Create a new drm_vma_entry structure as the \p vma private data entry and * add it to drm_device::vmalist. */ -void drm_vm_open_locked(struct vm_area_struct *vma) +void drm_vm_open_locked(struct drm_device *dev, + struct vm_area_struct *vma) { - struct drm_file *priv = vma->vm_file->private_data; - struct drm_device *dev = priv->minor->dev; struct drm_vma_entry *vma_entry; DRM_DEBUG("0x%08lx,0x%08lx\n", @@ -430,14 +429,13 @@ static void drm_vm_open(struct vm_area_struct *vma) struct drm_device *dev = priv->minor->dev; mutex_lock(&dev->struct_mutex); - drm_vm_open_locked(vma); + drm_vm_open_locked(dev, vma); mutex_unlock(&dev->struct_mutex); } -void drm_vm_close_locked(struct vm_area_struct *vma) +void drm_vm_close_locked(struct drm_device *dev, + struct vm_area_struct *vma) { - struct drm_file *priv = vma->vm_file->private_data; - struct drm_device *dev = priv->minor->dev; struct drm_vma_entry *pt, *temp; DRM_DEBUG("0x%08lx,0x%08lx\n", @@ -467,7 +465,7 @@ static void drm_vm_close(struct vm_area_struct *vma) struct drm_device *dev = priv->minor->dev; mutex_lock(&dev->struct_mutex); - drm_vm_close_locked(vma); + drm_vm_close_locked(dev, vma); mutex_unlock(&dev->struct_mutex); } @@ -519,7 +517,7 @@ static int drm_mmap_dma(struct file *filp, struct vm_area_struct *vma) vma->vm_flags |= VM_RESERVED; /* Don't swap */ vma->vm_flags |= VM_DONTEXPAND; - drm_vm_open_locked(vma); + drm_vm_open_locked(dev, vma); return 0; } @@ -670,7 +668,7 @@ int drm_mmap_locked(struct file *filp, struct vm_area_struct *vma) vma->vm_flags |= VM_RESERVED; /* Don't swap */ vma->vm_flags |= VM_DONTEXPAND; - drm_vm_open_locked(vma); + drm_vm_open_locked(dev, vma); return 0; } diff --git a/include/drm/drmP.h b/include/drm/drmP.h index dd73104..213a85a 100644 --- a/include/drm/drmP.h +++ b/include/drm/drmP.h @@ -1309,8 +1309,8 @@ extern int drm_release(struct inode *inode, struct file *filp); /* Mapping support (drm_vm.h) */ extern int drm_mmap(struct file *filp, struct vm_area_struct *vma); extern int drm_mmap_locked(struct file *filp, struct vm_area_struct *vma); -extern void drm_vm_open_locked(struct vm_area_struct *vma); -extern void drm_vm_close_locked(struct vm_area_struct *vma); +extern void drm_vm_open_locked(struct drm_device *dev, struct vm_area_struct *vma); +extern void drm_vm_close_locked(struct drm_device *dev, struct vm_area_struct *vma); extern unsigned int drm_poll(struct file *filp, struct poll_table_struct *wait); /* Memory management support (drm_memory.h) */ -- 1.7.9.5

13 years, 7 months

1
0
0 0

Re: [Linaro-mm-sig] ION interfaces - support for IOMMU

by Hiroshi Doyu

Hi Nishanth, On Sun, 29 Apr 2012 21:56:26 +0200 Nishanth Peethambaran <nishanth.peethu(a)gmail.com> wrote: > Hi Rebecca, Doyu, > > I am sending this mail related to the mailchain seen in the link: > http://lists.linaro.org/pipermail/linaro-mm-sig/2012-January/001009.html > I am not sure where to post the query. If I am supposed to post in a > mail-list, let me know and > I shall post it there. I think that "linaro-mm-sig(a)lists.linaro.org" would be the best for further discussion, putting linaro-mm-sig on Cc:. > I am also trying to use ION for IOMMU and have some comments on ION in > general and specific to IOMMU usage. > 1. Isn't 2 heap types sufficient - physically contiguous and non-contiguous? > We could treat physical carveout and sytem_contig(kmalloc) as two > implementations of physcially contiguous type > and add the heaps with separate ids. Order of using them would be > as ION currently does - order of registration of heap. > IOMMU heap type also won't be needed as that is just a different > implementation of system heap (no kernel map at allocation > time). Please correct me if I am missing something. > > 2. The user space interface does not support exposing a dma_addr_t to > user space. We could add this using custom ioctl. > But, shouldn't this be a standard interface. For example, to > protect/hide the graphics core IP details, platfrom provider would > prefer to generate graphics core program from user space (license > requirements) and only pass the final buffer containing > the program to the driver. If an IOMMU is used, the dma/iommu > address mapping would be needed in user space to embed > few pointers in the graphics program. > > 3. With the current ION implementation, how do we keep user space > code/drivers independent of platform supporting IOMMU or not? > For example, CMA is supported by the platform but want to restrict > buffers allocated from CMA only if necessary (to avoid migration > overheads). How does a client decide whether to request for > physically contiguous buffers (CMA) ot IOMMU buffers (buddy allocator) > In one platform, the buffer could be shared with an IP with IOMMU > support (eg: camera and codec both supporting IOMMU) - CMA not needed. > In another platform the buffer may have to be shared with an IP > which works on physical address space. buffer has to be > shared with an IP which does not support IOMMU(to avoid migrations) > - we need to use physically contiguous heap(CMA). > I see dma buf sharing API has a callback to exporter at attachment > time so that exporter can pass of fail the sharing based on the > receiver. > Don't we need something similar and more? > > ION version referred: > commit 3fe24366a40147d7c776e1f291193fd3b61f217d > Author: Iliyan Malchev <malchev(a)google.com> > Date: Tue Aug 9 14:42:08 2011 -0700 > > - Nishanth Peethambaran

13 years, 7 months

1
0
0 0

[PATCHv5 00/13] Integration of videobuf2 with dmabuf

by Tomasz Stanislawski

Hello everyone, This patchset adds support for DMABUF [2] importing to V4L2 stack. The support for DMABUF exporting was moved to separate patchset due to dependency on patches for DMA mapping redesign by Marek Szyprowski [4]. v5: - removed change of importer/exporter behaviour - fixes vb2_dc_pages_to_sgt basing on Laurent's hints - changed pin/unpin words to lock/unlock in Doc v4: - rebased on mainline 3.4-rc2 - included missing importing support for s5p-fimc and s5p-tv - added patch for changing map/unmap for importers - fixes to Documentation part - coding style fixes - pairing {map/unmap}_dmabuf in vb2-core - fixing variable types and semantic of arguments in videobufb2-dma-contig.c v3: - rebased on mainline 3.4-rc1 - split 'code refactor' patch to multiple smaller patches - squashed fixes to Sumit's patches - patchset is no longer dependant on 'DMA mapping redesign' - separated path for handling IO and non-IO mappings - add documentation for DMABUF importing to V4L - removed all DMABUF exporter related code - removed usage of dma_get_pages extension v2: - extended VIDIOC_EXPBUF argument from integer memoffset to struct v4l2_exportbuffer - added patch that breaks DMABUF spec on (un)map_atachment callcacks but allows to work with existing implementation of DMABUF prime in DRM - all dma-contig code refactoring patches were squashed - bugfixes v1: List of changes since [1]. - support for DMA api extension dma_get_pages, the function is used to retrieve pages used to create DMA mapping. - small fixes/code cleanup to videobuf2 - added prepare and finish callbacks to vb2 allocators, it is used keep consistency between dma-cpu acess to the memory (by Marek Szyprowski) - support for exporting of DMABUF buffer in V4L2 and Videobuf2, originated from [3]. - support for dma-buf exporting in vb2-dma-contig allocator - support for DMABUF for s5p-tv and s5p-fimc (capture interface) drivers, originated from [3] - changed handling for userptr buffers (by Marek Szyprowski, Andrzej Pietrasiewicz) - let mmap method to use dma_mmap_writecombine call (by Marek Szyprowski) [1] http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/4296… [2] https://lkml.org/lkml/2011/12/26/29 [3] http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/3635… [4] http://thread.gmane.org/gmane.linux.kernel.cross-arch/12819 Andrzej Pietrasiewicz (1): v4l: vb2-dma-contig: add support for scatterlist in userptr mode Laurent Pinchart (2): v4l: vb2-dma-contig: Shorten vb2_dma_contig prefix to vb2_dc v4l: vb2-dma-contig: Reorder functions Marek Szyprowski (2): v4l: vb2: add prepare/finish callbacks to allocators v4l: vb2-dma-contig: add prepare/finish to dma-contig allocator Sumit Semwal (4): v4l: Add DMABUF as a memory type v4l: vb2: add support for shared buffer (dma_buf) v4l: vb: remove warnings about MEMORY_DMABUF v4l: vb2-dma-contig: add support for dma_buf importing Tomasz Stanislawski (4): Documentation: media: description of DMABUF importing in V4L2 v4l: vb2-dma-contig: Remove unneeded allocation context structure v4l: s5p-tv: mixer: support for dmabuf importing v4l: s5p-fimc: support for dmabuf importing Documentation/DocBook/media/v4l/compat.xml | 4 + Documentation/DocBook/media/v4l/io.xml | 179 +++++++ .../DocBook/media/v4l/vidioc-create-bufs.xml | 1 + Documentation/DocBook/media/v4l/vidioc-qbuf.xml | 15 + Documentation/DocBook/media/v4l/vidioc-reqbufs.xml | 47 +- drivers/media/video/Kconfig | 1 + drivers/media/video/s5p-fimc/fimc-capture.c | 2 +- drivers/media/video/s5p-tv/Kconfig | 1 + drivers/media/video/s5p-tv/mixer_video.c | 2 +- drivers/media/video/videobuf-core.c | 4 + drivers/media/video/videobuf2-core.c | 207 ++++++++- drivers/media/video/videobuf2-dma-contig.c | 529 +++++++++++++++++--- include/linux/videodev2.h | 7 + include/media/videobuf2-core.h | 34 ++ 14 files changed, 932 insertions(+), 101 deletions(-) -- 1.7.5.4

13 years, 7 months

2
2
0 0

[PATCH] dma-buf: mmap support

by Daniel Vetter

Compared to Rob Clark's RFC I've ditched the prepare/finish hooks and corresponding ioctls on the dma_buf file. The major reason for that is that many people seem to be under the impression that this is also for synchronization with outstanding asynchronous processsing. I'm pretty massively opposed to this because: - It boils down reinventing a new rather general-purpose userspace synchronization interface. If we look at things like futexes, this is hard to get right. - Furthermore a lot of kernel code has to interact with this synchronization primitive. This smells a look like the dri1 hw_lock, a horror show I prefer not to reinvent. - Even more fun is that multiple different subsystems would interact here, so we have plenty of opportunities to create funny deadlock scenarios. I think synchronization is a wholesale different problem from data sharing and should be tackled as an orthogonal problem. Now we could demand that prepare/finish may only ensure cache coherency (as Rob intended), but that runs up into the next problem: We not only need mmap support to facilitate sw-only processing nodes in a pipeline (without jumping through hoops by importing the dma_buf into some sw-access only importer), which allows for a nicer ION->dma-buf upgrade path for existing Android userspace. We also need mmap support for existing importing subsystems to support existing userspace libraries. And a loot of these subsystems are expected to export coherent userspace mappings. So prepare/finish can only ever be optional and the exporter /needs/ to support coherent mappings. Given that mmap access is always somewhat fallback-y in nature I've decided to drop this optimization, instead of just making it optional. If we demonstrate a clear need for this, supported by benchmark results, we can always add it in again later as an optional extension. Other differences compared to Rob's RFC is the above mentioned support for mapping a dma-buf through facilities provided by the importer. Which results in mmap support no longer being optional. Note that this dma-buf mmap patch does _not_ support every possible insanity an existing subsystem could pull of with mmap: Because it does not allow to intercept pagefaults and shoot down ptes importing subsystems can't add some magic of their own at these points (e.g. to automatically synchronize with outstanding rendering or set up some special resources). I've done a cursory read through a few mmap implementions of various subsytems and I'm hopeful that we can avoid this (and the complexity it'd bring with it). Additonally I've extended the documentation a bit to explain the hows and whys of this mmap extension. In case we ever want to add support for explicitly cache maneged userspace mmap with a prepare/finish ioctl pair, we could specify that userspace needs to mmap a different part of the dma_buf, e.g. the range starting at dma_buf->size up to dma_buf->size*2. This works because the size of a dma_buf is invariant over it's lifetime. The exporter would obviously need to fall back to coherent mappings for both ranges if a legacy clients maps the coherent range and the architecture cannot suppor conflicting caching policies. Also, this would obviously be optional and userspace needs to be able to fall back to coherent mappings. v2: - Spelling fixes from Rob Clark. - Compile fix for !DMA_BUF from Rob Clark. - Extend commit message to explain how explicitly cache managed mmap support could be added later. - Extend the documentation with implementations notes for exporters that need to manually fake coherency. Cc: Rob Clark <rob.clark(a)linaro.org> Cc: Rebecca Schultz Zavin <rebecca(a)android.com> Signed-Off-by: Daniel Vetter <daniel.vetter(a)ffwll.ch> --- Documentation/dma-buf-sharing.txt | 98 ++++++++++++++++++++++++++++++++++--- drivers/base/dma-buf.c | 64 +++++++++++++++++++++++- include/linux/dma-buf.h | 16 ++++++ 3 files changed, 170 insertions(+), 8 deletions(-) diff --git a/Documentation/dma-buf-sharing.txt b/Documentation/dma-buf-sharing.txt index 3bbd5c5..5ff4d2b 100644 --- a/Documentation/dma-buf-sharing.txt +++ b/Documentation/dma-buf-sharing.txt @@ -29,13 +29,6 @@ The buffer-user in memory, mapped into its own address space, so it can access the same area of memory. -*IMPORTANT*: [see https://lkml.org/lkml/2011/12/20/211 for more details] -For this first version, A buffer shared using the dma_buf sharing API: -- *may* be exported to user space using "mmap" *ONLY* by exporter, outside of - this framework. -- with this new iteration of the dma-buf api cpu access from the kernel has been - enable, see below for the details. - dma-buf operations for device dma only -------------------------------------- @@ -313,6 +306,83 @@ Access to a dma_buf from the kernel context involves three steps: enum dma_data_direction dir); +Direct Userspace Access/mmap Support +------------------------------------ + +Being able to mmap an export dma-buf buffer object has 2 main use-cases: +- CPU fallback processing in a pipeline and +- supporting existing mmap interfaces in importers. + +1. CPU fallback processing in a pipeline + + In many processing pipelines it is sometimes required that the cpu can access + the data in a dma-buf (e.g. for thumbnail creation, snapshots, ...). To avoid + the need to handle this specially in userspace frameworks for buffer sharing + it's ideal if the dma_buf fd itself can be used to access the backing storage + from userspace using mmap. + + Furthermore Android's ION framework already supports this (and is otherwise + rather similar to dma-buf from a userspace consumer side with using fds as + handles, too). So it's beneficial to support this in a similar fashion on + dma-buf to have a good transition path for existing Android userspace. + + No special interfaces, userspace simply calls mmap on the dma-buf fd. + +2. Supporting existing mmap interfaces in exporters + + Similar to the motivation for kernel cpu access it is again important that + the userspace code of a given importing subsystem can use the same interfaces + with a imported dma-buf buffer object as with a native buffer object. This is + especially important for drm where the userspace part of contemporary OpenGL, + X, and other drivers is huge, and reworking them to use a different way to + mmap a buffer rather invasive. + + The assumption in the current dma-buf interfaces is that redirecting the + initial mmap is all that's needed. A survey of some of the existing + subsystems shows that no driver seems to do any nefarious thing like syncing + up with outstanding asynchronous processing on the device or allocating + special resources at fault time. So hopefully this is good enough, since + adding interfaces to intercept pagefaults and allow pte shootdowns would + increase the complexity quite a bit. + + Interface: + int dma_buf_mmap(struct dma_buf *, struct vm_area_struct *, + unsigned long); + + If the importing subsystem simply provides a special-purpose mmap call to set + up a mapping in userspace, calling do_mmap with dma_buf->file will equally + achieve that for a dma-buf object. + +3. Implementation notes for exporters + + Because dma-buf buffers have invariant size over their lifetime, the dma-buf + core checks whether a vma is too large and rejects such mappings. The + exporter hence does not need to duplicate this check. + + Because existing importing subsystems might presume coherent mappings for + userspace, the exporter needs to set up a coherent mapping. If that's not + possible, it needs to fake coherency by manually shooting down ptes when + leaving the cpu domain and flushing caches at fault time. Note that all the + dma_buf files share the same anon inode, hence the exporter needs to replace + the dma_buf file stored in vma->vm_file with it's own if pte shootdown is + requred. This is because the kernel uses the underlying inode's address_space + for vma tracking (and hence pte tracking at shootdown time with + unmap_mapping_range). + + If the above shootdown dance turns out to be too expensive in certain + scenarios, we can extend dma-buf with a more explicit cache tracking scheme + for userspace mappings. But the current assumption is that using mmap is + always a slower path, so some inefficiencies should be acceptable. + + Exporters that shoot down mappings (for any reasons) shall not do any + synchronization at fault time with outstanding device operations. + Synchronization is an orthogonal issue to sharing the backing storage of a + buffer and hence should not be handled by dma-buf itself. This is explictly + mentioned here because many people seem to want something like this, but if + different exporters handle this differently, buffer sharing can fail in + interesting ways depending upong the exporter (if userspace starts depending + upon this implicit synchronization). + Miscellaneous notes ------------------- @@ -336,6 +406,20 @@ Miscellaneous notes the exporting driver to create a dmabuf fd must provide a way to let userspace control setting of O_CLOEXEC flag passed in to dma_buf_fd(). +- If an exporter needs to manually flush caches and hence needs to fake + coherency for mmap support, it needs to be able to zap all the ptes pointing + at the backing storage. Now linux mm needs a struct address_space associated + with the struct file stored in vma->vm_file to do that with the function + unmap_mapping_range. But the dma_buf framework only backs every dma_buf fd + with the anon_file struct file, i.e. all dma_bufs share the same file. + + Hence exporters need to setup their own file (and address_space) association + by setting vma->vm_file and adjusting vma->vm_pgoff in the dma_buf mmap + callback. In the specific case of a gem driver the exporter could use the + shmem file already provided by gem (and set vm_pgoff = 0). Exporters can then + zap ptes by unmapping the corresponding range of the struct address_space + associated with their own file. + References: [1] struct dma_buf_ops in include/linux/dma-buf.h [2] All interfaces mentioned above defined in include/linux/dma-buf.h diff --git a/drivers/base/dma-buf.c b/drivers/base/dma-buf.c index 07cbbc6..8a573b9 100644 --- a/drivers/base/dma-buf.c +++ b/drivers/base/dma-buf.c @@ -44,8 +44,26 @@ static int dma_buf_release(struct inode *inode, struct file *file) return 0; } +static int dma_buf_mmap_internal(struct file *file, struct vm_area_struct *vma) +{ + struct dma_buf *dmabuf; + + if (!is_dma_buf_file(file)) + return -EINVAL; + + /* check for overflowing the buffer's size */ + if (vma->vm_pgoff + ((vma->vm_end - vma->vm_start) >> PAGE_SHIFT) > + dmabuf->size >> PAGE_SHIFT) + return -EINVAL; + + dmabuf = file->private_data; + + return dmabuf->ops->mmap(dmabuf, vma); +} + static const struct file_operations dma_buf_fops = { .release = dma_buf_release, + .mmap = dma_buf_mmap_internal, }; /* @@ -82,7 +100,8 @@ struct dma_buf *dma_buf_export(void *priv, const struct dma_buf_ops *ops, || !ops->unmap_dma_buf || !ops->release || !ops->kmap_atomic - || !ops->kmap)) { + || !ops->kmap + || !ops->mmap)) { return ERR_PTR(-EINVAL); } @@ -406,3 +425,46 @@ void dma_buf_kunmap(struct dma_buf *dmabuf, unsigned long page_num, dmabuf->ops->kunmap(dmabuf, page_num, vaddr); } EXPORT_SYMBOL_GPL(dma_buf_kunmap); + + +/** + * dma_buf_mmap - Setup up a userspace mmap with the given vma + * @dma_buf: [in] buffer that should back the vma + * @vma: [in] vma for the mmap + * @pgoff: [in] offset in pages where this mmap should start within the + * dma-buf buffer. + * + * This function adjusts the passed in vma so that it points at the file of the + * dma_buf operation. It alsog adjusts the starting pgoff and does bounds + * checking on the size of the vma. Then it calls the exporters mmap function to + * set up the mapping. + * + * Can return negative error values, returns 0 on success. + */ +int dma_buf_mmap(struct dma_buf *dmabuf, struct vm_area_struct *vma, + unsigned long pgoff) +{ + if (WARN_ON(!dmabuf || !vma)) + return -EINVAL; + + /* check for offset overflow */ + if (pgoff + ((vma->vm_end - vma->vm_start) >> PAGE_SHIFT) < pgoff) + return -EOVERFLOW; + + /* check for overflowing the buffer's size */ + if (pgoff + ((vma->vm_end - vma->vm_start) >> PAGE_SHIFT) > + dmabuf->size >> PAGE_SHIFT) + return -EINVAL; + + /* readjust the vma */ + if (vma->vm_file) + fput(vma->vm_file); + + vma->vm_file = dmabuf->file; + get_file(vma->vm_file); + + vma->vm_pgoff = pgoff; + + return dmabuf->ops->mmap(dmabuf, vma); +} +EXPORT_SYMBOL_GPL(dma_buf_mmap); diff --git a/include/linux/dma-buf.h b/include/linux/dma-buf.h index 3efbfc2..1f78d15 100644 --- a/include/linux/dma-buf.h +++ b/include/linux/dma-buf.h @@ -61,6 +61,10 @@ struct dma_buf_attachment; * This Callback must not sleep. * @kmap: maps a page from the buffer into kernel address space. * @kunmap: [optional] unmaps a page from the buffer. + * @mmap: used to expose the backing storage to userspace. Note that the + * mapping needs to be coherent - if the exporter doesn't directly + * support this, it needs to fake coherency by shooting down any ptes + * when transitioning away from the cpu domain. */ struct dma_buf_ops { int (*attach)(struct dma_buf *, struct device *, @@ -92,6 +96,8 @@ struct dma_buf_ops { void (*kunmap_atomic)(struct dma_buf *, unsigned long, void *); void *(*kmap)(struct dma_buf *, unsigned long); void (*kunmap)(struct dma_buf *, unsigned long, void *); + + int (*mmap)(struct dma_buf *, struct vm_area_struct *vma); }; /** @@ -167,6 +173,9 @@ void *dma_buf_kmap_atomic(struct dma_buf *, unsigned long); void dma_buf_kunmap_atomic(struct dma_buf *, unsigned long, void *); void *dma_buf_kmap(struct dma_buf *, unsigned long); void dma_buf_kunmap(struct dma_buf *, unsigned long, void *); + +int dma_buf_mmap(struct dma_buf *, struct vm_area_struct *, + unsigned long); #else static inline struct dma_buf_attachment *dma_buf_attach(struct dma_buf *dmabuf, @@ -248,6 +257,13 @@ static inline void dma_buf_kunmap(struct dma_buf *dmabuf, unsigned long pnum, void *vaddr) { } + +static inline int dma_buf_mmap(struct dma_buf *dmabuf, + struct vm_area_struct *vma, + unsigned long pgoff) +{ + return -ENODEV; +} #endif /* CONFIG_DMA_SHARED_BUFFER */ #endif /* __DMA_BUF_H__ */ -- 1.7.10

13 years, 7 months

6
5
0 0

[PATCH 0/4] ARM: replace custom consistent dma region with vmalloc

by Marek Szyprowski

Hi! Recent changes to ioremap and unification of vmalloc regions on ARM significantly reduces the possible size of the consistent dma region and limited allowed dma coherent/writecombine allocations. This experimental patch series replaces custom consistent dma regions usage in dma-mapping framework in favour of generic vmalloc areas created on demand for each coherent and writecombine allocations. This patch is based on vanilla v3.4-rc2 release. Best regards Marek Szyprowski Samsung Poland R&D Center Patch summary: Marek Szyprowski (4): mm: vmalloc: use const void * for caller argument mm: vmalloc: export find_vm_area() function mm: vmalloc: add VM_DMA flag to indicate areas used by dma-mapping framework ARM: remove consistent dma region and use common vmalloc range for dma allocations arch/arm/include/asm/dma-mapping.h | 2 +- arch/arm/mm/dma-mapping.c | 220 +++++++----------------------------- include/linux/vmalloc.h | 10 +- mm/vmalloc.c | 31 ++++-- 4 files changed, 67 insertions(+), 196 deletions(-) -- 1.7.1.569.g6f426

13 years, 7 months

6
9
0 0

Re: [Linaro-mm-sig] [PATCH 1/1] arm/dts: Tegra30: Add device tree support for SMMU

by Hiroshi Doyu

From: Thierry Reding <thierry.reding(a)avionic-design.de> Subject: Re: [PATCH 1/1] arm/dts: Tegra30: Add device tree support for SMMU Date: Wed, 18 Apr 2012 07:41:40 +0200 Message-ID: <20120418054140.GA17506(a)avionic-0098.adnet.avionic-design.de> > * PGP Signed by an unknown key > > * Hiroshi Doyu wrote: > > On Mon, 16 Apr 2012 17:34:19 +0200 > > Arnd Bergmann <arnd(a)arndb.de> wrote: > > > > > On Monday 16 April 2012, Hiroshi Doyu wrote: > > > > What about using "dma-window" property to specify IOVA range in dtsi as below? > > > > > > > > arch/powerpc/platforms/cell/iommu.c: > > > > > > > > 698 static int __init cell_iommu_get_window(struct device_node *np, > > > > 699 unsigned long *base, > > > > 700 unsigned long *size) > > > > 701 { > > > > 702 const void *dma_window; > > > > 703 unsigned long index; > > > > 704 > > > > 705 /* Use ibm,dma-window if available, else, hard code ! */ > > > > 706 dma_window = of_get_property(np, "ibm,dma-window", NULL); > > > > 707 if (dma_window == NULL) { ^^^^^^^^^^^^^^ > > > > 708 *base = 0; > > > > 709 *size = 0x80000000u; > > > > 710 return -ENODEV; > > > > 711 } > > > > 712 > > > > 713 of_parse_dma_window(np, dma_window, &index, base, size); > > > > 714 return 0; > > > > 715 } > > > > > > > > > > Yes, that's the right way to do it, but I would use the more generic > > > "dma-window" name rather than "ibm,dma-window", which was originally > > > introduced for pseries and for some reason copied into the cell qs2x > > > firmware. > > > > Which name is better, "dma-window" or "iova-window"? > > Considering DMA IOMMU mapping API, "dma-window" may sound appropriate to me. > > But the window isn't necessarily used for DMA transfers. I was going to > propose "aperture", but that doesn't seem quite right since it is a very > GART-specific term. "iova-window" sounds like the best fit for what it > really is. If we can consider IOMMU as one of the implementation of DMA(Direct Memory Access), the prefix "dma-(window)" may make sense here. Then, we don't have to introduce a new concept "IO virtual address(iova)" in addition to the existing "bus address"(?) Anyway, either name would be ok for me;)

13 years, 7 months

4
14
0 0

[PATCH v4 00/14] Integration of videobuf2 with dmabuf

by Tomasz Stanislawski

Hello everyone, This patchset adds support for DMABUF [2] importing to V4L2 stack. The support for DMABUF exporting was moved to separate patchset due to dependency on patches for DMA mapping redesign by Marek Szyprowski [4]. v4: - rebased on mainline 3.4-rc2 - included missing importing support for s5p-fimc and s5p-tv - added patch for changing map/unmap for importers - fixes to Documentation part - coding style fixes - pairing {map/unmap}_dmabuf in vb2-core - fixing variable types and semantic of arguments in videobufb2-dma-contig.c v3: - rebased on mainline 3.4-rc1 - split 'code refactor' patch to multiple smaller patches - squashed fixes to Sumit's patches - patchset is no longer dependant on 'DMA mapping redesign' - separated path for handling IO and non-IO mappings - add documentation for DMABUF importing to V4L - removed all DMABUF exporter related code - removed usage of dma_get_pages extension v2: - extended VIDIOC_EXPBUF argument from integer memoffset to struct v4l2_exportbuffer - added patch that breaks DMABUF spec on (un)map_atachment callcacks but allows to work with existing implementation of DMABUF prime in DRM - all dma-contig code refactoring patches were squashed - bugfixes v1: List of changes since [1]. - support for DMA api extension dma_get_pages, the function is used to retrieve pages used to create DMA mapping. - small fixes/code cleanup to videobuf2 - added prepare and finish callbacks to vb2 allocators, it is used keep consistency between dma-cpu acess to the memory (by Marek Szyprowski) - support for exporting of DMABUF buffer in V4L2 and Videobuf2, originated from [3]. - support for dma-buf exporting in vb2-dma-contig allocator - support for DMABUF for s5p-tv and s5p-fimc (capture interface) drivers, originated from [3] - changed handling for userptr buffers (by Marek Szyprowski, Andrzej Pietrasiewicz) - let mmap method to use dma_mmap_writecombine call (by Marek Szyprowski) [1] http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/4296… [2] https://lkml.org/lkml/2011/12/26/29 [3] http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/3635… [4] http://thread.gmane.org/gmane.linux.kernel.cross-arch/12819 Andrzej Pietrasiewicz (1): v4l: vb2-dma-contig: add support for scatterlist in userptr mode Laurent Pinchart (2): v4l: vb2-dma-contig: Shorten vb2_dma_contig prefix to vb2_dc v4l: vb2-dma-contig: Reorder functions Marek Szyprowski (2): v4l: vb2: add prepare/finish callbacks to allocators v4l: vb2-dma-contig: add prepare/finish to dma-contig allocator Sumit Semwal (4): v4l: Add DMABUF as a memory type v4l: vb2: add support for shared buffer (dma_buf) v4l: vb: remove warnings about MEMORY_DMABUF v4l: vb2-dma-contig: add support for dma_buf importing Tomasz Stanislawski (5): Documentation: media: description of DMABUF importing in V4L2 v4l: vb2-dma-contig: Remove unneeded allocation context structure v4l: vb2-dma-contig: change map/unmap behaviour for importers v4l: s5p-tv: mixer: support for dmabuf importing v4l: fimc: support for dmabuf importing Documentation/DocBook/media/v4l/compat.xml | 4 + Documentation/DocBook/media/v4l/io.xml | 179 +++++++ .../DocBook/media/v4l/vidioc-create-bufs.xml | 1 + Documentation/DocBook/media/v4l/vidioc-qbuf.xml | 15 + Documentation/DocBook/media/v4l/vidioc-reqbufs.xml | 47 +- drivers/media/video/Kconfig | 1 + drivers/media/video/s5p-fimc/fimc-capture.c | 2 +- drivers/media/video/s5p-tv/Kconfig | 1 + drivers/media/video/s5p-tv/mixer_video.c | 2 +- drivers/media/video/videobuf-core.c | 4 + drivers/media/video/videobuf2-core.c | 207 +++++++- drivers/media/video/videobuf2-dma-contig.c | 553 +++++++++++++++++--- include/linux/videodev2.h | 7 + include/media/videobuf2-core.h | 34 ++ 14 files changed, 956 insertions(+), 101 deletions(-) -- 1.7.5.4

13 years, 7 months

6
38
0 0

[PATCH] WIP: staging: drm/omap: dmabuf/prime mmap support

by Rob Clark

From: Rob Clark <rob(a)ti.com> There are still a few places to cleanup, and possibly things can be made a bit easier for individual drm drivers by some helpers in drm core. But this is enough for a proof of concept. With this, I can allocate cached buffers, fill them w/ software from userspace, and on kernel side with fault handling and PTE shootdown track which pages must be flushed to simulate coherency. Fyi, you can find my kernel branch, with this patch on top of Daniel's dmabuf mmap patch, here: https://github.com/robclark/kernel-omap4/commits/dmabuf/mmap --- drivers/staging/omapdrm/omap_drv.h | 4 + drivers/staging/omapdrm/omap_fb.c | 6 +- drivers/staging/omapdrm/omap_gem.c | 99 ++++++++++++++++++++++++++--- drivers/staging/omapdrm/omap_gem_dmabuf.c | 45 +++++++++++++ 4 files changed, 142 insertions(+), 12 deletions(-) diff --git a/drivers/staging/omapdrm/omap_drv.h b/drivers/staging/omapdrm/omap_drv.h index 2b41152..5812e20 100644 --- a/drivers/staging/omapdrm/omap_drv.h +++ b/drivers/staging/omapdrm/omap_drv.h @@ -138,6 +138,8 @@ int omap_gem_dumb_destroy(struct drm_file *file, struct drm_device *dev, int omap_gem_dumb_create(struct drm_file *file, struct drm_device *dev, struct drm_mode_create_dumb *args); int omap_gem_mmap(struct file *filp, struct vm_area_struct *vma); +int omap_gem_mmap_obj(struct drm_gem_object *obj, + struct vm_area_struct *vma); int omap_gem_fault(struct vm_area_struct *vma, struct vm_fault *vmf); int omap_gem_op_start(struct drm_gem_object *obj, enum omap_gem_op op); int omap_gem_op_finish(struct drm_gem_object *obj, enum omap_gem_op op); @@ -145,6 +147,8 @@ int omap_gem_op_sync(struct drm_gem_object *obj, enum omap_gem_op op); int omap_gem_op_async(struct drm_gem_object *obj, enum omap_gem_op op, void (*fxn)(void *arg), void *arg); int omap_gem_roll(struct drm_gem_object *obj, uint32_t roll); +int omap_gem_dma_sync(struct drm_gem_object *obj, + enum dma_data_direction dir); int omap_gem_get_paddr(struct drm_gem_object *obj, dma_addr_t *paddr, bool remap); int omap_gem_put_paddr(struct drm_gem_object *obj); diff --git a/drivers/staging/omapdrm/omap_fb.c b/drivers/staging/omapdrm/omap_fb.c index 04b235b..ac32b3d 100644 --- a/drivers/staging/omapdrm/omap_fb.c +++ b/drivers/staging/omapdrm/omap_fb.c @@ -197,8 +197,10 @@ int omap_framebuffer_replace(struct drm_framebuffer *a, pa->paddr = 0; } - if (pb && !ret) - ret = omap_gem_get_paddr(pb->bo, &pb->paddr, true); + if (pb && !ret) { + ret = omap_gem_get_paddr(pb->bo, &pb->paddr, true) || + omap_gem_dma_sync(pb->bo, DMA_TO_DEVICE); + } } if (ret) { diff --git a/drivers/staging/omapdrm/omap_gem.c b/drivers/staging/omapdrm/omap_gem.c index c5ba334..be7f6c0 100644 --- a/drivers/staging/omapdrm/omap_gem.c +++ b/drivers/staging/omapdrm/omap_gem.c @@ -212,8 +212,11 @@ static DEFINE_SPINLOCK(sync_lock); /** ensure backing pages are allocated */ static int omap_gem_attach_pages(struct drm_gem_object *obj) { + struct drm_device *dev = obj->dev; struct omap_gem_object *omap_obj = to_omap_bo(obj); struct page **pages; + int i, npages = obj->size >> PAGE_SHIFT; + dma_addr_t *addrs; WARN_ON(omap_obj->pages); @@ -231,16 +234,18 @@ static int omap_gem_attach_pages(struct drm_gem_object *obj) * DSS, GPU, etc. are not cache coherent: */ if (omap_obj->flags & (OMAP_BO_WC|OMAP_BO_UNCACHED)) { - int i, npages = obj->size >> PAGE_SHIFT; - dma_addr_t *addrs = kmalloc(npages * sizeof(addrs), GFP_KERNEL); + addrs = kmalloc(npages * sizeof(addrs), GFP_KERNEL); for (i = 0; i < npages; i++) { - addrs[i] = dma_map_page(obj->dev->dev, pages[i], + addrs[i] = dma_map_page(dev->dev, pages[i], 0, PAGE_SIZE, DMA_BIDIRECTIONAL); } - omap_obj->addrs = addrs; + } else { + addrs = kzalloc(npages * sizeof(addrs), GFP_KERNEL); } + omap_obj->addrs = addrs; omap_obj->pages = pages; + return 0; } @@ -258,10 +263,11 @@ static void omap_gem_detach_pages(struct drm_gem_object *obj) dma_unmap_page(obj->dev->dev, omap_obj->addrs[i], PAGE_SIZE, DMA_BIDIRECTIONAL); } - kfree(omap_obj->addrs); - omap_obj->addrs = NULL; } + kfree(omap_obj->addrs); + omap_obj->addrs = NULL; + _drm_gem_put_pages(obj, omap_obj->pages, true, false); omap_obj->pages = NULL; } @@ -336,6 +342,13 @@ static int fault_1d(struct drm_gem_object *obj, vma->vm_start) >> PAGE_SHIFT; if (omap_obj->pages) { + if ((omap_obj->flags & OMAP_BO_CACHE_MASK) == OMAP_BO_CACHED) { + if (omap_obj->addrs[pgoff]) { + dma_unmap_page(obj->dev->dev, omap_obj->addrs[pgoff], + PAGE_SIZE, DMA_BIDIRECTIONAL); + omap_obj->addrs[pgoff] = 0; + } + } pfn = page_to_pfn(omap_obj->pages[pgoff]); } else { BUG_ON(!(omap_obj->flags & OMAP_BO_DMA)); @@ -510,7 +523,6 @@ fail: /** We override mainly to fix up some of the vm mapping flags.. */ int omap_gem_mmap(struct file *filp, struct vm_area_struct *vma) { - struct omap_gem_object *omap_obj; int ret; ret = drm_gem_mmap(filp, vma); @@ -519,8 +531,14 @@ int omap_gem_mmap(struct file *filp, struct vm_area_struct *vma) return ret; } - /* after drm_gem_mmap(), it is safe to access the obj */ - omap_obj = to_omap_bo(vma->vm_private_data); + return omap_gem_mmap_obj(vma->vm_private_data, vma); +} + + +int omap_gem_mmap_obj(struct drm_gem_object *obj, + struct vm_area_struct *vma) +{ + struct omap_gem_object *omap_obj = to_omap_bo(obj); vma->vm_flags &= ~VM_PFNMAP; vma->vm_flags |= VM_MIXEDMAP; @@ -530,12 +548,34 @@ int omap_gem_mmap(struct file *filp, struct vm_area_struct *vma) } else if (omap_obj->flags & OMAP_BO_UNCACHED) { vma->vm_page_prot = pgprot_noncached(vm_get_page_prot(vma->vm_flags)); } else { + /* + * We do have some private objects, at least for scanout buffers + * on hardware without DMM/TILER. But these are allocated write- + * combine + */ + if (WARN_ON(!obj->filp)) + return -EINVAL; + + // TODO quick hack to avoid needing to re-invent my own vmops: + WARN_ON(obj->filp->private_data); + obj->filp->private_data = vma->vm_file->private_data; + fput(vma->vm_file); + get_file(obj->filp); + + /* + * Shunt off cached objs to shmem file so they have their own + * address_space (so unmap_mapping_range does what we want) + */ + vma->vm_pgoff = 0; + vma->vm_file = obj->filp; + vma->vm_page_prot = vm_get_page_prot(vma->vm_flags); } - return ret; + return 0; } + /** * omap_gem_dumb_create - create a dumb buffer * @drm_file: our client file @@ -645,6 +685,44 @@ fail: return ret; } +int omap_gem_dma_sync(struct drm_gem_object *obj, + enum dma_data_direction dir) +{ + struct drm_device *dev = obj->dev; + struct omap_gem_object *omap_obj = to_omap_bo(obj); + int ret = 0; + + // TODO not sure if I want this to be automagic or new flag set + // when allocating buffer (or maybe instead a flag to explictly + // disable? + + if ((omap_obj->flags & OMAP_BO_CACHE_MASK) == OMAP_BO_CACHED) { + int i, npages = obj->size >> PAGE_SHIFT; + struct page **pages = omap_obj->pages; + bool dirty = false; + + if (WARN_ON(!obj->filp)) + return -EINVAL; + + for (i = 0; i < npages; i++) { + if (!omap_obj->addrs[i]) { + // TODO using BIDIRECTIONAL for now because in the + // fault handler we don't really know the direction.. + omap_obj->addrs[i] = dma_map_page(dev->dev, pages[i], 0, + PAGE_SIZE, DMA_BIDIRECTIONAL); + dirty = true; + } + } + + if (dirty) { + unmap_mapping_range(obj->filp->f_mapping, 0, + omap_gem_mmap_size(obj), 1); + } + } + + return ret; +} + /* Get physical address for DMA.. if 'remap' is true, and the buffer is not * already contiguous, remap it to pin in physically contiguous memory.. (ie. * map in TILER) @@ -709,6 +787,7 @@ int omap_gem_get_paddr(struct drm_gem_object *obj, *paddr = omap_obj->paddr; } else { ret = -EINVAL; + goto fail; } fail: diff --git a/drivers/staging/omapdrm/omap_gem_dmabuf.c b/drivers/staging/omapdrm/omap_gem_dmabuf.c index 2fa39e8..85a0b1c 100644 --- a/drivers/staging/omapdrm/omap_gem_dmabuf.c +++ b/drivers/staging/omapdrm/omap_gem_dmabuf.c @@ -34,6 +34,8 @@ static struct sg_table *omap_gem_map_dma_buf( if (!sg) return ERR_PTR(-ENOMEM); + omap_gem_dma_sync(obj, dir); + /* camera, etc, need physically contiguous.. but we need a * better way to know this.. */ @@ -131,6 +133,48 @@ static void omap_gem_dmabuf_kunmap(struct dma_buf *buffer, kunmap(pages[page_num]); } +/* TODO: perhaps this could be a helper: */ +static int omap_gem_dmabuf_mmap(struct dma_buf *buffer, + struct vm_area_struct *vma) +{ + struct drm_gem_object *obj = buffer->priv; + int ret = 0; + + if (WARN_ON(!obj->filp)) + return -EINVAL; + + // TODO maybe we can split up drm_gem_mmap to avoid duplicating + // some here.. or at least have a drm_dmabuf helper.. + + /* Check for valid size. */ + if (omap_gem_mmap_size(obj) < vma->vm_end - vma->vm_start) { + ret = -EINVAL; + goto out_unlock; + } + + if (!obj->dev->driver->gem_vm_ops) { + ret = -EINVAL; + goto out_unlock; + } + + vma->vm_flags |= VM_RESERVED | VM_IO | VM_PFNMAP | VM_DONTEXPAND; + vma->vm_ops = obj->dev->driver->gem_vm_ops; + vma->vm_private_data = obj; + vma->vm_page_prot = pgprot_writecombine(vm_get_page_prot(vma->vm_flags)); + + /* Take a ref for this mapping of the object, so that the fault + * handler can dereference the mmap offset's pointer to the object. + * This reference is cleaned up by the corresponding vm_close + * (which should happen whether the vma was created by this call, or + * by a vm_open due to mremap or partial unmap or whatever). + */ + vma->vm_ops->open(vma); + +out_unlock: + + return omap_gem_mmap_obj(obj, vma); +} + struct dma_buf_ops omap_dmabuf_ops = { .map_dma_buf = omap_gem_map_dma_buf, .unmap_dma_buf = omap_gem_unmap_dma_buf, @@ -141,6 +185,7 @@ struct dma_buf_ops omap_dmabuf_ops = { .kunmap_atomic = omap_gem_dmabuf_kunmap_atomic, .kmap = omap_gem_dmabuf_kmap, .kunmap = omap_gem_dmabuf_kunmap, + .mmap = omap_gem_dmabuf_mmap, }; struct dma_buf * omap_gem_prime_export(struct drm_device *dev, -- 1.7.9.1

13 years, 8 months

1
0
0 0

[PATCHv8 00/10] ARM: DMA-mapping framework redesign

by Marek Szyprowski

Hello, Linux v3.4-rc2, which include dma-mapping preparation patches, has been released two days ago, now it's time for the next spin of ARM dma-mapping redesign patches. This version includes various fixes posted separately to v7, mainly related to incorrect io address space bitmap setup and a major issue with broken mmap for memory which comes from dma_declare_coherent(). The patches have been also rebased onto Linux v3.4-rc2 which comes with dma_map_ops related changes. The code has been tested on Samsung Exynos4 'UniversalC210' and NURI boards with IOMMU driver posted by KyongHo Cho, I will put separate branch which shows how to integrate this driver with this patchset. The patches are also available on my git repository at: git://git.linaro.org/people/mszyprowski/linux-dma-mapping.git 3.4-rc2-arm-dma-v8 History of the development: v1: (initial version of the DMA-mapping redesign patches): http://www.spinics.net/lists/linux-mm/msg21241.html v2: http://lists.linaro.org/pipermail/linaro-mm-sig/2011-September/000571.html http://lists.linaro.org/pipermail/linaro-mm-sig/2011-September/000577.html v3: http://www.spinics.net/lists/linux-mm/msg25490.html v4 and v5: http://www.spinics.net/lists/arm-kernel/msg151147.html http://www.spinics.net/lists/arm-kernel/msg154889.html v6: http://www.spinics.net/lists/linux-mm/msg29903.html v7: http://www.spinics.net/lists/arm-kernel/msg162149.html Best regards Marek Szyprowski Samsung Poland R&D Center Patch summary: Marek Szyprowski (10): common: add dma_mmap_from_coherent() function ARM: dma-mapping: use pr_* instread of printk ARM: dma-mapping: introduce ARM_DMA_ERROR constant ARM: dma-mapping: remove offset parameter to prepare for generic dma_ops ARM: dma-mapping: use asm-generic/dma-mapping-common.h ARM: dma-mapping: implement dma sg methods on top of any generic dma ops ARM: dma-mapping: move all dma bounce code to separate dma ops structure ARM: dma-mapping: remove redundant code and cleanup ARM: dma-mapping: use alloc, mmap, free from dma_ops ARM: dma-mapping: add support for IOMMU mapper arch/arm/Kconfig | 9 + arch/arm/common/dmabounce.c | 84 +++- arch/arm/include/asm/device.h | 4 + arch/arm/include/asm/dma-iommu.h | 34 ++ arch/arm/include/asm/dma-mapping.h | 407 ++++----------- arch/arm/mm/dma-mapping.c | 1019 ++++++++++++++++++++++++++++++------ arch/arm/mm/vmregion.h | 2 +- drivers/base/dma-coherent.c | 42 ++ include/asm-generic/dma-coherent.h | 4 +- 9 files changed, 1138 insertions(+), 467 deletions(-) create mode 100644 arch/arm/include/asm/dma-iommu.h -- 1.7.1.569.g6f426

13 years, 8 months

3
28
0 0

[PATCH 00/11] Integration of videobuf2 with dmabuf

by Tomasz Stanislawski

Hello everyone, This patchset adds support for DMABUF [2] importing to V4L2 stack. It was updated after Laurent Pinchart's review. The support for DMABUF exporting was moved to separate patchset due to dependency on patches for DMA mapping redesign by Marek Szyprowski [4]. v3: - rebased on mainline 3.4-rc1 - split 'code refactor' patch to multiple smaller patches - squashed fixes to Sumit's patches - patchset is no longer dependant on 'DMA mapping redesign' - separated path for handling IO and non-IO mappings - add documentation for DMABUF importing to V4L - removed all DMABUF exporter related code - removed usage of dma_get_pages extension v2: - extended VIDIOC_EXPBUF argument from integer memoffset to struct v4l2_exportbuffer - added patch that breaks DMABUF spec on (un)map_atachment callcacks but allows to work with existing implementation of DMABUF prime in DRM - all dma-contig code refactoring patches were squashed - bugfixes v1: List of changes since [1]. - support for DMA api extension dma_get_pages, the function is used to retrieve pages used to create DMA mapping. - small fixes/code cleanup to videobuf2 - added prepare and finish callbacks to vb2 allocators, it is used keep consistency between dma-cpu acess to the memory (by Marek Szyprowski) - support for exporting of DMABUF buffer in V4L2 and Videobuf2, originated from [3]. - support for dma-buf exporting in vb2-dma-contig allocator - support for DMABUF for s5p-tv and s5p-fimc (capture interface) drivers, originated from [3] - changed handling for userptr buffers (by Marek Szyprowski, Andrzej Pietrasiewicz) - let mmap method to use dma_mmap_writecombine call (by Marek Szyprowski) [1] http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/4296… [2] https://lkml.org/lkml/2011/12/26/29 [3] http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/3635… [4] http://thread.gmane.org/gmane.linux.kernel.cross-arch/12819 Andrzej Pietrasiewicz (1): v4l: vb2-dma-contig: add support for scatterlist in userptr mode Laurent Pinchart (2): v4l: vb2-dma-contig: Shorten vb2_dma_contig prefix to vb2_dc v4l: vb2-dma-contig: Reorder functions Marek Szyprowski (2): v4l: vb2: add prepare/finish callbacks to allocators v4l: vb2-dma-contig: add prepare/finish to dma-contig allocator Sumit Semwal (4): v4l: Add DMABUF as a memory type v4l: vb2: add support for shared buffer (dma_buf) v4l: vb: remove warnings about MEMORY_DMABUF v4l: vb2: Add dma-contig allocator as dma_buf user Tomasz Stanislawski (2): Documentation: media: description of DMABUF importing in V4L2 v4l: vb2-dma-contig: Remove unneeded allocation context structure Documentation/DocBook/media/v4l/compat.xml | 4 + Documentation/DocBook/media/v4l/io.xml | 177 +++++++ .../DocBook/media/v4l/vidioc-create-bufs.xml | 1 + Documentation/DocBook/media/v4l/vidioc-qbuf.xml | 15 + Documentation/DocBook/media/v4l/vidioc-reqbufs.xml | 8 +- drivers/media/video/videobuf-core.c | 4 + drivers/media/video/videobuf2-core.c | 195 +++++++- drivers/media/video/videobuf2-dma-contig.c | 536 +++++++++++++++++--- include/linux/videodev2.h | 8 + include/media/videobuf2-core.h | 38 ++ 10 files changed, 910 insertions(+), 76 deletions(-) -- 1.7.5.4

13 years, 8 months

4
25
0 0

overlay UI layer of ICS supports by preserved memory allocation in virtualized environment

by Kwang Sik Shin

I'm interested in CMA scheme or preserved memory allocation of ION (ION_HEAP_TYPE_CARVEOUT heap type) I knew many SoC vendors (TI, nvidia, qualcom) already used similar approaches for multimedia processing in the past. However, reservation of physical memory should waste memory and limit available system memory, so now they use an IOMMU to support a contiguous virtual address region. In addition to, ICS (Ice Cream Sandwitch) support overlay UI layer requiring lots of contiguous memory allocation area. Now I'm suggesting an idea to use lots of contiguous memory allocation area without IOMMU. So ION_HEAP_TYPE_CARVEOUT heap type of ION is one of my considerations, but you know that it might exhaust much physical memory. However, I think physical memory wasting problem can be solved in the virtualized system. In case of virtualized environment, physical memory is intermediate physical memory instead of real physical memory, so a preserved carveout heap does not exhaust real physical memory any more. In addition to, if virtual address and intermediate physical address are 32 and 40bits respectively, virtual memory is not exhausted neither. How do you think about my suggestion?

13 years, 8 months

2
1
0 0

[PATCH 0/4] [RFC] Addition of dma-mapping IOMMU framework in Exynos DRM

by Prathyush

From: Prathyush K <prathyush.k(a)samsung.com> With these set of patches, the Exynos5 DRM module will be able to allocate, export and map non-contiguous memory for GEM objects using the dma-mapping IOMMU framework. These patches are based on the following references: 1> Exynos 5 SYSMMU driver by Kyongho Cho http://lists.infradead.org/pipermail/linux-arm-kernel/2011-December/078636.… 2> DMA-MAPPING IOMMU framework by Marek Szyprowski http://lists.infradead.org/pipermail/linux-arm-kernel/2011-June/053636.html 3> DRM-PRIME by Dave Airlie http://patches.linaro.org/7480/ 4> DRM Exynos DMABUF module by Inki Dae http://git.infradead.org/users/kmpark/linux-2.6-samsung/commit/ d59d3e521d8a9d27e7b329f89f24a8473f32f50c/ 5> Support for dma_get_pages by Tomasz Stanislawski http://patchwork.linuxtv.org/patch/9639/ The updated GEM framework by Inki Dae is not considered for this patch set. IOMMU mapping is created for exynos-drm-device initially. Allocation of GEM objects happens through dma_alloc_writecombine which inturn calls arm_iommu_alloc_attrs. This will allocate a non-contig set of pages, allocate a iova and map all the pages. The following changes are done to support non-contiguous memory for GEM objects [PATCH 1/4]: drm/exynos: DMABUF: Added support for exporting non-contig buffers. This patch is for creating and mapping a SGT in map_dma_buf by retrieving the pages by calling dma_get_pages. [PATCH 2/4]: drm/exynos: Mapping of gem objects uses dma_mmap_writecombine. This patch is for mapping the non-contiguous GEM objects to user space by calling dma_mmap_writecombine. [PATCH 3/4]: drm/Exynos: Added 'disable' function to Exynos drm crtc module. This patch is required for safe release of DRM. If a FB of a CRTC is released, the driver tries to disable the CRTC if that is supported by the CRTC. This patch adds Exynos DRM CRTC disable functionality. [PATCH 4/4]: drm: Releasing FBs before releasing GEM objects during drm_release. This patch is required for safe release of DRM. During drm release, all the FBs and GEM objects are released. A gem object which is used as a FB must not be freed first before releasing the FB. This patch modifies the drm release function to first release the FBs and then release the GEMs. drivers/gpu/drm/drm_fops.c | 6 +- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 11 +++ drivers/gpu/drm/exynos/exynos_drm_dmabuf.c | 98 +++++++++++++++++++++++----- drivers/gpu/drm/exynos/exynos_drm_gem.c | 70 +++++++++----------- 4 files changed, 128 insertions(+), 57 deletions(-)

13 years, 8 months

4
9
0 0

[PATCH/RFC] ARM: Exynos4: Integrate IOMMU aware DMA-mapping

by Marek Szyprowski

Hi! This is an example of the IOMMU aware DMA-mapping implementation usage on a Samsung Exynos4 based NURI board. The ARM DMA-mapping IOMMU aware implementation is available in the [1] thread: This patch essentially registers DMA-mmaping/IOMMU support for FIMC and MFC devices and performs some tweaks in clocks hierarchy to get SYSMMU driver working correctly. The drivers have been tested with mainline V4L2 drivers for FIMC and MFC hardware. For easier testing I've created a separate kernel branch with all required prerequisite patches. It is based on lastest kgene/for-next branch and is available on my git repository: git://git.linaro.org/people/mszyprowski/linux-dma-mapping.git 3.4-rc2-arm-dma-v8-samsung This patch requires the following items: 1. ARM DMA-mapping patches [1] 2. Exynos SYSMMU driver v12 [2] 3. Exynos SYSMMU driver runtime pm fixes 4. Exynos4 gen_pd power domain driver fixes Runtime pm and power domain patches are required on Samsung Nuri board, but might be optional on boards where bootloader doesn't disable all devices on boot. [1] http://www.spinics.net/lists/linux-arch/msg17331.html [2] https://lkml.org/lkml/2012/3/15/51 Best regards Marek Szyprowski Samsung Poland R&D Center Patch summary: Marek Szyprowski (1): ARM: Exynos4: integrate SYSMMU driver with DMA-mapping interface arch/arm/mach-exynos/Kconfig | 1 + arch/arm/mach-exynos/clock-exynos4.c | 64 +++++++++++++++------------- arch/arm/mach-exynos/dev-sysmmu.c | 44 +++++++++++++++++++ arch/arm/mach-exynos/include/mach/sysmmu.h | 3 + drivers/iommu/Kconfig | 1 + 5 files changed, 84 insertions(+), 29 deletions(-) -- 1.7.1.569.g6f426

13 years, 8 months

4
6
0 0

Test application for DMABUF sharing between V4L2 and DRM

by Tomasz Stanislawski

Hi Everyone, This email contains a test application showing DMABUF sharing between DRM/KMS display and capture node including VIVI. It shows a simple preview on LCD display. The similar application was posted in thread: http://thread.gmane.org/gmane.comp.video.dri.devel/65997 This version makes use of single-plane API for V4L2 capture instead of multiplanar. This change allows VIVI driver to be tested as DMABUF importer. The program is written in C99 and it was tested using Exynos/DRM and VIVI capture. This application shows how buffer sharing between V4L2/DRM may look like. Please let me know if/where I use DRM/V4L2 incorrectly. The application was tested against 3.4-rc1 kernel with patches: - Integration of videobuf2 with dmabuf http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/46586 - Integration of vb2-vmalloc and VIVI with dmabuf http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/46713 - Support for DRM prime for Exynos by Inki Dae http://git.infradead.org/users/kmpark/linux-2.6-samsung/shortlog/refs/heads… - patch fixing kmap/vmap support for EXYNOS-DRM prime. http://git.infradead.org/users/kmpark/linux-2.6-samsung/commit/3c483f24e418… The branch containing all mentioned patches (without platform code) rebased on 3.4-rc1 is available at link: http://git.infradead.org/users/kmpark/linux-2.6-samsung/shortlog/refs/heads… Regards, Tomasz Stanislawski --- #include <errno.h> #include <fcntl.h> #include <linux/videodev2.h> #include <math.h> #include <poll.h> #include <stdio.h> #include <stdint.h> #include <stdlib.h> #include <string.h> #include <sys/ioctl.h> #include <sys/mman.h> #include <sys/stat.h> #include <sys/types.h> #include <unistd.h> #include <xf86drm.h> #include <xf86drmMode.h> #include <exynos_drm.h> #define ERRSTR strerror(errno) #define BYE_ON(cond, ...) \ do { \ if (cond) { \ int errsv = errno; \ fprintf(stderr, "ERROR(%s:%d) : ", \ __FILE__, __LINE__); \ errno = errsv; \ fprintf(stderr, __VA_ARGS__); \ abort(); \ } \ } while(0) static inline int warn(const char *file, int line, const char *fmt, ...) { int errsv = errno; va_list va; va_start(va, fmt); fprintf(stderr, "WARN(%s:%d): ", file, line); vfprintf(stderr, fmt, va); va_end(va); errno = errsv; return 1; } #define WARN_ON(cond, ...) \ ((cond) ? warn(__FILE__, __LINE__, __VA_ARGS__) : 0) struct setup { char module[32]; uint32_t conId; uint32_t crtId; char modestr[32]; char video[32]; unsigned int w, h; unsigned int use_wh : 1; unsigned int in_fourcc; unsigned int out_fourcc; unsigned int buffer_count; unsigned int use_crop : 1; unsigned int use_compose : 1; struct v4l2_rect crop; struct v4l2_rect compose; }; struct buffer { unsigned int bo_handle; unsigned int fb_handle; int dbuf_fd; }; struct stream { int v4lfd; int current_buffer; int buffer_count; struct buffer *buffer; } stream; static void usage(char *name) { fprintf(stderr, "usage: %s [-Moisth]\n", name); fprintf(stderr, "\t-M <drm-module>\tset DRM module\n"); fprintf(stderr, "\t-o <connector_id>:<crtc_id>:<mode>\tset a mode\n"); fprintf(stderr, "\t-i <video-node>\tset video node like /dev/video*\n"); fprintf(stderr, "\t-S <width,height>\tset input resolution\n"); fprintf(stderr, "\t-f <fourcc>\tset input format using 4cc\n"); fprintf(stderr, "\t-F <fourcc>\tset output format using 4cc\n"); fprintf(stderr, "\t-s <width,height>@<left,top>\tset crop area\n"); fprintf(stderr, "\t-t <width,height>@<left,top>\tset compose area\n"); fprintf(stderr, "\t-b buffer_count\tset number of buffers\n"); fprintf(stderr, "\t-h\tshow this help\n"); fprintf(stderr, "\n\tDefault is to dump all info.\n"); } static inline int parse_rect(char *s, struct v4l2_rect *r) { return sscanf(s, "%d,%d@%d,%d", &r->width, &r->height, &r->top, &r->left) != 4; } static int parse_args(int argc, char *argv[], struct setup *s) { if (argc <= 1) usage(argv[0]); int c, ret; memset(s, 0, sizeof(*s)); while ((c = getopt(argc, argv, "M:o:i:S:f:F:s:t:b:h")) != -1) { switch (c) { case 'M': strncpy(s->module, optarg, 31); break; case 'o': ret = sscanf(optarg, "%u:%u:%31s", &s->conId, &s->crtId, s->modestr); if (WARN_ON(ret != 3, "incorrect mode description\n")) return -1; break; case 'i': strncpy(s->video, optarg, 31); break; case 'S': ret = sscanf(optarg, "%u,%u", &s->w, &s->h); if (WARN_ON(ret != 2, "incorrect input size\n")) return -1; s->use_wh = 1; break; case 'f': if (WARN_ON(strlen(optarg) != 4, "invalid fourcc\n")) return -1; s->in_fourcc = ((unsigned)optarg[0] << 0) | ((unsigned)optarg[1] << 8) | ((unsigned)optarg[2] << 16) | ((unsigned)optarg[3] << 24); break; case 'F': if (WARN_ON(strlen(optarg) != 4, "invalid fourcc\n")) return -1; s->out_fourcc = ((unsigned)optarg[0] << 0) | ((unsigned)optarg[1] << 8) | ((unsigned)optarg[2] << 16) | ((unsigned)optarg[3] << 24); break; case 's': ret = parse_rect(optarg, &s->crop); if (WARN_ON(ret, "incorrect crop area\n")) return -1; s->use_crop = 1; break; case 't': ret = parse_rect(optarg, &s->compose); if (WARN_ON(ret, "incorrect compose area\n")) return -1; s->use_compose = 1; break; case 'b': ret = sscanf(optarg, "%u", &s->buffer_count); if (WARN_ON(ret != 1, "incorrect buffer count\n")) return -1; break; case '?': case 'h': usage(argv[0]); return -1; } } return 0; } static int buffer_create(struct buffer *b, int drmfd, struct setup *s, uint64_t size, uint32_t pitch) { int ret = strncmp(s->module, "exynos", 6); if (WARN_ON(ret, "drm: only exynos GEM is supported\n")) return -1; struct drm_exynos_gem_create gem; struct drm_gem_close gem_close; memset(&gem, 0, sizeof gem); gem.size = size; ret = ioctl(drmfd, DRM_IOCTL_EXYNOS_GEM_CREATE, &gem); if (WARN_ON(ret, "EXYNOS_GEM_CREATE failed: %s\n", ERRSTR)) return -1; b->bo_handle = gem.handle; struct drm_prime_handle prime; memset(&prime, 0, sizeof prime); prime.handle = b->bo_handle; ret = ioctl(drmfd, DRM_IOCTL_PRIME_HANDLE_TO_FD, &prime); if (WARN_ON(ret, "PRIME_HANDLE_TO_FD failed: %s\n", ERRSTR)) goto fail_gem; printf("dbuf_fd = %d\n", prime.fd); b->dbuf_fd = prime.fd; uint32_t offsets[4] = { 0 }; uint32_t pitches[4] = { pitch }; uint32_t bo_handles[4] = { b->bo_handle }; unsigned int fourcc = s->out_fourcc; if (!fourcc) fourcc = s->in_fourcc; ret = drmModeAddFB2(drmfd, s->w, s->h, fourcc, bo_handles, pitches, offsets, &b->fb_handle, 0); if (WARN_ON(ret, "drmModeAddFB2 failed: %s\n", ERRSTR)) goto fail_prime; return 0; fail_prime: close(b->dbuf_fd); fail_gem: memset(&gem_close, 0, sizeof gem_close); gem_close.handle = b->bo_handle, ret = ioctl(drmfd, DRM_IOCTL_GEM_CLOSE, gem_close); WARN_ON(ret, "GEM_CLOSE failed: %s\n", ERRSTR); return -1; } static int find_mode(drmModeModeInfo *m, int drmfd, struct setup *s, uint32_t *con) { int ret = -1; drmModeRes *res = drmModeGetResources(drmfd); if (WARN_ON(!res, "drmModeGetResources failed: %s\n", ERRSTR)) return -1; if (WARN_ON(res->count_crtcs <= 0, "drm: no crts\n")) goto fail_res; if (WARN_ON(res->count_connectors <= 0, "drm: no connectors\n")) goto fail_res; if (WARN_ON(s->conId >= res->count_connectors, "connector %d " "is not supported\n", s->conId)) goto fail_res; drmModeConnector *c; c = drmModeGetConnector(drmfd, res->connectors[s->conId]); if (WARN_ON(!c, "drmModeGetConnector failed: %s\n", ERRSTR)) goto fail_res; if (WARN_ON(!c->count_modes, "connector supports no mode\n")) goto fail_conn; drmModeModeInfo *found = NULL; for (int i = 0; i < c->count_modes; ++i) if (strcmp(c->modes[i].name, s->modestr) == 0) found = &c->modes[i]; if (WARN_ON(!found, "mode %s not supported\n", s->modestr)) { fprintf(stderr, "Valid modes:"); for (int i = 0; i < c->count_modes; ++i) fprintf(stderr, " %s", c->modes[i].name); fprintf(stderr, "\n"); goto fail_conn; } memcpy(m, found, sizeof *found); if (con) *con = c->connector_id; ret = 0; fail_conn: drmModeFreeConnector(c); fail_res: drmModeFreeResources(res); return ret; } static void page_flip_handler(int fd, unsigned int frame, unsigned int sec, unsigned int usec, void *data) { int index = stream.current_buffer; struct v4l2_buffer buf; int ret; stream.current_buffer = (int)data; if (index < 0) return; memset(&buf, 0, sizeof buf); buf.type = V4L2_BUF_TYPE_VIDEO_CAPTURE; buf.memory = V4L2_MEMORY_DMABUF; buf.index = index; buf.m.fd = stream.buffer[index].dbuf_fd; ret = ioctl(stream.v4lfd, VIDIOC_QBUF, &buf); BYE_ON(ret, "VIDIOC_QBUF(index = %d) failed: %s\n", index, ERRSTR); } int main(int argc, char *argv[]) { int ret; struct setup s; ret = parse_args(argc, argv, &s); BYE_ON(ret, "failed to parse arguments\n"); BYE_ON(s.module[0] == 0, "DRM module is missing\n"); BYE_ON(s.video[0] == 0, "video node is missing\n"); int drmfd = drmOpen(s.module, NULL); BYE_ON(drmfd < 0, "drmOpen(%s) failed: %s\n", s.module, ERRSTR); int v4lfd = open(s.video, O_RDWR); BYE_ON(v4lfd < 0, "failed to open %s: %s\n", s.video, ERRSTR); struct v4l2_capability caps; memset(&caps, 0, sizeof caps); ret = ioctl(v4lfd, VIDIOC_QUERYCAP, &caps); BYE_ON(ret, "VIDIOC_QUERYCAP failed: %s\n", ERRSTR); /* TODO: add single plane support */ BYE_ON(~caps.capabilities & V4L2_CAP_VIDEO_CAPTURE, "video: singleplanar capture is not supported\n"); struct v4l2_format fmt; memset(&fmt, 0, sizeof fmt); fmt.type = V4L2_BUF_TYPE_VIDEO_CAPTURE; ret = ioctl(v4lfd, VIDIOC_G_FMT, &fmt); BYE_ON(ret < 0, "VIDIOC_G_FMT failed: %s\n", ERRSTR); printf("G_FMT(start): width = %u, height = %u, 4cc = %.4s\n", fmt.fmt.pix.width, fmt.fmt.pix.height, (char*)&fmt.fmt.pix.pixelformat); if (s.use_wh) { fmt.fmt.pix.width = s.w; fmt.fmt.pix.height = s.h; } if (s.in_fourcc) fmt.fmt.pix.pixelformat = s.in_fourcc; ret = ioctl(v4lfd, VIDIOC_S_FMT, &fmt); BYE_ON(ret < 0, "VIDIOC_S_FMT failed: %s\n", ERRSTR); ret = ioctl(v4lfd, VIDIOC_G_FMT, &fmt); BYE_ON(ret < 0, "VIDIOC_G_FMT failed: %s\n", ERRSTR); printf("G_FMT(final): width = %u, height = %u, 4cc = %.4s\n", fmt.fmt.pix.width, fmt.fmt.pix.height, (char*)&fmt.fmt.pix.pixelformat); struct v4l2_requestbuffers rqbufs; memset(&rqbufs, 0, sizeof(rqbufs)); rqbufs.count = s.buffer_count; rqbufs.type = V4L2_BUF_TYPE_VIDEO_CAPTURE; rqbufs.memory = V4L2_MEMORY_DMABUF; ret = ioctl(v4lfd, VIDIOC_REQBUFS, &rqbufs); BYE_ON(ret < 0, "VIDIOC_REQBUFS failed: %s\n", ERRSTR); BYE_ON(rqbufs.count < s.buffer_count, "video node allocated only " "%u of %u buffers\n", rqbufs.count, s.buffer_count); s.in_fourcc = fmt.fmt.pix.pixelformat; s.w = fmt.fmt.pix.width; s.h = fmt.fmt.pix.height; /* TODO: add support for multiplanar formats */ struct buffer buffer[s.buffer_count]; uint64_t size = fmt.fmt.pix.sizeimage; uint32_t pitch = fmt.fmt.pix.bytesperline; printf("size = %llu pitch = %u\n", size, pitch); for (int i = 0; i < s.buffer_count; ++i) { ret = buffer_create(&buffer[i], drmfd, &s, size, pitch); BYE_ON(ret, "failed to create buffer%d\n", i); } printf("buffers ready\n"); drmModeModeInfo drmmode; uint32_t con; ret = find_mode(&drmmode, drmfd, &s, &con); BYE_ON(ret, "failed to find valid mode\n"); ret = drmModeSetCrtc(drmfd, s.crtId, buffer[0].fb_handle, 0, 0, &con, 1, &drmmode); BYE_ON(ret, "drmModeSetCrtc failed: %s\n", ERRSTR); /* enqueueing first buffer to DRM */ ret = drmModePageFlip(drmfd, s.crtId, buffer[0].fb_handle, DRM_MODE_PAGE_FLIP_EVENT, 0); BYE_ON(ret, "drmModePageFlip failed: %s\n", ERRSTR); for (int i = 1; i < s.buffer_count; ++i) { struct v4l2_buffer buf; memset(&buf, 0, sizeof buf); buf.index = i; buf.type = V4L2_BUF_TYPE_VIDEO_CAPTURE; buf.memory = V4L2_MEMORY_DMABUF; buf.m.fd = buffer[i].dbuf_fd; ret = ioctl(v4lfd, VIDIOC_QBUF, &buf); BYE_ON(ret < 0, "VIDIOC_QBUF for buffer %d failed: %s\n", buf.index, ERRSTR); } int type = V4L2_BUF_TYPE_VIDEO_CAPTURE; ret = ioctl(v4lfd, VIDIOC_STREAMON, &type); BYE_ON(ret < 0, "STREAMON failed: %s\n", ERRSTR); struct pollfd fds[] = { { .fd = v4lfd, .events = POLLIN }, { .fd = drmfd, .events = POLLIN }, }; /* buffer currently used by drm */ stream.v4lfd = v4lfd; stream.current_buffer = -1; stream.buffer = buffer; while ((ret = poll(fds, 2, 5000)) > 0) { if (fds[0].revents & POLLIN) { struct v4l2_buffer buf; memset(&buf, 0, sizeof buf); /* dequeue buffer */ buf.type = V4L2_BUF_TYPE_VIDEO_CAPTURE; buf.memory = V4L2_MEMORY_DMABUF; ret = ioctl(v4lfd, VIDIOC_DQBUF, &buf); BYE_ON(ret, "VIDIOC_DQBUF failed: %s\n", ERRSTR); ret = drmModePageFlip(drmfd, s.crtId, buffer[buf.index].fb_handle, DRM_MODE_PAGE_FLIP_EVENT, (void*)buf.index); BYE_ON(ret, "drmModePageFlip failed: %s\n", ERRSTR); } if (fds[1].revents & POLLIN) { drmEventContext evctx; memset(&evctx, 0, sizeof evctx); evctx.version = DRM_EVENT_CONTEXT_VERSION; evctx.page_flip_handler = page_flip_handler; ret = drmHandleEvent(drmfd, &evctx); BYE_ON(ret, "drmHandleEvent failed: %s\n", ERRSTR); } } return 0; }

13 years, 8 months

2
1
0 0

[PATCH 0/3] Integration of vb2-vmalloc and VIVI with dmabuf

by Tomasz Stanislawski

Hello everyone, The patcheset adds support for DMABUF [1] importing to vmalloc allocator in videobuf2 stack. This is an incremental patch to 'Integration of videobuf2 with dmabuf' patchset [2]. This patch makes use of vmap extension for dmabuf proposed by Dave Airlie [3]. The vmap was preferred over the kmap extension. The reason is that VIVI driver requires the memory to be mapped into a contiguous block of virtual memory accessible by kernel. The workaround could be mapping all pages into kernel memory but the dmabuf-kmap interface does guarantee that consecutive pages are mapped into consecutive addresses. [1] https://lkml.org/lkml/2011/12/26/29 [2] http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/46586 [3] http://cgit.freedesktop.org/~airlied/linux/commit/?h=drm-dmabuf2&id=c481a54… Dave Airlie (1): dma-buf: add vmap interface Tomasz Stanislawski (2): v4l: vb2-vmalloc: add support for dmabuf importing v4l: vivi: support for dmabuf importing drivers/base/dma-buf.c | 29 ++++++++++++++++ drivers/media/video/Kconfig | 1 + drivers/media/video/videobuf2-vmalloc.c | 56 +++++++++++++++++++++++++++++++ drivers/media/video/vivi.c | 2 +- include/linux/dma-buf.h | 16 +++++++++ 5 files changed, 103 insertions(+), 1 deletions(-) -- 1.7.5.4

13 years, 8 months

2
4
0 0

“海关三大质疑”解析与应对

by 通关改革

��ɡ��Ӧ�Բ�� ʱ��ص㣺2012��4��12-13��Ϻ� 4��17-18�ձ�� 2012��4��19-20�� γ̷��ã�2800Ԫ/��/2�죨��Ϸѡ��ͼ��ȣ� �γ̶��󣺽��ҵ�ܾ��񡢽��ڡ��ء��ɹ��߼��Ա,��ҵ��Ա�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� γ̱�� ź��ط��ͨ�ظĸ�Ĳ��ƽ��ȫ��д��ҵ��ԡ��ڻ�� Ʒ��ࡱ��Ʒ�۸񡱡��걨��ʵΪ�ɵ��ܺ��ɺʹ�� г��ҵ��Ӱ��ҵ��ͨ�ء��ʽ��ת�ͳ��˰��ҵ�� Ӱ�졣 ��ɽ��ڻ��Ʒ��ࡱ��ҵ��Ʒ�۸��걨�� ҵ�� 걨��ʵ��⡰��ɡ��ʵ��ҵ��ͨ��Ѷȴ�Υ��ձȽϸߵļ�� ؼ��㣬�Ժ��Ҳͬ��ս��еķ��ɹ淶û�ж��걨��ʵ�Ķ��塢��ɡ��ʡ�Ҫ�� ׼ȷ�Ľ綨��Ҳ��ʵ��ж�ͬһ��⣬��ͬ��塢��ͬ�Ĺ��ͬһ��ز�ͬ ��ְ�ܲ��ͬһִ��߲�ͬ��ʱ�ڻ��в�ͬ��ʹ�� Ϊ��ҵ��׷��ӵ��걨��ʵ��ͷ�۵��⣻ͬʱ��ܺ�ָ��ҵ�� Ʒ��༼�ɽ��кϷ��˰��֤ʵ�÷�� ؾٰ�˴��ѵ�࣬ͨ��ڼ��ɡ�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� γ̴�� T�� һ��֣��α��⡰��ɡ��걨��ʵ�� һ��ɽ��ڻ��Ʒ��࣬��ô�죿 1��ع��ɡ��ҵ��붯̬��յ��Ʒ��ߺͼ�� 2��ο��ٶ�λ��ҵ��Ʒ��Լ��з��ղ��㣿 3��WCO��涨��ɹ��й��ع��϶�� 4��Ӧ��Ʒ��ҵ��ķ��ɷ��գ� ��ɶ��ҵ��Ʒ�۸��걨��ô�죿 1��ͨ�ع��ܵ��ɣ��뵽�Ĳ��Լ�Ӧ�ã� 2��κ��ܹ��˫��֮��Ĺ��ϵ��ϵ�Ժ��۵�Ӱ�죿 3��׼ȷ��Ȩʹ�÷ѡ��Ƿ�Ӧ��˰�۸� 4��Э��ã��ΰ죿 5��ӹ�ó�׻����Ʒ��ϼ��д�Ʒ��߽��ϵȣ��۵��ص㼰��˰&��ղ�� 6��ӹ�ó�׻����Ʒ��ϼ��д�Ʒ��߽��ϵȣ��ڼ۸��걨�� ҵ��걨��ʵ��ô�죿 1��϶��ҵ��걨��ʵ�� 2��ڳ��ֶ��װ��м��ֲ��ȷ�ʽ��ô��ǰ�ȫ��ѧ�ģ� 3��ӹ�ó�ײ��ƽ��ı�Ȼ��Լ��ʧ��Ĳ��Ȳ��Ժ;��ʵʩ�� T�� ڶ��֣��Ʒ��༼��Ϸ��˰��֤ һ��Ʒ��ɽ�� Ҫ��ʾ��ҵƷ��淶��걨��Ϊ��һ��ܵ��ĺ��ص㡣Ŀǰ��ҵ��Ե��С� 1��2011��Ʒ��ص��߽�� 2��к��Ʒ��̻��Ƶ�ȱ��ԣ��ȷʵ��Ч��ú��Ʒ��̻��ƣ� 3��Щ��ڽ��Ʒ��пɲ��õķ�� 4��ŷ��Һ��Ʒ��Ľ��;�� 5��Ļ��Ժ��ؽ��Ʒ��Ӱ�켰��ι�� 6��ҵ��׼��Լ��롶Э��ƶ�ע�͡��ν�� 7��ضԲ��Ṥ��Ʒ�Ĺ��˼·��ɽ�� 8��ڻ��㲿��Ĺ��˼·��ɽ�� 9��ض��ϻ��Ͷ๦�ܻ��Ĺ��˼·��еĲ�� 10��ҵ��Ա��ʵ��Ч��Ʒ��ͨ�ء��Լ�ɱ� ��Ʒ��༼��Ϸ��˰ 1��Żݵ��ݶ�˰�ʺ��Ʒ�� 2��ҵ��Ӧ�Ժ��صĹ�� 3��ܺ��ؽ��ƷԤ��Ĺ涨�� 4��ú��ض��Ʒ��ö��Ϸ��˰ 5��á��Ʒ��״̬��롰��Ʒ��༼�ɡ��Ϸ��˰ 6��á��Ʒ��ר��ԡ��롰��Ʒ��ͨ��ԡ��Ϸ��˰ 7��á�ר��롰ͨ��Ϸ��˰ 8��á��Ż�ԭ��ر�׼��롰��Ż�ԭ��ر�׼��Ϸ��˰ ��Ʒ��༼��Ϸ��֤ 1��ó�׹��Ƶ�Ŀ�ġ��ֶΡ� 2��֤��֤��ؼ��֤��ʲô��ͬ�� 3��綨��Ʒ��ġ� 4��֤��ķ��塣 5��á��Ʒ�ɷ֡��ó�׹��ơ� 6��á��״̬��Ϸ��֤�� 7��á��ӹ��ȡ��Ϸ��֤�� 8��ú��ö��ܡ��֤��ա� 9��ߡ��顢��Ͼȼá��֤��Ϊ�� T�� ҵ��ʵս��Ч��ú�� һ��ض�� 1��ı�� 2��ĵ��Ͳ��ʵ�� 3��Ӱ�캣��е��ߺͷ�� 4��ķ�չ�� 5��ҵ��úú��Ż�� ˰�� 1��˰��ʺ͹�� 2��йر�˰��ĺ��ߺ��Ӧ��Żݴ�ʩ 3��йر�˰��ߺ��Ӧ��Żݴ�ʩ 4��ҵӦ��ú�Ӧ�Ա�˰�� 5��˰��߶��ҵ��Ӫ��׷�� 6��˰��ļ�ܰ취 7��뾳��˰�ı�� 8��˰��Ľ��뻷�� 9��˰��δ��չ�� ڼӹ�� 1��ڼӹ��빦�� 2��йس��ڼӹ��ĺ��ߺ��Ӧ��Żݴ�ʩ 3��йس��ڼӹ��ߺ��Ӧ��Żݴ�ʩ 4��ҵӦ��ú�Ӧ�Գ��ڼӹ�� 5��ڼӹ��߶��ҵ��Ӫ��׷�� 6��ڼӹ��ļ�� 7��ڼӹ��Ľ��뻷�� 8��ڼӹ��ͷ�չ�� 9��˰��ڼӹ��ӱȽ� �� ġ��˰��԰�� 1��԰��빦�� 2��԰��ҵ��ģʽ�뺣��԰��淶 3��й��԰��ĺ��ߺ��Ӧ��Żݴ�ʩ 4��й��԰��Ĺ�˰��ߺ�� 5��԰��ز��ߺ͵ط�� 6��ҵӦ��ú�Ӧ��԰�� 7��԰��߶��ҵ��Ӫ��׷�� 8��԰��԰��ҵ�� 9��԰��Ľ��뻷�� 10��԰��ͷ�չ�� 11��ҵ��Ӫ��Ӱ�� 12��˸��ҵ 13��԰��뱣˰��ͳ��ڼӹ��Ӫҵ��ױȽ� 14��԰��뱣˰��ͳ��ڼӹ��Ŀ��ҵ�� 15��԰��밶ҵ�� 16��԰��ʱ�˰�� 塢��˰��A��B�� 1��˰��ĵ��빦�� 2��йر�˰��ĵĺ��ߺ��Ӧ��Żݴ�ʩ 3��йر�˰��ĵ��ߺ��Ӧ��Żݴ�ʩ 4��ҵӦ��ú�Ӧ�Ա�˰��ĵ�� 5��˰��߶��ҵ��Ӫ��׷�� 6��˰��Ļ��ļ�� 7��˰��Ļ��Ľ��뻷�� 8��˰��ĵ��ͷ�չ�� 9��˰��뱣˰��ͳ��ڼӹ��ӱȽ� 10��˰��A��B�͵��ͬ��ҵ��Ӧ�Բ�� 11��˰��ĵĿ��ҵ��Ӧע�� ˰�� 1��˰�� 2��˰��Żݴ�ʩ��뱣˰��԰��ıȽ� 3��˰��ҵ��Ӧ��β�� 4��ҵ��Ч��ñ�˰��ĸ�� ߡ��ӹ�ó�׺��ؼ�� 1��ӹ�ó�׺��ؼ�ܵ��ʺ͹�� 2��ӹ�ó�׺��ؼ�ܵ��Ӧ�Ż��ߺ�� 3��ӹ�ó�׵�˰��Ż��߷�� 4��ϼӹ��ϼӹ��˰�ȽϷ�� 5��ӹ�ó��ת�� 6��ӹ�ó��̷�� 7��ӹ�ó�׵ĵ��Ĺ�� 8��ӹ�ó��ƽ��뺣�ؼӹ�ó�� 9��밶��еļӹ�ó�� ˡ��ӹ��ת��ؼ�� 1��ӹ��ת�� 2��ض��ӹ��ת�Ĺ淶��Ͳ�ͬ��Ĳ�� 3��ӹ��ת��˰��ϵĵط��Բ��˶��µĽ�ת�� 4��ӹ��ת��뻷�� 5��ӹ��ת��˰ 6��ӹ��ת��԰�� 7��밶��е��ӹ��ת �� š�� 1�� 2��ҵ�� 3��걨��ڰ��ŵ��Ե�� 4��ҵӦ��Ӧ�� ʮ��˰��е��밶��͹��ʱ�˰�� 1��ҵӦ��ν��˰��Ӫ��ʱ�˰��밶�� 2��밶��ҵ��˰��ҵ�� 3��밶��ʲ�ת�� 4��밶ó�׵Ĳ�� 5��밶ó�ײ��е��Ѵ��Ӧ�� 6��밶��뱣˰��ر��԰��ͱ�˰��Ч�� 7��׷��ҵ��Ӫ�еĹ�� 8��⾭Ӫ��ʱ�˰�ﻮ 9��Ӧ�Թ��ʷ��˰��ʩ 10��ʱ�˰��Ժͼ�� 11��ʱ�˰�Ĳ�ͬ�ֶ� 12��ʱ�˰�뱣˰��Ľ�� ʮһ��ͬ��ʵ��ҵ��Ч��ú��ߺ��Żݴ�ʩ 1��ó�׹�˾��ú��ߺͱ�˰�� 2��ҵ�ر��ǵ��/��ķ��Ӧ��ҵ��ú��ߺͱ�˰�� 3��һ��ó��ҵ��ú��ߺͱ�˰�� 4��ӹ�ó��ҵ��ú��ߺͱ�˰�� 5��ҵ��ú��ߺͱ�˰�� 6��ת��ҵ��еı�˰��ĺ�� 7��ҵ��ν��˰��뺣��ҵ��Ч�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� ʦ�� ˶ ��ʦ��˫˶ʿ(��ѧMBA��Ͽ��ѧ��ѧ˶ʿ)��ʡ�⾭ó��ó�׹��ʣ��۹� �ʾ��ù��ѧԺ��ڣ��ó�״ٽ��Ա��С��ҵó��̳��֮һ�� 磵��ǿ��й��ʳƷ��ڼ��Ź�˾��פ��ۡ��ô��죬 �ݶ��(��)�Ϻ��޹�˾��Ӫ�ܼࡢ��ĳ��ѯ��޹�˾�ܾ��IBT�� ѯ��޹�˾��ó��ϯ��ѯʦ��һ�ۺ��г��ܼࡢ�麣��ʯ��豸 ��ڹ�˾�ܾ��Ⱥ��Ϻ��ɽ��㽭��ա��Ĵ��ȵؾ��ˣ��ೡ�� ó��ר�⽲��Ϊ��ټ��ҵ��ר��ѵ��ʷ��ܵ��ҵ��ѧԱ�Ĺ㷺�� м��֪ʶ��ʵ��飬�ǵ��͵�ʵս�ɽ�ʦ��óҵ��飬�ر��ڴ� ��óҵ��ⷽ��ж��ļ��ͼ��ɣ��ҵ��ܺͼ��ѵ��Ա��Թ� ��ó��м��ȷ��⣬ͬʱ��ںܶഴ��ԡ��Ե�ԵĲ��ַ��ĵ�ͬ��ҽ� ��ͷ��ÿ�ζ��ѧԱ��δ��é��ٿ�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� .��.��.֯��ŵ˹��ҵ��ѯ��޹�˾ �� .�� .��.��.�ߣ��- - ��.��.��.�� С�� .�� .��.��.��: �� - - ��.��.��.�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� ��뽫��±��д��͵��chinasypx@foxmail.com��Ա��ڵ�һʱ��ϵ! �� ִ �� ҵ�λ��_______�˱�.��μӡ��ɡ��Ӧ�Բ��ԡ� ��λ��ƣ�_____________________________________________ �� ϵ �ˣ�_____________ ��ϵ�绰��_______________ �ֻ��_______________ ͼ�Ĵ��棺_____________ ��䣺_____________________________________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ã�___________ Ԫ�� ʽ�� 𡡡� ֧ Ʊ�� ת �ʡ��ѡ��򡰡̡�� ע: 1.��ѱ��ִ��ú�ش��˾��Ϊȷ��,��ٴε绰ȷ��! 2.��γ̿ɸ��ҵ��Ҫ��֯��ѵ��

13 years, 8 months

1
0
0 0

“海关三大质疑”

by 各关区

��ɡ��Ӧ�Բ�� ʱ��ص㣺2012��4��12-13��Ϻ� 4��17-18�ձ�� 2012��4��19-20�� γ̷��ã�2800Ԫ/��/2�죨��Ϸѡ��ͼ��ȣ� �γ̶��󣺽��ҵ�ܾ��񡢽��ڡ��ء��ɹ��߼��Ա,��ҵ��Ա�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� γ̱�� ź��ط��ͨ�ظĸ�Ĳ��ƽ��ȫ��д��ҵ��ԡ��ڻ�� Ʒ��ࡱ��Ʒ�۸񡱡��걨��ʵΪ�ɵ��ܺ��ɺʹ�� г��ҵ��Ӱ��ҵ��ͨ�ء��ʽ��ת�ͳ��˰��ҵ�� Ӱ�졣 ��ɽ��ڻ��Ʒ��ࡱ��ҵ��Ʒ�۸��걨�� ҵ�� 걨��ʵ��⡰��ɡ��ʵ��ҵ��ͨ��Ѷȴ�Υ��ձȽϸߵļ�� ؼ��㣬�Ժ��Ҳͬ��ս��еķ��ɹ淶û�ж��걨��ʵ�Ķ��塢��ɡ��ʡ�Ҫ�� ׼ȷ�Ľ綨��Ҳ��ʵ��ж�ͬһ��⣬��ͬ��塢��ͬ�Ĺ��ͬһ��ز�ͬ ��ְ�ܲ��ͬһִ��߲�ͬ��ʱ�ڻ��в�ͬ��ʹ�� Ϊ��ҵ��׷��ӵ��걨��ʵ��ͷ�۵��⣻ͬʱ��ܺ�ָ��ҵ�� Ʒ��༼�ɽ��кϷ��˰��֤ʵ�÷�� ؾٰ�˴��ѵ�࣬ͨ��ڼ��ɡ�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� γ̴�� T�� һ��֣��α��⡰��ɡ��걨��ʵ�� һ��ɽ��ڻ��Ʒ��࣬��ô�죿 1��ع��ɡ��ҵ��붯̬��յ��Ʒ��ߺͼ�� 2��ο��ٶ�λ��ҵ��Ʒ��Լ��з��ղ��㣿 3��WCO��涨��ɹ��й��ع��϶�� 4��Ӧ��Ʒ��ҵ��ķ��ɷ��գ� ��ɶ��ҵ��Ʒ�۸��걨��ô�죿 1��ͨ�ع��ܵ��ɣ��뵽�Ĳ��Լ�Ӧ�ã� 2��κ��ܹ��˫��֮��Ĺ��ϵ��ϵ�Ժ��۵�Ӱ�죿 3��׼ȷ��Ȩʹ�÷ѡ��Ƿ�Ӧ��˰�۸� 4��Э��ã��ΰ죿 5��ӹ�ó�׻����Ʒ��ϼ��д�Ʒ��߽��ϵȣ��۵��ص㼰��˰&��ղ�� 6��ӹ�ó�׻����Ʒ��ϼ��д�Ʒ��߽��ϵȣ��ڼ۸��걨�� ҵ��걨��ʵ��ô�죿 1��϶��ҵ��걨��ʵ�� 2��ڳ��ֶ��װ��м��ֲ��ȷ�ʽ��ô��ǰ�ȫ��ѧ�ģ� 3��ӹ�ó�ײ��ƽ��ı�Ȼ��Լ��ʧ��Ĳ��Ȳ��Ժ;��ʵʩ�� T�� ڶ��֣��Ʒ��༼��Ϸ��˰��֤ һ��Ʒ��ɽ�� Ҫ��ʾ��ҵƷ��淶��걨��Ϊ��һ��ܵ��ĺ��ص㡣Ŀǰ��ҵ��Ե��С� 1��2011��Ʒ��ص��߽�� 2��к��Ʒ��̻��Ƶ�ȱ��ԣ��ȷʵ��Ч��ú��Ʒ��̻��ƣ� 3��Щ��ڽ��Ʒ��пɲ��õķ�� 4��ŷ��Һ��Ʒ��Ľ��;�� 5��Ļ��Ժ��ؽ��Ʒ��Ӱ�켰��ι�� 6��ҵ��׼��Լ��롶Э��ƶ�ע�͡��ν�� 7��ضԲ��Ṥ��Ʒ�Ĺ��˼·��ɽ�� 8��ڻ��㲿��Ĺ��˼·��ɽ�� 9��ض��ϻ��Ͷ๦�ܻ��Ĺ��˼·��еĲ�� 10��ҵ��Ա��ʵ��Ч��Ʒ��ͨ�ء��Լ�ɱ� ��Ʒ��༼��Ϸ��˰ 1��Żݵ��ݶ�˰�ʺ��Ʒ�� 2��ҵ��Ӧ�Ժ��صĹ�� 3��ܺ��ؽ��ƷԤ��Ĺ涨�� 4��ú��ض��Ʒ��ö��Ϸ��˰ 5��á��Ʒ��״̬��롰��Ʒ��༼�ɡ��Ϸ��˰ 6��á��Ʒ��ר��ԡ��롰��Ʒ��ͨ��ԡ��Ϸ��˰ 7��á�ר��롰ͨ��Ϸ��˰ 8��á��Ż�ԭ��ر�׼��롰��Ż�ԭ��ر�׼��Ϸ��˰ ��Ʒ��༼��Ϸ��֤ 1��ó�׹��Ƶ�Ŀ�ġ��ֶΡ� 2��֤��֤��ؼ��֤��ʲô��ͬ�� 3��綨��Ʒ��ġ� 4��֤��ķ��塣 5��á��Ʒ�ɷ֡��ó�׹��ơ� 6��á��״̬��Ϸ��֤�� 7��á��ӹ��ȡ��Ϸ��֤�� 8��ú��ö��ܡ��֤��ա� 9��ߡ��顢��Ͼȼá��֤��Ϊ�� T�� ҵ��ʵս��Ч��ú�� һ��ض�� 1��ı�� 2��ĵ��Ͳ��ʵ�� 3��Ӱ�캣��е��ߺͷ�� 4��ķ�չ�� 5��ҵ��úú��Ż�� ˰�� 1��˰��ʺ͹�� 2��йر�˰��ĺ��ߺ��Ӧ��Żݴ�ʩ 3��йر�˰��ߺ��Ӧ��Żݴ�ʩ 4��ҵӦ��ú�Ӧ�Ա�˰�� 5��˰��߶��ҵ��Ӫ��׷�� 6��˰��ļ�ܰ취 7��뾳��˰�ı�� 8��˰��Ľ��뻷�� 9��˰��δ��չ�� ڼӹ�� 1��ڼӹ��빦�� 2��йس��ڼӹ��ĺ��ߺ��Ӧ��Żݴ�ʩ 3��йس��ڼӹ��ߺ��Ӧ��Żݴ�ʩ 4��ҵӦ��ú�Ӧ�Գ��ڼӹ�� 5��ڼӹ��߶��ҵ��Ӫ��׷�� 6��ڼӹ��ļ�� 7��ڼӹ��Ľ��뻷�� 8��ڼӹ��ͷ�չ�� 9��˰��ڼӹ��ӱȽ� �� ġ��˰��԰�� 1��԰��빦�� 2��԰��ҵ��ģʽ�뺣��԰��淶 3��й��԰��ĺ��ߺ��Ӧ��Żݴ�ʩ 4��й��԰��Ĺ�˰��ߺ�� 5��԰��ز��ߺ͵ط�� 6��ҵӦ��ú�Ӧ��԰�� 7��԰��߶��ҵ��Ӫ��׷�� 8��԰��԰��ҵ�� 9��԰��Ľ��뻷�� 10��԰��ͷ�չ�� 11��ҵ��Ӫ��Ӱ�� 12��˸��ҵ 13��԰��뱣˰��ͳ��ڼӹ��Ӫҵ��ױȽ� 14��԰��뱣˰��ͳ��ڼӹ��Ŀ��ҵ�� 15��԰��밶ҵ�� 16��԰��ʱ�˰�� 塢��˰��A��B�� 1��˰��ĵ��빦�� 2��йر�˰��ĵĺ��ߺ��Ӧ��Żݴ�ʩ 3��йر�˰��ĵ��ߺ��Ӧ��Żݴ�ʩ 4��ҵӦ��ú�Ӧ�Ա�˰��ĵ�� 5��˰��߶��ҵ��Ӫ��׷�� 6��˰��Ļ��ļ�� 7��˰��Ļ��Ľ��뻷�� 8��˰��ĵ��ͷ�չ�� 9��˰��뱣˰��ͳ��ڼӹ��ӱȽ� 10��˰��A��B�͵��ͬ��ҵ��Ӧ�Բ�� 11��˰��ĵĿ��ҵ��Ӧע�� ˰�� 1��˰�� 2��˰��Żݴ�ʩ��뱣˰��԰��ıȽ� 3��˰��ҵ��Ӧ��β�� 4��ҵ��Ч��ñ�˰��ĸ�� ߡ��ӹ�ó�׺��ؼ�� 1��ӹ�ó�׺��ؼ�ܵ��ʺ͹�� 2��ӹ�ó�׺��ؼ�ܵ��Ӧ�Ż��ߺ�� 3��ӹ�ó�׵�˰��Ż��߷�� 4��ϼӹ��ϼӹ��˰�ȽϷ�� 5��ӹ�ó��ת�� 6��ӹ�ó��̷�� 7��ӹ�ó�׵ĵ��Ĺ�� 8��ӹ�ó��ƽ��뺣�ؼӹ�ó�� 9��밶��еļӹ�ó�� ˡ��ӹ��ת��ؼ�� 1��ӹ��ת�� 2��ض��ӹ��ת�Ĺ淶��Ͳ�ͬ��Ĳ�� 3��ӹ��ת��˰��ϵĵط��Բ��˶��µĽ�ת�� 4��ӹ��ת��뻷�� 5��ӹ��ת��˰ 6��ӹ��ת��԰�� 7��밶��е��ӹ��ת �� š�� 1�� 2��ҵ�� 3��걨��ڰ��ŵ��Ե�� 4��ҵӦ��Ӧ�� ʮ��˰��е��밶��͹��ʱ�˰�� 1��ҵӦ��ν��˰��Ӫ��ʱ�˰��밶�� 2��밶��ҵ��˰��ҵ�� 3��밶��ʲ�ת�� 4��밶ó�׵Ĳ�� 5��밶ó�ײ��е��Ѵ��Ӧ�� 6��밶��뱣˰��ر��԰��ͱ�˰��Ч�� 7��׷��ҵ��Ӫ�еĹ�� 8��⾭Ӫ��ʱ�˰�ﻮ 9��Ӧ�Թ��ʷ��˰��ʩ 10��ʱ�˰��Ժͼ�� 11��ʱ�˰�Ĳ�ͬ�ֶ� 12��ʱ�˰�뱣˰��Ľ�� ʮһ��ͬ��ʵ��ҵ��Ч��ú��ߺ��Żݴ�ʩ 1��ó�׹�˾��ú��ߺͱ�˰�� 2��ҵ�ر��ǵ��/��ķ��Ӧ��ҵ��ú��ߺͱ�˰�� 3��һ��ó��ҵ��ú��ߺͱ�˰�� 4��ӹ�ó��ҵ��ú��ߺͱ�˰�� 5��ҵ��ú��ߺͱ�˰�� 6��ת��ҵ��еı�˰��ĺ�� 7��ҵ��ν��˰��뺣��ҵ��Ч�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� ʦ�� ˶ ��ʦ��˫˶ʿ(��ѧMBA��Ͽ��ѧ��ѧ˶ʿ)��ʡ�⾭ó��ó�׹��ʣ��۹� �ʾ��ù��ѧԺ��ڣ��ó�״ٽ��Ա��С��ҵó��̳��֮һ�� 磵��ǿ��й��ʳƷ��ڼ��Ź�˾��פ��ۡ��ô��죬 �ݶ��(��)�Ϻ��޹�˾��Ӫ�ܼࡢ��ĳ��ѯ��޹�˾�ܾ��IBT�� ѯ��޹�˾��ó��ϯ��ѯʦ��һ�ۺ��г��ܼࡢ�麣��ʯ��豸 ��ڹ�˾�ܾ��Ⱥ��Ϻ��ɽ��㽭��ա��Ĵ��ȵؾ��ˣ��ೡ�� ó��ר�⽲��Ϊ��ټ��ҵ��ר��ѵ��ʷ��ܵ��ҵ��ѧԱ�Ĺ㷺�� м��֪ʶ��ʵ��飬�ǵ��͵�ʵս�ɽ�ʦ��óҵ��飬�ر��ڴ� ��óҵ��ⷽ��ж��ļ��ͼ��ɣ��ҵ��ܺͼ��ѵ��Ա��Թ� ��ó��м��ȷ��⣬ͬʱ��ںܶഴ��ԡ��Ե�ԵĲ��ַ��ĵ�ͬ��ҽ� ��ͷ��ÿ�ζ��ѧԱ��δ��é��ٿ�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� .��.��.֯��ŵ˹��ҵ��ѯ��޹�˾ �� .�� .��.��.�ߣ��- - ��.��.��.�� С�� .�� .��.��.��: �� - - ��.��.��.�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� ��뽫��±��д��͵��chinasypx@foxmail.com��Ա��ڵ�һʱ��ϵ! �� ִ �� ҵ�λ��_______�˱�.��μӡ��ɡ��Ӧ�Բ��ԡ� ��λ��ƣ�_____________________________________________ �� ϵ �ˣ�_____________ ��ϵ�绰��_______________ �ֻ��_______________ ͼ�Ĵ��棺_____________ ��䣺_____________________________________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ã�___________ Ԫ�� ʽ�� 𡡡� ֧ Ʊ�� ת �ʡ��ѡ��򡰡̡�� ע: 1.��ѱ��ִ��ú�ش��˾��Ϊȷ��,��ٴε绰ȷ��! 2.��γ̿ɸ��ҵ��Ҫ��֯��ѵ��

13 years, 8 months

1
0
0 0

“海关三大质疑”

by 各关区

��ɡ��Ӧ�Բ�� ʱ��ص㣺2012��4��12-13��Ϻ� 4��17-18�ձ�� 2012��4��19-20�� γ̷��ã�2800Ԫ/��/2�죨��Ϸѡ��ͼ��ȣ� �γ̶��󣺽��ҵ�ܾ��񡢽��ڡ��ء��ɹ��߼��Ա,��ҵ��Ա�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� γ̱�� ź��ط��ͨ�ظĸ�Ĳ��ƽ��ȫ��д��ҵ��ԡ��ڻ�� Ʒ��ࡱ��Ʒ�۸񡱡��걨��ʵΪ�ɵ��ܺ��ɺʹ�� г��ҵ��Ӱ��ҵ��ͨ�ء��ʽ��ת�ͳ��˰��ҵ�� Ӱ�졣 ��ɽ��ڻ��Ʒ��ࡱ��ҵ��Ʒ�۸��걨�� ҵ�� 걨��ʵ��⡰��ɡ��ʵ��ҵ��ͨ��Ѷȴ�Υ��ձȽϸߵļ�� ؼ��㣬�Ժ��Ҳͬ��ս��еķ��ɹ淶û�ж��걨��ʵ�Ķ��塢��ɡ��ʡ�Ҫ�� ׼ȷ�Ľ綨��Ҳ��ʵ��ж�ͬһ��⣬��ͬ��塢��ͬ�Ĺ��ͬһ��ز�ͬ ��ְ�ܲ��ͬһִ��߲�ͬ��ʱ�ڻ��в�ͬ��ʹ�� Ϊ��ҵ��׷��ӵ��걨��ʵ��ͷ�۵��⣻ͬʱ��ܺ�ָ��ҵ�� Ʒ��༼�ɽ��кϷ��˰��֤ʵ�÷�� ؾٰ�˴��ѵ�࣬ͨ��ڼ��ɡ�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� γ̴�� T�� һ��֣��α��⡰��ɡ��걨��ʵ�� һ��ɽ��ڻ��Ʒ��࣬��ô�죿 1��ع��ɡ��ҵ��붯̬��յ��Ʒ��ߺͼ�� 2��ο��ٶ�λ��ҵ��Ʒ��Լ��з��ղ��㣿 3��WCO��涨��ɹ��й��ع��϶�� 4��Ӧ��Ʒ��ҵ��ķ��ɷ��գ� ��ɶ��ҵ��Ʒ�۸��걨��ô�죿 1��ͨ�ع��ܵ��ɣ��뵽�Ĳ��Լ�Ӧ�ã� 2��κ��ܹ��˫��֮��Ĺ��ϵ��ϵ�Ժ��۵�Ӱ�죿 3��׼ȷ��Ȩʹ�÷ѡ��Ƿ�Ӧ��˰�۸� 4��Э��ã��ΰ죿 5��ӹ�ó�׻����Ʒ��ϼ��д�Ʒ��߽��ϵȣ��۵��ص㼰��˰&��ղ�� 6��ӹ�ó�׻����Ʒ��ϼ��д�Ʒ��߽��ϵȣ��ڼ۸��걨�� ҵ��걨��ʵ��ô�죿 1��϶��ҵ��걨��ʵ�� 2��ڳ��ֶ��װ��м��ֲ��ȷ�ʽ��ô��ǰ�ȫ��ѧ�ģ� 3��ӹ�ó�ײ��ƽ��ı�Ȼ��Լ��ʧ��Ĳ��Ȳ��Ժ;��ʵʩ�� T�� ڶ��֣��Ʒ��༼��Ϸ��˰��֤ һ��Ʒ��ɽ�� Ҫ��ʾ��ҵƷ��淶��걨��Ϊ��һ��ܵ��ĺ��ص㡣Ŀǰ��ҵ��Ե��С� 1��2011��Ʒ��ص��߽�� 2��к��Ʒ��̻��Ƶ�ȱ��ԣ��ȷʵ��Ч��ú��Ʒ��̻��ƣ� 3��Щ��ڽ��Ʒ��пɲ��õķ�� 4��ŷ��Һ��Ʒ��Ľ��;�� 5��Ļ��Ժ��ؽ��Ʒ��Ӱ�켰��ι�� 6��ҵ��׼��Լ��롶Э��ƶ�ע�͡��ν�� 7��ضԲ��Ṥ��Ʒ�Ĺ��˼·��ɽ�� 8��ڻ��㲿��Ĺ��˼·��ɽ�� 9��ض��ϻ��Ͷ๦�ܻ��Ĺ��˼·��еĲ�� 10��ҵ��Ա��ʵ��Ч��Ʒ��ͨ�ء��Լ�ɱ� ��Ʒ��༼��Ϸ��˰ 1��Żݵ��ݶ�˰�ʺ��Ʒ�� 2��ҵ��Ӧ�Ժ��صĹ�� 3��ܺ��ؽ��ƷԤ��Ĺ涨�� 4��ú��ض��Ʒ��ö��Ϸ��˰ 5��á��Ʒ��״̬��롰��Ʒ��༼�ɡ��Ϸ��˰ 6��á��Ʒ��ר��ԡ��롰��Ʒ��ͨ��ԡ��Ϸ��˰ 7��á�ר��롰ͨ��Ϸ��˰ 8��á��Ż�ԭ��ر�׼��롰��Ż�ԭ��ر�׼��Ϸ��˰ ��Ʒ��༼��Ϸ��֤ 1��ó�׹��Ƶ�Ŀ�ġ��ֶΡ� 2��֤��֤��ؼ��֤��ʲô��ͬ�� 3��綨��Ʒ��ġ� 4��֤��ķ��塣 5��á��Ʒ�ɷ֡��ó�׹��ơ� 6��á��״̬��Ϸ��֤�� 7��á��ӹ��ȡ��Ϸ��֤�� 8��ú��ö��ܡ��֤��ա� 9��ߡ��顢��Ͼȼá��֤��Ϊ�� T�� ҵ��ʵս��Ч��ú�� һ��ض�� 1��ı�� 2��ĵ��Ͳ��ʵ�� 3��Ӱ�캣��е��ߺͷ�� 4��ķ�չ�� 5��ҵ��úú��Ż�� ˰�� 1��˰��ʺ͹�� 2��йر�˰��ĺ��ߺ��Ӧ��Żݴ�ʩ 3��йر�˰��ߺ��Ӧ��Żݴ�ʩ 4��ҵӦ��ú�Ӧ�Ա�˰�� 5��˰��߶��ҵ��Ӫ��׷�� 6��˰��ļ�ܰ취 7��뾳��˰�ı�� 8��˰��Ľ��뻷�� 9��˰��δ��չ�� ڼӹ�� 1��ڼӹ��빦�� 2��йس��ڼӹ��ĺ��ߺ��Ӧ��Żݴ�ʩ 3��йس��ڼӹ��ߺ��Ӧ��Żݴ�ʩ 4��ҵӦ��ú�Ӧ�Գ��ڼӹ�� 5��ڼӹ��߶��ҵ��Ӫ��׷�� 6��ڼӹ��ļ�� 7��ڼӹ��Ľ��뻷�� 8��ڼӹ��ͷ�չ�� 9��˰��ڼӹ��ӱȽ� �� ġ��˰��԰�� 1��԰��빦�� 2��԰��ҵ��ģʽ�뺣��԰��淶 3��й��԰��ĺ��ߺ��Ӧ��Żݴ�ʩ 4��й��԰��Ĺ�˰��ߺ�� 5��԰��ز��ߺ͵ط�� 6��ҵӦ��ú�Ӧ��԰�� 7��԰��߶��ҵ��Ӫ��׷�� 8��԰��԰��ҵ�� 9��԰��Ľ��뻷�� 10��԰��ͷ�չ�� 11��ҵ��Ӫ��Ӱ�� 12��˸��ҵ 13��԰��뱣˰��ͳ��ڼӹ��Ӫҵ��ױȽ� 14��԰��뱣˰��ͳ��ڼӹ��Ŀ��ҵ�� 15��԰��밶ҵ�� 16��԰��ʱ�˰�� 塢��˰��A��B�� 1��˰��ĵ��빦�� 2��йر�˰��ĵĺ��ߺ��Ӧ��Żݴ�ʩ 3��йر�˰��ĵ��ߺ��Ӧ��Żݴ�ʩ 4��ҵӦ��ú�Ӧ�Ա�˰��ĵ�� 5��˰��߶��ҵ��Ӫ��׷�� 6��˰��Ļ��ļ�� 7��˰��Ļ��Ľ��뻷�� 8��˰��ĵ��ͷ�չ�� 9��˰��뱣˰��ͳ��ڼӹ��ӱȽ� 10��˰��A��B�͵��ͬ��ҵ��Ӧ�Բ�� 11��˰��ĵĿ��ҵ��Ӧע�� ˰�� 1��˰�� 2��˰��Żݴ�ʩ��뱣˰��԰��ıȽ� 3��˰��ҵ��Ӧ��β�� 4��ҵ��Ч��ñ�˰��ĸ�� ߡ��ӹ�ó�׺��ؼ�� 1��ӹ�ó�׺��ؼ�ܵ��ʺ͹�� 2��ӹ�ó�׺��ؼ�ܵ��Ӧ�Ż��ߺ�� 3��ӹ�ó�׵�˰��Ż��߷�� 4��ϼӹ��ϼӹ��˰�ȽϷ�� 5��ӹ�ó��ת�� 6��ӹ�ó��̷�� 7��ӹ�ó�׵ĵ��Ĺ�� 8��ӹ�ó��ƽ��뺣�ؼӹ�ó�� 9��밶��еļӹ�ó�� ˡ��ӹ��ת��ؼ�� 1��ӹ��ת�� 2��ض��ӹ��ת�Ĺ淶��Ͳ�ͬ��Ĳ�� 3��ӹ��ת��˰��ϵĵط��Բ��˶��µĽ�ת�� 4��ӹ��ת��뻷�� 5��ӹ��ת��˰ 6��ӹ��ת��԰�� 7��밶��е��ӹ��ת �� š�� 1�� 2��ҵ�� 3��걨��ڰ��ŵ��Ե�� 4��ҵӦ��Ӧ�� ʮ��˰��е��밶��͹��ʱ�˰�� 1��ҵӦ��ν��˰��Ӫ��ʱ�˰��밶�� 2��밶��ҵ��˰��ҵ�� 3��밶��ʲ�ת�� 4��밶ó�׵Ĳ�� 5��밶ó�ײ��е��Ѵ��Ӧ�� 6��밶��뱣˰��ر��԰��ͱ�˰��Ч�� 7��׷��ҵ��Ӫ�еĹ�� 8��⾭Ӫ��ʱ�˰�ﻮ 9��Ӧ�Թ��ʷ��˰��ʩ 10��ʱ�˰��Ժͼ�� 11��ʱ�˰�Ĳ�ͬ�ֶ� 12��ʱ�˰�뱣˰��Ľ�� ʮһ��ͬ��ʵ��ҵ��Ч��ú��ߺ��Żݴ�ʩ 1��ó�׹�˾��ú��ߺͱ�˰�� 2��ҵ�ر��ǵ��/��ķ��Ӧ��ҵ��ú��ߺͱ�˰�� 3��һ��ó��ҵ��ú��ߺͱ�˰�� 4��ӹ�ó��ҵ��ú��ߺͱ�˰�� 5��ҵ��ú��ߺͱ�˰�� 6��ת��ҵ��еı�˰��ĺ�� 7��ҵ��ν��˰��뺣��ҵ��Ч�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� ʦ�� ˶ ��ʦ��˫˶ʿ(��ѧMBA��Ͽ��ѧ��ѧ˶ʿ)��ʡ�⾭ó��ó�׹��ʣ��۹� �ʾ��ù��ѧԺ��ڣ��ó�״ٽ��Ա��С��ҵó��̳��֮һ�� 磵��ǿ��й��ʳƷ��ڼ��Ź�˾��פ��ۡ��ô��죬 �ݶ��(��)�Ϻ��޹�˾��Ӫ�ܼࡢ��ĳ��ѯ��޹�˾�ܾ��IBT�� ѯ��޹�˾��ó��ϯ��ѯʦ��һ�ۺ��г��ܼࡢ�麣��ʯ��豸 ��ڹ�˾�ܾ��Ⱥ��Ϻ��ɽ��㽭��ա��Ĵ��ȵؾ��ˣ��ೡ�� ó��ר�⽲��Ϊ��ټ��ҵ��ר��ѵ��ʷ��ܵ��ҵ��ѧԱ�Ĺ㷺�� м��֪ʶ��ʵ��飬�ǵ��͵�ʵս�ɽ�ʦ��óҵ��飬�ر��ڴ� ��óҵ��ⷽ��ж��ļ��ͼ��ɣ��ҵ��ܺͼ��ѵ��Ա��Թ� ��ó��м��ȷ��⣬ͬʱ��ںܶഴ��ԡ��Ե�ԵĲ��ַ��ĵ�ͬ��ҽ� ��ͷ��ÿ�ζ��ѧԱ��δ��é��ٿ�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� .��.��.֯��ŵ˹��ҵ��ѯ��޹�˾ �� .�� .��.��.�ߣ��- - ��.��.��.�� С�� .�� .��.��.��: �� - - ��.��.��.�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� ��뽫��±��д��͵��chinasypx@foxmail.com��Ա��ڵ�һʱ��ϵ! �� ִ �� ҵ�λ��_______�˱�.��μӡ��ɡ��Ӧ�Բ��ԡ� ��λ��ƣ�_____________________________________________ �� ϵ �ˣ�_____________ ��ϵ�绰��_______________ �ֻ��_______________ ͼ�Ĵ��棺_____________ ��䣺_____________________________________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ã�___________ Ԫ�� ʽ�� 𡡡� ֧ Ʊ�� ת �ʡ��ѡ��򡰡̡�� ע: 1.��ѱ��ִ��ú�ش��˾��Ϊȷ��,��ٴε绰ȷ��! 2.��γ̿ɸ��ҵ��Ҫ��֯��ѵ��

13 years, 8 months

1
0
0 0

研发★质量★管理

by 保证产品质量的6个根基

研发质量管理――保证产品质量的6个根基 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ 举办时间：2012年4月23-24日北京 4月26-27日上海 4月19-20日深圳培训费用：4000元/两天买一赠一,不再打折” ,单独一人收费2600元。（含两天中餐、指定教材、证书、茶点） ******现特价3200元/两天，买一送一，来一人收费2200元。培训方式：案例分享、实务分析、互动讨论、项目模拟、培训游戏 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ ■课程背景通过产品质量问题的根源分析，发现54％的质量问题源自研发阶段，客户对产品的质量要求越来越高，质量成为产品在市场竞争中脱颖而出的重要武器： 1.如何培养整个公司的质量意识？ 2.如何把质量管理活动变成具体开发的人员的自觉行为？ 3.如何避免质量管理体系和实际执行“两张皮”？ 4.如何把设计中构建产品质量的理念落实到具体的产品开发活动中去？ 5.如何通过全流程的质量管理活动获得产品全生命周期成本的竞争优势？ 6.如何构建能很好支撑公司核心业务运作的研发质量管理体系？ 7.质量管理的职能部门如何设置？如何考评？与业务部门如何协同？ 8.什么样的人比较从事研发质量管理，同时这部分人员的出路在哪里？ 9.质量管理如何从一个支撑辅助角色，转变为公司研发决策的关键支撑？这些问题是业界研发管理人员普遍感到困惑的核心问题。本课程通过业界最佳实践的分享、具体的案例研讨等方式，详细介绍研发质量管理六根基，具体涉及： 1.研发质量管理的组织体系 2.结构化的产品开发流程体系与指标体系 3.产品质量策略和质量计划的制定方法 4.产品开发过程中的技术评审体系（产品级+模块级） 5.产品开发的量化管理方法（业务度量、质量度量） 6.质量管理人员的工作职责、方法、职业发展 7.如何避免研发质量管理体系优化虎头蛇尾 ■参加对象研发总经理/副总、质量部经理、QA经理、PMO（项目管理办公室）主任、测试经理等。 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ ■培训收益 1.了解业界产品研发质量管理的最佳模式与实践 2.了解业务导向的研发管理体系在公司管理体系中的位置 3.掌握研发质量管理组织的架构、职责定位 4.掌握结构化的产品开发流程体系、层次间的接口关系 5.掌握产品质量策划和质量计划的制定方法 6.掌握产品开发过程中技术评审的分层分级与操作方法 7.掌握如何建立质量保证体系、开展质量保证工作 8.掌握度量管理的方法及度量结果在过程改进和绩效考核中的应用 9.掌握如何成功在公司内部实施研发质量管理体系优化 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ ■课程内容 ★ 一、案例分析 ★ 二、研发质量管理概述 1.研发质量管理体系的六个根基： 1)之一：研发流程与指标体系 2)之二：研发质量的组织保障 3)研发质量执行体系 a 之三：研发质量策划（质量计划、质量目标） b 之四：研发质量控制（评审、测试） c 之五：研发质量保证（引导、培训、审计） d 之六：研发质量改进（度量、考核、能力基线） 4)根基之载体：文件体系、IT体系 2.研发质量管理在研发价值链中的位置 1)研发质量管理与研发业务流程、研发项目管理之间的关系 2)研发质量管理与市场、制造、采购、客户服务之间的关系 3.研发质量管理中常见的误区（责任主体错位、缺少全流程概念、……） 4.业界常用研发管理模式介绍 1)NPD（PDMA） a 8大要素介绍（结构化流程、管道管理、……） b 实施实例讲解 2)CMM/CMMI（SEI） a 模型/级别/过程域/具体实践 b 实施实例讲解 3)两者对比分析（优点、改进点、相互配合） 5.研发质量管理体系 1)质量管理新老七工具（关联图、系统图、直方图、控制图、……） 2)研发过程资产库（PAL）（作用、内容、……） 6.实战演练与问题讨论 ★ 三、六根基之一：研发流程与指标体系 1.研发流程体系定义方法论：Designflow 1)基于角色、关注客户、锁定开始与结束 2)角色、活动、链接、分支、结束、多线头、返回点、终端与连接 2.研发流程管理体系： 1)L0：公司整体流程体系定义方法论 ? 波特价值链分析模型 2)L1：产品开发流程概览 3)L2：产品开发阶段流程 4)L3：产品开发子流程（软件开发流程、硬件开发流程、测试流程、……） 5)L4：活动定义与角色说明 6)L5：模板、指导书、样例、检查表 7)实例讲解：某案例公司产品开发流程体系介绍 8)使能流程体系 a 定义 b 举例：缺陷反馈流程、技术评审流程、问题跟踪流程、审计流程 3.度量的基本概念（定义、作用和目的、度量与测量、驾驶窗、度量模型、……） 1)过程质量指标、交付件质量指标 2)度量模型、度量流程 3)实例讲解：某业界最佳的某公司研发过程能力基线（PCB） 4.质量指标的定义 1)质量目标的分解（逻辑分解、物理分解） 2)实例讲解：某案例公司级质量指标定义 3)实例讲解：某案例公司产品级质量指标定义 4)实例讲解：某案例公司项目级质量指标定义 ★ 四、六根基之二：研发质量的组织保障 1.如何设置研发质量管理组织 1)研发质量管理组织设计中存在的误区 2)公司级的质量管理组织如何定位 3)产品级的质量管理组织如何定位 4)项目级的质量管理角色如何定位 5)质量管理与测试、项目管理、文档管理混合在一起的弊端分析 6)质量管理人员的规模确定（业界经验、产品类型、行业竞争、……） 2.质量管理人员的任职资格与职业发展通道 3.什么样的人适合承担QA角色（PQA、SQA、HQA、TQA……） 1)员工不愿意作QA怎么办？ 2)没有QA或者兼职QA可能会导致的后果 4.实例讲解：某业界最佳研发质量管理人员的任职资格体系介绍 5.如何培养QA人员? 6.实战演练与问题讨论 ★ 五、六根基之三：研发质量策划 1.制定质量计划的时机 2.产品质量策略与产品质量计划的关系 1)实例讲解：某案例公司产品质量策略 2)实例讲解：某案例公司产品质量计划（产品级、软件/硬件项目级） 3.产品质量计划相关的责任主体（谁制定、谁批准、谁配合、谁实施） 4.质量目标定义方法 1)目标、上限、下限 2)公司基线目标、公司基线上限、公司基线下限 5.产品质量计划与产品开发其他计划的配合关系 6.产品质量计划与PHB的关系 7.实战演练与问题讨论 ★ 六、六根基之四：研发质量控制之：技术评审（TR） 1.企业在评审操作中常见的问题 1)评审抓壮丁、评审先变科普会、再变批斗会、评审缺少标准靠拍脑袋…… 2.业界最佳研发管理企业的评审体系介绍 1)三级评审体系（业务评审、技术评审、正规检视） 3.技术评审（TR） 1)TR的目的、原则 2)TR评审流程（主要活动、输入、输出） 3)各个角色在评审中的定义和职责（SE、PM、QA、技术专家、……） 4)各TR点的评审要素是如何相互支撑的（产品级、模块级、职能领域、……） 5)TR的三个结论 6)评审专家管理方法 7)谁决定TR是否通过？决策团队、项目经理、QA、还是技术专家？ 8)如何避免技术评审流于形式？（任职资格、计划确定、评审标准、……） 9)实例讲解：某案例公司具体3级技术评审体系 4.实例讲解：TR的载体：TR IT化 5.实战演练与问题讨论 ★ 七、六根基之四：质量控制体系之：测试验证（V&V） 1.研发企业在测试操作中常见的问题 1)基于设计测试、测试过分重复、测试人员地位低下、…… 2.产品级渐增测试模型 1)为什么尽早测试？ 2)渐增测试的优点分析？（提前发现问题、并行开发、减少测试重复、……） 3.高效测试的前提条件 ? 清晰、明确的需求定义 1)客户化测试思维 2)缺陷引入阶段分析 3)优秀需求的标准 4.高效测试的法宝 ? 刚刚好，不多测，也不少测 1)场景用例设计法，案例讲解 2)边界值用例设计法，案例讲解 3)等价类用例设计法，案例讲解 5.业界测试经验汇总（NASA） 6.实战演练与问题讨论 ★ 八、六根基之五：研发质量保证 1.研发质量保证（QA）的理念 1)QA的独立性 2)QA与QC的区别 2.QA工作关系与汇报关系（PQA、SQA、HQA、TQA……） 3.QA主要活动 1)主要活动之一：产品质量计划 2)主要活动之二：引导培训 3)主要活动之三：产品质量度量 4)主要活动之四：技术评审（TR） 5)主要活动之五：审计 6)主要活动之六：质量活动协调 7)主要活动之七：产品质量回溯 8)主要活动之八：质量报告 9)主要活动之九：准备PHB 10)主要活动之十：收集体系改进建议 4.实战演练与问题讨论 ★ 九、六根基之六：研发质量改进 1.企业在质量改进中常见的问题 1)缺少量化数据，管理拍脑袋、数据堆积如山但缺少分析…… 2.度量是研发质量改进的基础（没有度量就没有改进，也无法考核） 3.度量结果的应用 1)度量结果应用的常见误区 2)不考虑无人度量、用于考核又导致造假、如何处理？ 3)哪些度量指标用于过程改进？ 4)哪些度量指标用于绩效考核？ 4.质量体系构造方法论： 1)如何处理变革中的人的问题？ 2)如何正视研发管理体系优化导致的短期绩效下降？ 3)如何分步实施研发管理体系优化？ 4)研发管理体系优化3步曲（现状诊断、设计、推行） 5)研发体系优化成功的关键要素 6)实例讲解：分享历史近10家企业研发管理体系优化过程、遇到问题和解决方法 7)高层领导在研发体系优化中的关键作用 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ ◇研发管理师资：Don：研发管理咨询资深顾问　INCOSE （国际系统工程师联合会www.incose.org）会员 ■专业背景：十多年高科技企业的研发与管理实践经验，在某著名高科技企业工作期间，先后担当项目经理、系统工程师、产品经理、软件部经理；先后作为三个产品的主任系统工程师，带领系统分析团队开展客户需求调研、产品特性定义和详细的需求分解与分配等端到端的需求管理工作，奠定了产品市场的成功；长期与国际顶尖咨询顾问一起工作，全程参与该公司研发管理变革项目。曾驻印度工作一年半，先后负责四个合作项目（合作方分别为：BFL、Infosys）的实施，全程参与印度研究所CMM四级认证过程；对业务导向的研发质量管理体系的构建有深入地研究。 ■研发管理咨询经验：曾作为项目总监或经理主导了10多个研发管理咨询项目，帮助这些企业全面建立研发管理体系（流程、组织、绩效），有效地提升了这些公司的研发效率和创新能力： 1)华大电子 2)超图软件 3)上海格尔 4)网易 5)重庆奥普泰 6)佳讯飞鸿 7)广联达软件 8)京信通信 9)华胜天成 10)信利半导体 ■研发管理培训经验：曾为海尔、研祥科技、宇通重工、康佳集团、北京移动、北大方正、阿里巴巴、华胜天成、南太电子、网易、富港电子、用友软件、星网锐捷、东软股份、格林威尔、金蝶软件、天马微电子、超图地理、华动飞天、新奥特、信利半导体、郎坤软件、深圳桑菲、久其软件、德信无线、新意科技、沈阳移动、光桥科技、斯特奇、合力金桥、蓝托扑、绿盟科技、建行总行开发中心、成都迈普、上海电信、佳讯飞鸿、德信无线、创维集团、威创日新、TCL、日电电子、展讯通信、易思科技、盛大网络、威科姆科技、协同集团、成都索贝、重庆奥普泰、京信通信、汇川技术、亿力吉奥、迈瑞医疗、同方威视、大唐移动、中软国际、北大方正、思源电气、南京华瑞杰、联想网域、天津通广、兴唐通信、寿力亚洲、浪潮计算机、上海华虹、浦发银行、恒宝股份、武大吉奥、广东电信研究院、华宁电子、三安光电、广西博联、东方通信、北京拓明等100多家企业提供了专业的研发管理培训，涉及的行业包括通信、软件、互联网、家电、运营商、芯片等。 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ 会务组织：中国商业培训网深圳报名热线：０７５５- - ６１２８２５７１北京报名热线: ０１０- - ８１６７５２６７上海报名热线: ０２１- - ５１８７３７０８客服工作 Q Q : １０７８８６１１１８ ▲请将以下报名表内容填写后发送到：chinasypx(a)foxmail.xn--com-s18docw0dhtoqp48a05g9vuvzhmss763etxf01o3s3g! ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ ◇ <<研发质量管理>> 报名回执参加地点: □北京 □上海 □深圳（选中请打“√”）公司名称：______________________________________________企业规模/人数__________ 1. 姓名：__________ 职位：___________ 联系方式_________________ 2. 姓名：__________ 职位：___________ 联系方式_________________ 3. 姓名：__________ 职位：___________ 联系方式_________________ 4. 姓名：__________ 职位：___________ 联系方式_________________ 补充参会人____________________________________ 联系人资料：姓名：_________________部门：_____________________ 职位：___________________ 电话：________________ 传真：_____________________ 电邮：___________________ 付款资料： □电汇 □转账 □现金支票请将报名表填写完整E-mail至我方即可。我方收到报名表后，将以电话、传真或E-mail 等方式确认收到报名表。注意：请在培训之前三个工作日内将报名表回传，本地客户可培训当天现场交费，外地客户请提前转帐,课前一周另行发送详细会务安排。

13 years, 8 months

1
0
0 0

120945-linaro-mm-sig

by 注塑★零缺陷★技术

ע��ȱ�ݸ߼��ް� ʱ��ص㣺04��14-15��Ϻ� 04��21-22�� 04��28-29�ձ�� 06��09-10��Ϻ� 06��16-17�� 06��29-30�ձ�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� ��ڿζ��ע��ҵ�ܾ��ע�ܳ��ܡ�ע�ܲ��/��ܡ�ע��Ʒ�ʾ��/��ܡ�ע�� ̾��/��ܡ�ע��ģ��ʦ��ע��ʦ��ע��Ʒ�ʹ��ʦ��ע��鳤/��/��Ա�� շѱ�׼��2800 /�ˣ��Ϸѡ��ͼ��ȣ� �ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� ע��о��ָ��Ʒ��ȱ�ݺ��쳣��󣻳��ע�ܹ��߽�ƾ��鴦�� äĿ��ʱ�䳤��ԭ��˷Ѵ󣬶�һЩ��ȱ��ѧϵͳ�ط��ע�ܼӹ��һ��֪ʶ��㡢�� ǿ��ҵ��ƾ��ǲ��ġ�"ע��ȱ��ԭ��"�߼�ѧ��רΪѧϰ�� ע��ȱ�ݺ��쳣��⴦��߷��/��ע�ܼ��/��Ա��衣 �� 1.��ע�ܳ��רҵѵ��ý�壬ȫ�漯�й��ע�ܳ��͹��ա�ע�ܳ��ͻ�е��ܽ�� ҵ��ר�Һ�ѧ�ߵ��ǻ��뾭�飻 2.�߶��ܻ��Ļ��ʽ��ý��ƽ̨��ͬʱ��ͼƬ��ֱ��Ч�� 3.��΢�۵�ȫ��λ��̵Ķ�̬��ʾ��ȫ��չ�ֳ��ֳ��ܿ�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� ɫ�� 1. ȫ��ں�ģ�;��ע��ֳ��ܣ�Ϊ��ҵ��ģ��ע�ܵļ��ר�ҡ�ѧԱ ��Դ��Ʒ�μӿγ̣��γ��ѡ��д��Եİ��ϸ�� 2. ��ע�ܳ��רҵѵ~��ý�壬ȫ�漯�й��ע��ģ�ߡ�ע�ܳ��͹��ա�ע�� ͻ�е��ϲ��Ϸ��ҵ��ר�Һ�ѧ�ߵ��뾭�飻 3. �߶��ܻ��Ľ��ʽ��ý��ƽ̨��ͬʱ��ͼƬ��ֱ��Ч�� 4. ��΢�۵�ȫ��λ��̵Ķ�̬��ʾ��ȫ��չ�ֳ��ֳ��ܿ��ݡ� �ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� ݣ� ��T�� һ��֣�ע�ܳ��͹��ջ�� 1.�¶ȡ�ѹ��ٶ��ȴ��Ƶ�Ŀ�ġ�� 2.ע�ܻ��趨�ĵ��Ӱ�칤��Ʒ�ʣ� 3.�Ż��ݸ˿��趨�� 4.��γ��α�ѹ��ƣ��ᾧ��ǽᾧ��/��ά��Թ��ռ�Ʒ�ʵ�Ӱ�죻 5.��Ӧ��ȴ�ٶȡ��ܼ�Ʒ�ʵ�Ӱ�죻 6.��ѧ��ı�ճ�ȣ��/��ά��ϵ�� 7.��עϵͳ��ȴϵͳ��ģ�߽ṹ��ע�ܹ��֮��Ĺ�ϵ�� T�� ڶ��֣�ģ��ֳ��Բ� ��ס��ˮ��ģ��ë�ߡ��۽Ӻۡ��˿��ۡ��ս��Ρ��/��ѡ��ߴ糬��� ע��ԭ��Լ��ģ��ơ��͹��տ��ơ��Ʒ��Ƽ��ϲ��ϵȷ��֮�� Բߡ� 1. ע�ܼ��ܱ�ȱ��ģ��ԭ��Բߣ� 2. ��棨ë�ߣ��ԭ��Բߣ� 3. ע�ܼ��ˮ��ף��ݣ��ԭ��Բߣ� 4. ��ƣ��ϻ��ˮ��ս��Ƶ�ԭ��Բߣ� 5. ע�ܼ��ˮ��ơ��ƣ��ۣ��ԭ��Բߣ� 6. ע�ܼ��ˮ�ƣ��۽Ӻۣ��ƣ��ƣ��ԭ��Բߣ� 7. ע�ܼ��ƣ��ѣ��ף��ԭ��Բߣ� 8. ע�ܼ��ɫ���ɫ��ڵ��ԭ��Բߣ� 9. ע�ܼ��Ρ��Ӧ��ѵ�ԭ��Բߣ� 10. ע�ܼ��ߴ�ƫ��ԭ��Բߣ� 11. ע�ܼ�ճģ��ϻ��ˣ��ϰ׵�ԭ��Բߣ� 12. ע�ܼ�͸��Ȳ��㡢ǿ�Ȳ��㣨��ϣ��ԭ��Բߣ� 13. ע�ܼ��ϰߡ��Ƥ��ֲ㣩��ԭ��Բߣ� 14. ע�ܼ��Ƕ��ԭ��Բߣ� 15. ��ѣ��飩��©��ˮ��˿��ģ��ѵ�ԭ��ƴ�ʩ�� 16. ��CAEģ��ٵ��Ч��ע��ֳ��⡣ ��T�� ֣�ģ��Ż��ʹ�� 1. ע��ģ�ߵĽṹ��ɡ��༰��ܣ� 2. ��עϵͳ��ڡ��Ͼ��ȣ��Ż��ƣ� 3. ��ȴϵͳ��ˮ·��ˮƬ��Ͳ�ȣ��Ż��ƣ� 4. ��ˮ�ʵ��趨�� 5. ��עϵͳ��ȴϵͳ��ģ�߽ṹ��ע�ܹ��֮��Ĺ�ϵ�� 6. ģ�ߵİ�װ��Թ��ά�� 7. ��CAEģ��ģ��Ż��ơ� ��T�� Ĳ��֣�ģ��¹�� 1. ��Ӧ�ü�� 2.˫ɫ��ͼ��Ӧ�ü�� 3. ��帨��ͼ��Ӧ�ü�� 岿�֣�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� :�� й��ܳ�ע�ܼ��ģ��Ż��ѵʵսר�ң�˶ʿ��Ⱥ��¡�̨��󡢴� ��ع��꣬��ι��ʦ��ܡ��ְ��һ�߶��򣬲��ѯ�� л��˷ḻ�ľ��飬��ע��ȱ��ԭ��ģ��Ż��ע�ܻ�е�� ϲ��Ͼ��൱�ļ��ף��γ��˶��ɫ��ʵ��ģ��/ע�ܼ��ϵ��ʦʵ�� ḻ��ڹ��оٴ��ر�ǿ��ʵ��ԺͿɲ��ԣ��Ա�ĺ��𾴡� ��ʦΪ��ҵ��ʵ��Ҫ��Ⱥ�ٰ��ע�ܼ��ģ��Ż��ѵ�� γ̹��600�ೡ��ѵ��ҵ4000��ң��һ��ҵ��˲ţ�Ŀǰ��Ҫ�ֲ�� ڡ��㶫��ҵ��Ϊ��ҵ��ѵ��ͻ��ף� ʵʵ��Ϊ��ҵ��⡣ �ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� .��.��.֯��ŵ˹��ҵ��ѯ��޹�˾ �� .�� .��.��.�ߣ��- - ��.��.��.�� С�� .�� .��.��.��: �� - - ��.��.��.�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� ��뽫��±��д��͵��chinasypx@foxmail.com��Ա��ڵ�һʱ��ϵ! �� ִ �� ҵ�λ��_______�˱�.��μӡ�ע��ȱ�ݸ߼��ްࡷ ��λ��ƣ�_____________________________________________ �� ϵ �ˣ�_____________ ��ϵ�绰��_______________ �ֻ��_______________ ͼ�Ĵ��棺_____________ ��䣺_____________________________________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ã�___________ Ԫ�� ʽ�� 𡡡� ֧ Ʊ�� ת �ʡ��ѡ��򡰡̡�� ע: 1.��ѱ��ִ��ú�ش��˾��Ϊȷ��,��ٴε绰ȷ��! 2.��γ̿ɸ��ҵ��Ҫ��֯��ѵ��

13 years, 8 months

1
0
0 0

[PATCHv7 0/9] ARM: DMA-mapping framework redesign

by Marek Szyprowski

Hello, This is yet another update on my works DMA-mapping framework redesign for ARM architecture. It includes a few minor cleanup and fixes reported by Konrad Rzeszutek Wilk and Krishna Reddy. This version uses vmalloc for allocating page pointers array if it is larger than PAGE_SIZE. The chained allocation which fits inside a set of PAGE_SIZE units will be added later, once the base patches are merged. Like the previous version, this patchset is also based on the generic, cross-arch dma-mapping redesign patches posted in the "[PATCH 00/14] DMA-mapping framework redesign preparation" thread: http://www.spinics.net/lists/linux-sh/msg09777.html All patches have been now rebased onto v3.3-rc5 kernel. All the code has been tested on Samsung Exynos4 'UniversalC210' board with IOMMU driver posted by KyongHo Cho. History of the development: v1: (initial version of the DMA-mapping redesign patches): http://www.spinics.net/lists/linux-mm/msg21241.html v2: http://lists.linaro.org/pipermail/linaro-mm-sig/2011-September/000571.html http://lists.linaro.org/pipermail/linaro-mm-sig/2011-September/000577.html v3: http://www.spinics.net/lists/linux-mm/msg25490.html v4 and v5: http://www.spinics.net/lists/arm-kernel/msg151147.html http://www.spinics.net/lists/arm-kernel/msg154889.html v6: http://www.spinics.net/lists/linux-mm/msg29903.html Best regards -- Marek Szyprowski Samsung Poland R&D Center Patch summary: Marek Szyprowski (9): ARM: dma-mapping: introduce ARM_DMA_ERROR constant ARM: dma-mapping: use pr_* instread of printk ARM: dma-mapping: remove offset parameter to prepare for generic dma_ops ARM: dma-mapping: use asm-generic/dma-mapping-common.h ARM: dma-mapping: implement dma sg methods on top of any generic dma ops ARM: dma-mapping: move all dma bounce code to separate dma ops structure ARM: dma-mapping: remove redundant code and cleanup ARM: dma-mapping: use alloc, mmap, free from dma_ops ARM: dma-mapping: add support for IOMMU mapper arch/arm/Kconfig | 9 + arch/arm/common/dmabounce.c | 84 +++- arch/arm/include/asm/device.h | 4 + arch/arm/include/asm/dma-iommu.h | 34 ++ arch/arm/include/asm/dma-mapping.h | 407 ++++----------- arch/arm/mm/dma-mapping.c | 1013 ++++++++++++++++++++++++++++++------ arch/arm/mm/vmregion.h | 2 +- 7 files changed, 1088 insertions(+), 465 deletions(-) create mode 100644 arch/arm/include/asm/dma-iommu.h -- 1.7.1.569.g6f426

13 years, 8 months

6
38
0 0

366583-linaro-mm-sig

by 注塑★零缺陷★技术

ע��ȱ�ݸ߼��ް� ʱ��ص㣺04��14-15��Ϻ� 04��21-22�� 04��28-29�ձ�� 06��09-10��Ϻ� 06��16-17�� 06��29-30�ձ�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� ��ڿζ��ע��ҵ�ܾ��ע�ܳ��ܡ�ע�ܲ��/��ܡ�ע��Ʒ�ʾ��/��ܡ�ע�� ̾��/��ܡ�ע��ģ��ʦ��ע��ʦ��ע��Ʒ�ʹ��ʦ��ע��鳤/��/��Ա�� շѱ�׼��2800 /�ˣ��Ϸѡ��ͼ��ȣ� �ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� ע��о��ָ��Ʒ��ȱ�ݺ��쳣��󣻳��ע�ܹ��߽�ƾ��鴦�� äĿ��ʱ�䳤��ԭ��˷Ѵ󣬶�һЩ��ȱ��ѧϵͳ�ط��ע�ܼӹ��һ��֪ʶ��㡢�� ǿ��ҵ��ƾ��ǲ��ġ�"ע��ȱ��ԭ��"�߼�ѧ��רΪѧϰ�� ע��ȱ�ݺ��쳣��⴦��߷��/��ע�ܼ��/��Ա��衣 �� 1.��ע�ܳ��רҵѵ��ý�壬ȫ�漯�й��ע�ܳ��͹��ա�ע�ܳ��ͻ�е��ܽ�� ҵ��ר�Һ�ѧ�ߵ��ǻ��뾭�飻 2.�߶��ܻ��Ļ��ʽ��ý��ƽ̨��ͬʱ��ͼƬ��ֱ��Ч�� 3.��΢�۵�ȫ��λ��̵Ķ�̬��ʾ��ȫ��չ�ֳ��ֳ��ܿ�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� ɫ�� 1. ȫ��ں�ģ�;��ע��ֳ��ܣ�Ϊ��ҵ��ģ��ע�ܵļ��ר�ҡ�ѧԱ ��Դ��Ʒ�μӿγ̣��γ��ѡ��д��Եİ��ϸ�� 2. ��ע�ܳ��רҵѵ~��ý�壬ȫ�漯�й��ע��ģ�ߡ�ע�ܳ��͹��ա�ע�� ͻ�е��ϲ��Ϸ��ҵ��ר�Һ�ѧ�ߵ��뾭�飻 3. �߶��ܻ��Ľ��ʽ��ý��ƽ̨��ͬʱ��ͼƬ��ֱ��Ч�� 4. ��΢�۵�ȫ��λ��̵Ķ�̬��ʾ��ȫ��չ�ֳ��ֳ��ܿ��ݡ� �ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� ݣ� ��T�� һ��֣�ע�ܳ��͹��ջ�� 1.�¶ȡ�ѹ��ٶ��ȴ��Ƶ�Ŀ�ġ�� 2.ע�ܻ��趨�ĵ��Ӱ�칤��Ʒ�ʣ� 3.�Ż��ݸ˿��趨�� 4.��γ��α�ѹ��ƣ��ᾧ��ǽᾧ��/��ά��Թ��ռ�Ʒ�ʵ�Ӱ�죻 5.��Ӧ��ȴ�ٶȡ��ܼ�Ʒ�ʵ�Ӱ�죻 6.��ѧ��ı�ճ�ȣ��/��ά��ϵ�� 7.��עϵͳ��ȴϵͳ��ģ�߽ṹ��ע�ܹ��֮��Ĺ�ϵ�� T�� ڶ��֣�ģ��ֳ��Բ� ��ס��ˮ��ģ��ë�ߡ��۽Ӻۡ��˿��ۡ��ս��Ρ��/��ѡ��ߴ糬��� ע��ԭ��Լ��ģ��ơ��͹��տ��ơ��Ʒ��Ƽ��ϲ��ϵȷ��֮�� Բߡ� 1. ע�ܼ��ܱ�ȱ��ģ��ԭ��Բߣ� 2. ��棨ë�ߣ��ԭ��Բߣ� 3. ע�ܼ��ˮ��ף��ݣ��ԭ��Բߣ� 4. ��ƣ��ϻ��ˮ��ս��Ƶ�ԭ��Բߣ� 5. ע�ܼ��ˮ��ơ��ƣ��ۣ��ԭ��Բߣ� 6. ע�ܼ��ˮ�ƣ��۽Ӻۣ��ƣ��ƣ��ԭ��Բߣ� 7. ע�ܼ��ƣ��ѣ��ף��ԭ��Բߣ� 8. ע�ܼ��ɫ���ɫ��ڵ��ԭ��Բߣ� 9. ע�ܼ��Ρ��Ӧ��ѵ�ԭ��Բߣ� 10. ע�ܼ��ߴ�ƫ��ԭ��Բߣ� 11. ע�ܼ�ճģ��ϻ��ˣ��ϰ׵�ԭ��Բߣ� 12. ע�ܼ�͸��Ȳ��㡢ǿ�Ȳ��㣨��ϣ��ԭ��Բߣ� 13. ע�ܼ��ϰߡ��Ƥ��ֲ㣩��ԭ��Բߣ� 14. ע�ܼ��Ƕ��ԭ��Բߣ� 15. ��ѣ��飩��©��ˮ��˿��ģ��ѵ�ԭ��ƴ�ʩ�� 16. ��CAEģ��ٵ��Ч��ע��ֳ��⡣ ��T�� ֣�ģ��Ż��ʹ�� 1. ע��ģ�ߵĽṹ��ɡ��༰��ܣ� 2. ��עϵͳ��ڡ��Ͼ��ȣ��Ż��ƣ� 3. ��ȴϵͳ��ˮ·��ˮƬ��Ͳ�ȣ��Ż��ƣ� 4. ��ˮ�ʵ��趨�� 5. ��עϵͳ��ȴϵͳ��ģ�߽ṹ��ע�ܹ��֮��Ĺ�ϵ�� 6. ģ�ߵİ�װ��Թ��ά�� 7. ��CAEģ��ģ��Ż��ơ� ��T�� Ĳ��֣�ģ��¹�� 1. ��Ӧ�ü�� 2.˫ɫ��ͼ��Ӧ�ü�� 3. ��帨��ͼ��Ӧ�ü�� 岿�֣�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� :�� й��ܳ�ע�ܼ��ģ��Ż��ѵʵսר�ң�˶ʿ��Ⱥ��¡�̨��󡢴� ��ع��꣬��ι��ʦ��ܡ��ְ��һ�߶��򣬲��ѯ�� л��˷ḻ�ľ��飬��ע��ȱ��ԭ��ģ��Ż��ע�ܻ�е�� ϲ��Ͼ��൱�ļ��ף��γ��˶��ɫ��ʵ��ģ��/ע�ܼ��ϵ��ʦʵ�� ḻ��ڹ��оٴ��ر�ǿ��ʵ��ԺͿɲ��ԣ��Ա�ĺ��𾴡� ��ʦΪ��ҵ��ʵ��Ҫ��Ⱥ�ٰ��ע�ܼ��ģ��Ż��ѵ�� γ̹��600�ೡ��ѵ��ҵ4000��ң��һ��ҵ��˲ţ�Ŀǰ��Ҫ�ֲ�� ڡ��㶫��ҵ��Ϊ��ҵ��ѵ��ͻ��ף� ʵʵ��Ϊ��ҵ��⡣ �ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� .��.��.֯��ŵ˹��ҵ��ѯ��޹�˾ �� .�� .��.��.�ߣ��- - ��.��.��.�� С�� .�� .��.��.��: �� - - ��.��.��.�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� ��뽫��±��д��͵��chinasypx@foxmail.com��Ա��ڵ�һʱ��ϵ! �� ִ �� ҵ�λ��_______�˱�.��μӡ�ע��ȱ�ݸ߼��ްࡷ ��λ��ƣ�_____________________________________________ �� ϵ �ˣ�_____________ ��ϵ�绰��_______________ �ֻ��_______________ ͼ�Ĵ��棺_____________ ��䣺_____________________________________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ã�___________ Ԫ�� ʽ�� 𡡡� ֧ Ʊ�� ת �ʡ��ѡ��򡰡̡�� ע: 1.��ѱ��ִ��ú�ش��˾��Ϊȷ��,��ٴε绰ȷ��! 2.��γ̿ɸ��ҵ��Ҫ��֯��ѵ��

13 years, 8 months

1
0
0 0

[PATCHv2 00/14] DMA-mapping framework redesign preparation

by Marek Szyprowski

Hello everyone, This is an updated version of the DMA-mapping framework redesign preparation patches, which resolves issues pointed by Linus: https://lkml.org/lkml/2012/3/23/305 These patches are the first step to clean up a bit dma-mapping api and introduce support for architecture specific performance improving hints in a generic way. For more information please refer to the thread with the first version of the patches: https://lkml.org/lkml/2011/12/23/97 Best regards Marek Szyprowski Samsung Poland R&D Center Patch summary: Andrzej Pietrasiewicz (8): X86 & IA64: adapt for dma_map_ops changes MIPS: adapt for dma_map_ops changes PowerPC: adapt for dma_map_ops changes SPARC: adapt for dma_map_ops changes Alpha: adapt for dma_map_ops changes SH: adapt for dma_map_ops changes Microblaze: adapt for dma_map_ops changes Unicore32: adapt for dma_map_ops changes Marek Szyprowski (6): common: dma-mapping: introduce alloc_attrs and free_attrs methods Hexagon: adapt for dma_map_ops changes common: dma-mapping: remove old alloc_coherent and free_coherent methods common: dma-mapping: introduce mmap method common: DMA-mapping: add WRITE_COMBINE attribute common: DMA-mapping: add NON-CONSISTENT attribute Documentation/DMA-attributes.txt | 19 +++++++++++++++++++ arch/alpha/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/alpha/kernel/pci-noop.c | 10 ++++++---- arch/alpha/kernel/pci_iommu.c | 10 ++++++---- arch/hexagon/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/hexagon/kernel/dma.c | 9 +++++---- arch/ia64/hp/common/sba_iommu.c | 11 ++++++----- arch/ia64/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/ia64/kernel/pci-swiotlb.c | 14 +++++++++++--- arch/ia64/sn/pci/pci_dma.c | 9 +++++---- arch/microblaze/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/microblaze/kernel/dma.c | 10 ++++++---- arch/mips/cavium-octeon/dma-octeon.c | 12 ++++++------ arch/mips/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/mips/mm/dma-default.c | 8 ++++---- arch/powerpc/include/asm/dma-mapping.h | 24 ++++++++++++++++-------- arch/powerpc/kernel/dma-iommu.c | 10 ++++++---- arch/powerpc/kernel/dma-swiotlb.c | 4 ++-- arch/powerpc/kernel/dma.c | 10 ++++++---- arch/powerpc/kernel/ibmebus.c | 10 ++++++---- arch/powerpc/kernel/vio.c | 14 ++++++++------ arch/powerpc/platforms/cell/iommu.c | 16 +++++++++------- arch/powerpc/platforms/ps3/system-bus.c | 13 +++++++------ arch/sh/include/asm/dma-mapping.h | 28 ++++++++++++++++++---------- arch/sh/kernel/dma-nommu.c | 4 ++-- arch/sh/mm/consistent.c | 6 ++++-- arch/sparc/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/sparc/kernel/iommu.c | 10 ++++++---- arch/sparc/kernel/ioport.c | 18 ++++++++++-------- arch/sparc/kernel/pci_sun4v.c | 9 +++++---- arch/unicore32/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/unicore32/mm/dma-swiotlb.c | 18 ++++++++++++++++-- arch/x86/include/asm/dma-mapping.h | 26 ++++++++++++++++---------- arch/x86/kernel/amd_gart_64.c | 11 ++++++----- arch/x86/kernel/pci-calgary_64.c | 9 +++++---- arch/x86/kernel/pci-dma.c | 3 ++- arch/x86/kernel/pci-nommu.c | 6 +++--- arch/x86/kernel/pci-swiotlb.c | 17 +++++++++++++---- arch/x86/xen/pci-swiotlb-xen.c | 4 ++-- drivers/iommu/amd_iommu.c | 10 ++++++---- drivers/iommu/intel-iommu.c | 9 +++++---- drivers/xen/swiotlb-xen.c | 5 +++-- include/linux/dma-attrs.h | 2 ++ include/linux/dma-mapping.h | 13 +++++++++---- include/xen/swiotlb-xen.h | 6 ++++-- 45 files changed, 355 insertions(+), 198 deletions(-) -- 1.7.1.569.g6f426

13 years, 8 months

7
22
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig