Linaro-mm-sig March 2012

linaro-mm-sig@lists.linaro.org

54 participants
44 discussions

[RFCv2 PATCH 0/9] Integration of videobuf2 with dmabuf

by Tomasz Stanislawski

Hello everyone, This patchset is an incremental patch to patchset created by Sumit Semwal [1]. The patches are dedicated to help find a better solution for support of buffer sharing by V4L2 API. It is expected to start discussion on the final installment for dma-buf in vb2-dma-contig allocator. Current version of the patches contain little documentation. It is going to be fixed after achieving consensus about design for buffer exporting. Moreover the API between vb2-core and the allocator should be revised. The patches were successfully tested to cooperate with EXYNOS DRM driver using DMABUF mechanism. Please note, that the amount of changes to vb2-dma-contig.c was significant making the difference patch very difficult to read. The patchset makes use of dma_get_pages extension for DMA API, which is posted on a top of dma-mapping patches by Marek Szyprowski [4] [5]. The tree, that contains all needed patches, can be found here [6]. 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 [5] http://git.infradead.org/users/kmpark/linux-2.6-samsung/shortlog/refs/heads… [6] http://git.infradead.org/users/kmpark/linux-2.6-samsung/shortlog/refs/heads… Sumit Semwal (1): v4l: vb2: Add dma-contig allocator as dma_buf user Tomasz Stanislawski (8): v4l: vb2: fixes for DMABUF support v4l: vb2-dma-contig: update and code refactoring v4l: add buffer exporting via dmabuf v4l: vb2: add buffer exporting via dmabuf v4l: vb2-dma-contig: add support for DMABUF exporting v4l: vb2-dma-contig: change map/unmap behaviour v4l: fimc: integrate capture i-face with dmabuf v4l: s5p-tv: mixer: integrate with dmabuf drivers/media/video/Kconfig | 1 + drivers/media/video/s5p-fimc/fimc-capture.c | 11 +- drivers/media/video/s5p-tv/Kconfig | 1 + drivers/media/video/s5p-tv/mixer_video.c | 12 +- drivers/media/video/v4l2-compat-ioctl32.c | 1 + drivers/media/video/v4l2-ioctl.c | 11 + drivers/media/video/videobuf2-core.c | 88 +++- drivers/media/video/videobuf2-dma-contig.c | 717 ++++++++++++++++++++++++--- include/linux/videodev2.h | 20 + include/media/v4l2-ioctl.h | 2 + include/media/videobuf2-core.h | 8 +- 11 files changed, 779 insertions(+), 93 deletions(-) -- 1.7.5.4

12 years, 1 month

[PULL REQUEST] DMA-mapping framework redesign preparation patches

by Marek Szyprowski

Hi Stephen, Our patches with DMA-mapping framework redesign proposal have been hanging for over a month with just a few comments. We would like to go further in the development, but first I would like to ask You to give them a try in the linux-next kernel. For everyone interested in this patch series, here is the relevant thread: https://lkml.org/lkml/2011/12/23/97 If there are any problems with our git tree, please contact Marek Szyprowski <m.szyprowski(a)samsung.com> or alternatively Kyungmin Park <kyungmin.park(a)samsung.com>. The following changes since commit 62aa2b537c6f5957afd98e29f96897419ed5ebab: Linux 3.3-rc2 (2012-01-31 13:31:54 -0800) are available in the git repository at: git://git.infradead.org/users/kmpark/linux-samsung dma-mapping-next Andrzej Pietrasiewicz (9): X86: adapt for dma_map_ops changes MIPS: adapt for dma_map_ops changes PowerPC: adapt for dma_map_ops changes IA64: 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 (5): common: dma-mapping: introduce alloc_attrs and free_attrs methods 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/ia64/hp/common/sba_iommu.c | 11 ++++++----- arch/ia64/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/ia64/kernel/pci-swiotlb.c | 9 +++++---- arch/ia64/sn/pci/pci_dma.c | 9 +++++---- arch/microblaze/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/microblaze/kernel/dma.c | 10 ++++++---- 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/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 | 4 ++-- 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 | 12 +++++++----- 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/linux/swiotlb.h | 6 ++++-- include/xen/swiotlb-xen.h | 6 ++++-- lib/swiotlb.c | 5 +++-- 43 files changed, 305 insertions(+), 182 deletions(-) Best regards Marek Szyprowski Samsung Poland R&D Center

12 years, 1 month

120945-linaro-mm-sig

by 消灭▲财务黑洞▲

财务黑洞无情-消灭漏洞有道【培训时间】2012年4月13-14日深圳 4月20-21日上海 4月27-28日北京 6月9-10日深圳 6月15-16日上海 7月6-7日北京【培训对象】公司股东、董事长、经理以及企业其他中高层管理人员。【培训费用】￥2800元/人（提供讲义、午餐、发票、茶点等） ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ 【课程背景】邓老师告诉你：如何发现财务健康的DNA密码如何做到：消灭财务漏洞避免财务黑洞确保经营成果中国企业财务黑洞问题诊断与防范行家，消灭财务黑洞专题研究第一人。用百度搜索“消灭财务漏洞”6个字达260多万条，影响巨大！用谷歌搜索“邓鸿老师”4个字达到1000多万条，是否徒有虚名？培训目标： 1、企业财务黑洞是由多方面因素造成的，财务黑洞的封杀要有专业指导、丰富的实践经验和恰当的方式方法。 2、企业的财务工作好坏不单只是财务部的事情，是企业综合管理水平的体现。邓老师以自己多年所经历的，许多老板用昂贵的金钱甚至是生命为代价所换来的丰富案例，策您警醒，让你吃人家之堑长自己之智。 3、经常听到会计人员抱怨：老板不重视财务。你不妨请你的老板来听一场邓老师的《消灭财务黑洞》的课程，也许是你送给老板的最好礼物！也是给自己工作的最好帮助；经常听到我们的会计抱怨：同事不配合、不理解、不支持我们的财务工作。你不妨建议老板请邓老师去给你的公司全体员工上一堂《消灭财务黑洞》的课程，你的工作环境是不是会得到显著改善？你不妨试一试？课程100%为落地可操作的方法与工具，绝对实战、实效、实用！授课方式：专题讲授、互动交流、案例分析 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ 【课程大纲】序言： 1、什么是黑洞？ 2、什么是财务黑洞？ 3、织网与补网一、财务黑洞的八大原发病毒（一）收款黑洞 1、常规收款手段为什么失效？ 2、货款要不回为什么还要倒赔钱？ 3、案例：合同纠纷背后的货款欺诈陷阱 4、消灭财务黑洞： A、结合案件一些证据和日常单据明白问题在哪里？ B、如何解决和防范诊断出来的问题？（二）付款黑洞 1、公司有没有资金紧张的时候？资金紧张怎么办？你是怎么做的？为什么说你的做法是错误的，是在自己制造财务黑洞，或者说是自掘陷阱！ 2、错误表现在两个极端：（1）一个极端是忽悠、再忽悠（有的）到骗；（2）另一个极端是扛、死扛、扛到死，把自己弄得很悲壮 3、消灭财务黑洞：（1）惨淡经营、死扛、扛到死有没有必要？（2）提供两种解决办法，供参考：办法一、你能不能挑出可以帮助你暂时渡过难关的那些供应商？暂时继续占用一下人家的资金。办法二、有没有第三条路可走？第三条路怎么走？案例：企业暂停经营撇债（三）税务黑洞 1、内外两套账，为什么税务一查一个准？ 2、是什么原因？因为有三道坎迈不过去：第一道坎：合同与账本，两张皮不黏！第二道坎：资金账户似迷宫，剪不断来理还乱第三道坎：账实要相符，神仙也犯难 3、面对三道坎，你是不是就束手无策？消灭财务黑洞，道在哪里？案例：桌上放收款单据的故事的后续故事（四）投资黑洞 1、投资前-- 练就火眼金睛问题：（1）没有看清合作方，搞清楚其真实意图，让表面现象所迷惑；（2）对产权状况不清，盲目投资；（3）公司收购的两大猫腻如何识破猫腻？避免陷于巨大财务黑洞？ 2、投资合作中-- 给我一双慧眼，不要聪明人办傻事问题：（1）是投资入股还是借款？（2）问题形成后处理方法要得当 3、投资后-- 半睁半闭眼睛，要吃小亏避免上大当。（五）融资黑洞 1、不懂融资，要多作功课，不要犯吃饭不看菜，裁衣不量体常识错误。表现： 1、喜欢包装，“临时抱佛脚” 2、盲目相信中介，迷信能人和关系功课之一：企业所处的发展阶段不同融资渠道有别功课之二：用好企业现有的有效资源是融资的关键。功课之三：认识资金和其能够提供的金融产品，不要做瞎子摸象 2、为了融资而融资，一条道走到黑表现： a、抛开实业玩概念； b、盲目相信过度包装。 3、企业在融资时如何防骗？（六）沟通黑洞 1、采购绑架财务 2、销售尾巴何其多？某物业管理公司的案例三招解决公司沟通黑洞（七）成本黑洞 1、企业成本核算的基本要求 2、案例：原材料成本 X 2 = 销售价的故事（八）管理黑洞 1、会计由谁来招聘？人事部和老板招聘的会计有什么错？ 2、会计工作能不能胜任由谁来考察？ 3、会计经常换有什么严重后果？ 4、账实严重不相符谁之过？ 5、案例：（1）逾期未提交出口单据，税局认定“内销”，补税和滞纳金等500多万元。（2）单据不齐，1000余万出口退税遇阻。二、财务黑洞根源探究 1、曲突徙薪亡恩泽，焦头烂额为上客。 ----忙救火，疏预防 2、麦克唐纳牧师的故事 ----只知其一，不知其二；或者说：知其然不知其所以然。 3、犯用人之忌！（1）用老乡 a、老乡老乡，背后一枪 b、老乡靠得住，母猪能上树（2）用老婆老婆做出纳，管住了钱还有什么没有管住？ 4、四大认识误区最害人，现在明白来得及。三、消灭财务黑洞之道（一）练就消灭财务黑洞的上乘功法 1、五个前提条件 2、织网与补网，你做何选择？ 3、审查方法介绍（1）业务循环审查法（2）五大审查技术方法介绍（二）四级定位防范财务黑洞咨询系统介绍 A、消灭财务黑洞咨询服务方法 1、发现财务黑洞是一项复杂的系统专业工程 2、抓住8大高发点，以点带面，寻根探源，让财务黑洞无可逃遁。 B、四级定位图介绍?? ? 1级：人（财务）行，制度、流程也行解决办法：执行偏差的案例 2级：人（财务）行，制度流程不行 3级：人（财务）不行，制度流程行 4级：人（财务）不行，制度流程也不行案例：理清了一团乱麻四、警惕财务黑洞的变种病毒案例1：外派黑洞：养虎为患案例2：材料黑洞：空运费大于机器价值案例案例3：保密黑洞：老板被敲诈案例4：收购公司黑洞案例5：某公司海外上市劫 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ 【讲师介绍】邓鸿中国企业财务黑洞问题诊断与防范行家，消灭财务黑洞专题研究第一人 --深圳市福中达投资控股有限公司财务总监 --深圳市多丽电子商务产业园财务顾问 --亚太集团会计师事务所有限公司深圳所合伙人亚太集团会计师事务所有限公司深圳所注册会计师、执业年限12年、会计、审计、财务管理岗位及顾问工作从业年限28年。资深注册会计师、香港城市大学国际会计硕士，亚太集团会计师事务所有限公司深圳总部合伙人。企业各类财务漏洞、财务黑洞问题的咨询诊断与防范行家。资深财务管理、审计、咨询从业者，担任过多家企业财务顾问，从事企业财务管理、咨询和投融资工作达二十多年, 具有较强的综合协调沟通问题能力，主持及参与的项目达三位数以上，具有较为丰富的财务管理、企业投融资、审计、评估、税收筹划、财务税收顾问经验。 ? ? 熟悉国家财务制度和相关政策法规，熟悉国家税收法律法规，熟悉公司改制及上市制度及程序、熟悉财政、税务、工商、劳动人事等政府各部门办事程序及方法，熟悉银行等金融机构投融资技巧并有一定的投融资渠道。有较强的文字功力，能将工作中发现的问题及改进办法整理发表，曾在中国著名《财经》杂志、《会计月刊》、《公司金融》等报刊杂志上发表百多篇文章，《公司金融》杂志更是开辟专栏连载财务黑洞研究方面的系列文章。本人的经验总结性文章《财务黑洞案例实录》在中国会计界最高学府“国家会计学院”“中国会计视野”网站发表一天就达2500多浏览量，创该站记录，时至今日热度不减，第二天就已被收入“中国会计视野”精品文库，仅该网站网友留言就达200多条，转载网站达几万家，上至企业老板，下至大学学生都将该文当做教科书，备受关注和引发热议。在《公司金融》（国内统一刊号：CN44-1563/F 国际标准连续出版刊号：ISSN 1671-6728）杂志上连载的文章有： 1、《私募融资背后的商业谎言》 2009年10月1日总第42期 2、财务黑洞启示录（一）--《内外账的老思维要不得了》 2009年11月1日总第44期 3、财务黑洞启示录（二）--《单据丢失酝酿严重税务后果》2009年11月16日总第45期 4、财务黑洞启示录（三）--《表述模糊引发十年官司》 2009年12月1日总第46期 5、财务黑洞启示录（四）--《合同纠纷背后的货款欺诈陷阱》2010年1月1日总第48期 6、财务黑洞启示录（五）--《友情信任反成投资陷阱》 2010年1月16日总第49期 7、财务黑洞启示录（六）--《资产收购中隐藏的猫腻》 2010年2月1日总第50期培训风格 1.邓鸿老师有很强的现场亲和力、敏锐的学员洞察力以及丰富的授课经验，了解成年人学习的特点，把复杂的问题说得通俗易懂。 2.授课风格既稳重，但又不乏幽默和风趣，采用多样化的互动授课方式，营造轻松愉快的学习气氛，充分调动学员的听课积极性。 3.授课内容既有理论深度，又注重实用效果，使学员在培训后，能在工作中解决实际问题，体现培训真正的价值。培训现场互动性很强，有很强的控场能力，倡导“家常式的互动性强”的授课理念。邓老师提倡实用、实在、实际、实战的培训风格，用专业、专注、方向、方法凝聚学员的满意。 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ 深.圳报.名.热.线：０７５５- - ６１.２８.２５.７１陈小姐上.海报.名.热.线: ０２１- - ５１.８７.３７.０８张先生温馨提示:(每期限40人,如需参加请提前预定) QQ订位!-1078861118 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ ▲请将以下报名表内容填写后发送到：chinasypx(a)foxmail.xn--com-s18docw0dhtoqp48a05g9vuvzhmss763etxf01o3s3g! 　　　　　　　　　　　报名回执表　　我单位共_______人报.名参加财务黑洞无情-消灭漏洞有道 4月13-14日深圳□ 4月20-21日上海□ 4月27-28日北京□ 单位名称：_____________________________________________ 联系人：_____________ 联系电话：_______________ 手机：_______________ 图文传真：_____________ 电子信箱：_____________________________________ 参会人：_____________ 参会人：_____________ 参会人：_____________ 参会人：_____________ 参会人：_____________ 参会人：_____________ 总费用：___________ 元整。付款方式：□ 现金　□ 支票　□ 转帐　　（请选择打“√”）备注: 1.请您把报名回执认真填好后回传我司，为确保您报名无误,请您再次电话确认! 2.本课程可根据企业需要组织内训。

12 years, 1 month

注塑★ 零缺陷★

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.��γ̿ɸ��ҵ��Ҫ��֯��ѵ��

12 years, 1 month

[PATCH] drm: base prime/dma-buf support (v5)

by Dave Airlie

From: Dave Airlie <airlied(a)redhat.com> This adds the basic drm dma-buf interface layer, called PRIME, The main APIs exposed to userspace allow translating a 32-bit object handle to a file descriptor, and a file descriptor to a 32-bit object handle. The flags value is currently limited to O_CLOEXEC. Acknowledgements: Daniel Vetter: lots of review Rob Clark: cleaned up lots of the internals and did lifetime review. v2: rename some functions after Chris preferred a green shed fix IS_ERR_OR_NULL -> IS_ERR v3: Fix Ville pointed out using buffer + kmalloc v4: add locking as per ickle review v5: allow re-exporting the original dma-buf (Daniel) Signed-off-by: Dave Airlie <airlied(a)redhat.com> --- drivers/gpu/drm/Kconfig | 1 + drivers/gpu/drm/Makefile | 2 +- drivers/gpu/drm/drm_drv.c | 4 + drivers/gpu/drm/drm_fops.c | 7 + drivers/gpu/drm/drm_gem.c | 9 ++ drivers/gpu/drm/drm_prime.c | 299 +++++++++++++++++++++++++++++++++++++++++++ include/drm/drm.h | 14 ++- include/drm/drmP.h | 62 +++++++++ 8 files changed, 396 insertions(+), 2 deletions(-) create mode 100644 drivers/gpu/drm/drm_prime.c diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig index cc11488..e354bc0 100644 --- a/drivers/gpu/drm/Kconfig +++ b/drivers/gpu/drm/Kconfig @@ -9,6 +9,7 @@ menuconfig DRM depends on (AGP || AGP=n) && !EMULATED_CMPXCHG && MMU select I2C select I2C_ALGOBIT + select DMA_SHARED_BUFFER help Kernel-level support for the Direct Rendering Infrastructure (DRI) introduced in XFree86 4.0. If you say Y here, you need to select diff --git a/drivers/gpu/drm/Makefile b/drivers/gpu/drm/Makefile index a858532..c20da5b 100644 --- a/drivers/gpu/drm/Makefile +++ b/drivers/gpu/drm/Makefile @@ -12,7 +12,7 @@ drm-y := drm_auth.o drm_buffer.o drm_bufs.o drm_cache.o \ drm_platform.o drm_sysfs.o drm_hashtab.o drm_mm.o \ drm_crtc.o drm_modes.o drm_edid.o \ drm_info.o drm_debugfs.o drm_encoder_slave.o \ - drm_trace_points.o drm_global.o + drm_trace_points.o drm_global.o drm_prime.o drm-$(CONFIG_COMPAT) += drm_ioc32.o diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c index 0b65fbc..6116e3b 100644 --- a/drivers/gpu/drm/drm_drv.c +++ b/drivers/gpu/drm/drm_drv.c @@ -136,6 +136,10 @@ static struct drm_ioctl_desc drm_ioctls[] = { DRM_IOCTL_DEF(DRM_IOCTL_GEM_OPEN, drm_gem_open_ioctl, DRM_AUTH|DRM_UNLOCKED), DRM_IOCTL_DEF(DRM_IOCTL_MODE_GETRESOURCES, drm_mode_getresources, DRM_CONTROL_ALLOW|DRM_UNLOCKED), + + DRM_IOCTL_DEF(DRM_IOCTL_PRIME_HANDLE_TO_FD, drm_prime_handle_to_fd_ioctl, DRM_AUTH|DRM_UNLOCKED), + DRM_IOCTL_DEF(DRM_IOCTL_PRIME_FD_TO_HANDLE, drm_prime_fd_to_handle_ioctl, DRM_AUTH|DRM_UNLOCKED), + DRM_IOCTL_DEF(DRM_IOCTL_MODE_GETPLANERESOURCES, drm_mode_getplane_res, DRM_MASTER|DRM_CONTROL_ALLOW|DRM_UNLOCKED), DRM_IOCTL_DEF(DRM_IOCTL_MODE_GETCRTC, drm_mode_getcrtc, DRM_CONTROL_ALLOW|DRM_UNLOCKED), DRM_IOCTL_DEF(DRM_IOCTL_MODE_SETCRTC, drm_mode_setcrtc, DRM_MASTER|DRM_CONTROL_ALLOW|DRM_UNLOCKED), diff --git a/drivers/gpu/drm/drm_fops.c b/drivers/gpu/drm/drm_fops.c index 7348a3d..cdfbf27 100644 --- a/drivers/gpu/drm/drm_fops.c +++ b/drivers/gpu/drm/drm_fops.c @@ -271,6 +271,9 @@ static int drm_open_helper(struct inode *inode, struct file *filp, if (dev->driver->driver_features & DRIVER_GEM) drm_gem_open(dev, priv); + if (drm_core_check_feature(dev, DRIVER_PRIME)) + drm_prime_init_file_private(&priv->prime); + if (dev->driver->open) { ret = dev->driver->open(dev, priv); if (ret < 0) @@ -571,6 +574,10 @@ int drm_release(struct inode *inode, struct file *filp) if (dev->driver->postclose) dev->driver->postclose(dev, file_priv); + + if (drm_core_check_feature(dev, DRIVER_PRIME)) + drm_prime_destroy_file_private(&file_priv->prime); + kfree(file_priv); /* ======================================================== diff --git a/drivers/gpu/drm/drm_gem.c b/drivers/gpu/drm/drm_gem.c index 0ef358e..83114b5 100644 --- a/drivers/gpu/drm/drm_gem.c +++ b/drivers/gpu/drm/drm_gem.c @@ -35,6 +35,7 @@ #include <linux/mman.h> #include <linux/pagemap.h> #include <linux/shmem_fs.h> +#include <linux/dma-buf.h> #include "drmP.h" /** @file drm_gem.c @@ -232,6 +233,10 @@ drm_gem_handle_delete(struct drm_file *filp, u32 handle) idr_remove(&filp->object_idr, handle); spin_unlock(&filp->table_lock); + if (obj->import_attach) + drm_prime_remove_imported_buf_handle(&filp->prime, + obj->import_attach->dmabuf); + if (dev->driver->gem_close_object) dev->driver->gem_close_object(obj, filp); drm_gem_object_handle_unreference_unlocked(obj); @@ -527,6 +532,10 @@ drm_gem_object_release_handle(int id, void *ptr, void *data) struct drm_gem_object *obj = ptr; struct drm_device *dev = obj->dev; + if (obj->import_attach) + drm_prime_remove_imported_buf_handle(&file_priv->prime, + obj->import_attach->dmabuf); + if (dev->driver->gem_close_object) dev->driver->gem_close_object(obj, file_priv); diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c new file mode 100644 index 0000000..ff566eb --- /dev/null +++ b/drivers/gpu/drm/drm_prime.c @@ -0,0 +1,299 @@ +/* + * Copyright © 2012 Red Hat + * + * Permission is hereby granted, free of charge, to any person obtaining a + * copy of this software and associated documentation files (the "Software"), + * to deal in the Software without restriction, including without limitation + * the rights to use, copy, modify, merge, publish, distribute, sublicense, + * and/or sell copies of the Software, and to permit persons to whom the + * Software is furnished to do so, subject to the following conditions: + * + * The above copyright notice and this permission notice (including the next + * paragraph) shall be included in all copies or substantial portions of the + * Software. + * + * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR + * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, + * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL + * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER + * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING + * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS + * IN THE SOFTWARE. + * + * Authors: + * Dave Airlie <airlied(a)redhat.com> + * Rob Clark <rob.clark(a)linaro.org> + * + */ + +#include <linux/export.h> +#include <linux/dma-buf.h> +#include "drmP.h" + +/* + * DMA-BUF/GEM Object references and lifetime overview: + * + * On the export the dma_buf holds a reference to the exporting GEM + * object. It takes this reference in handle_to_fd_ioctl, when it + * first calls .prime_export and stores the exporting GEM object in + * the dma_buf priv. This reference is released when the dma_buf + * object goes away in the driver .release function. + * + * On the import the importing GEM object holds a reference to the + * dma_buf (which in turn holds a ref to the exporting GEM object). + * It takes that reference in the fd_to_handle ioctl. + * It calls dma_buf_get, creates an attachment to it and stores the + * attachment in the GEM object. When this attachment is destroyed + * when the imported object is destroyed, we remove the attachment + * and drop the reference to the dma_buf. + * + * Thus the chain of references always flows in one direction + * (avoiding loops): importing_gem -> dmabuf -> exporting_gem + */ + +struct drm_prime_member { + struct list_head entry; + struct dma_buf *dma_buf; + uint32_t handle; +}; + +int drm_gem_prime_handle_to_fd(struct drm_device *dev, + struct drm_file *file_priv, uint32_t handle, uint32_t flags, + int *prime_fd) +{ + struct drm_gem_object *obj; + void *buf; + + obj = drm_gem_object_lookup(dev, file_priv, handle); + if (!obj) + return -ENOENT; + + mutex_lock(&file_priv->prime.lock); + /* re-export the original imported object */ + if (obj->import_attach) { + get_dma_buf(obj->import_attach->dmabuf); + *prime_fd = dma_buf_fd(obj->import_attach->dmabuf, flags); + drm_gem_object_unreference_unlocked(obj); + mutex_unlock(&file_priv->prime.lock); + return 0; + } + + if (obj->export_dma_buf) { + get_dma_buf(obj->export_dma_buf); + *prime_fd = dma_buf_fd(obj->export_dma_buf, flags); + drm_gem_object_unreference_unlocked(obj); + } else { + buf = dev->driver->gem_prime_export(dev, obj, flags); + if (IS_ERR(buf)) { + /* normally the created dma-buf takes ownership of the ref, + * but if that fails then drop the ref + */ + drm_gem_object_unreference_unlocked(obj); + mutex_unlock(&file_priv->prime.lock); + return PTR_ERR(buf); + } + obj->export_dma_buf = buf; + *prime_fd = dma_buf_fd(buf, flags); + } + mutex_unlock(&file_priv->prime.lock); + return 0; +} +EXPORT_SYMBOL(drm_gem_prime_handle_to_fd); + +int drm_gem_prime_fd_to_handle(struct drm_device *dev, + struct drm_file *file_priv, int prime_fd, uint32_t *handle) +{ + struct dma_buf *dma_buf; + struct drm_gem_object *obj; + int ret; + + dma_buf = dma_buf_get(prime_fd); + if (IS_ERR(dma_buf)) + return PTR_ERR(dma_buf); + + mutex_lock(&file_priv->prime.lock); + + ret = drm_prime_lookup_imported_buf_handle(&file_priv->prime, + dma_buf, handle); + if (!ret) { + ret = 0; + goto out_put; + } + + /* never seen this one, need to import */ + obj = dev->driver->gem_prime_import(dev, dma_buf); + if (IS_ERR(obj)) { + ret = PTR_ERR(obj); + goto out_put; + } + + ret = drm_gem_handle_create(file_priv, obj, handle); + drm_gem_object_unreference_unlocked(obj); + if (ret) + goto out_put; + + ret = drm_prime_add_imported_buf_handle(&file_priv->prime, + dma_buf, *handle); + if (ret) + goto fail; + + mutex_unlock(&file_priv->prime.lock); + return 0; + +fail: + /* hmm, if driver attached, we are relying on the free-object path + * to detach.. which seems ok.. + */ + drm_gem_object_handle_unreference_unlocked(obj); +out_put: + dma_buf_put(dma_buf); + mutex_unlock(&file_priv->prime.lock); + return ret; +} +EXPORT_SYMBOL(drm_gem_prime_fd_to_handle); + +int drm_prime_handle_to_fd_ioctl(struct drm_device *dev, void *data, + struct drm_file *file_priv) +{ + struct drm_prime_handle *args = data; + uint32_t flags; + + if (!drm_core_check_feature(dev, DRIVER_PRIME)) + return -EINVAL; + + if (!dev->driver->prime_handle_to_fd) + return -ENOSYS; + + /* check flags are valid */ + if (args->flags & ~DRM_CLOEXEC) + return -EINVAL; + + /* we only want to pass DRM_CLOEXEC which is == O_CLOEXEC */ + flags = args->flags & DRM_CLOEXEC; + + return dev->driver->prime_handle_to_fd(dev, file_priv, + args->handle, flags, &args->fd); +} + +int drm_prime_fd_to_handle_ioctl(struct drm_device *dev, void *data, + struct drm_file *file_priv) +{ + struct drm_prime_handle *args = data; + + if (!drm_core_check_feature(dev, DRIVER_PRIME)) + return -EINVAL; + + if (!dev->driver->prime_fd_to_handle) + return -ENOSYS; + + return dev->driver->prime_fd_to_handle(dev, file_priv, + args->fd, &args->handle); +} + +/* + * drm_prime_pages_to_sg + * + * this helper creates an sg table object from a set of pages + * the driver is responsible for mapping the pages into the + * importers address space + */ +struct sg_table *drm_prime_pages_to_sg(struct page **pages, int nr_pages) +{ + struct sg_table *sg = NULL; + struct scatterlist *iter; + int i; + int ret; + + sg = kmalloc(sizeof(struct sg_table), GFP_KERNEL); + if (!sg) + goto out; + + ret = sg_alloc_table(sg, nr_pages, GFP_KERNEL); + if (ret) + goto out; + + for_each_sg(sg->sgl, iter, nr_pages, i) + sg_set_page(iter, pages[i], PAGE_SIZE, 0); + + return sg; +out: + kfree(sg); + return NULL; +} +EXPORT_SYMBOL(drm_prime_pages_to_sg); + +/* helper function to cleanup a GEM/prime object */ +void drm_prime_gem_destroy(struct drm_gem_object *obj, struct sg_table *sg) +{ + struct dma_buf_attachment *attach; + struct dma_buf *dma_buf; + attach = obj->import_attach; + if (sg) + dma_buf_unmap_attachment(attach, sg, DMA_BIDIRECTIONAL); + dma_buf = attach->dmabuf; + dma_buf_detach(attach->dmabuf, attach); + /* remove the reference */ + dma_buf_put(dma_buf); +} +EXPORT_SYMBOL(drm_prime_gem_destroy); + +void drm_prime_init_file_private(struct drm_prime_file_private *prime_fpriv) +{ + INIT_LIST_HEAD(&prime_fpriv->head); + mutex_init(&prime_fpriv->lock); +} +EXPORT_SYMBOL(drm_prime_init_file_private); + +void drm_prime_destroy_file_private(struct drm_prime_file_private *prime_fpriv) +{ + struct drm_prime_member *member, *safe; + list_for_each_entry_safe(member, safe, &prime_fpriv->head, entry) { + list_del(&member->entry); + kfree(member); + } +} +EXPORT_SYMBOL(drm_prime_destroy_file_private); + +int drm_prime_add_imported_buf_handle(struct drm_prime_file_private *prime_fpriv, struct dma_buf *dma_buf, uint32_t handle) +{ + struct drm_prime_member *member; + + member = kmalloc(sizeof(*member), GFP_KERNEL); + if (!member) + return -ENOMEM; + + member->dma_buf = dma_buf; + member->handle = handle; + list_add(&member->entry, &prime_fpriv->head); + return 0; +} +EXPORT_SYMBOL(drm_prime_add_imported_buf_handle); + +int drm_prime_lookup_imported_buf_handle(struct drm_prime_file_private *prime_fpriv, struct dma_buf *dma_buf, uint32_t *handle) +{ + struct drm_prime_member *member; + + list_for_each_entry(member, &prime_fpriv->head, entry) { + if (member->dma_buf == dma_buf) { + *handle = member->handle; + return 0; + } + } + return -ENOENT; +} +EXPORT_SYMBOL(drm_prime_lookup_imported_buf_handle); + +void drm_prime_remove_imported_buf_handle(struct drm_prime_file_private *prime_fpriv, struct dma_buf *dma_buf) +{ + struct drm_prime_member *member, *safe; + + mutex_lock(&prime_fpriv->lock); + list_for_each_entry_safe(member, safe, &prime_fpriv->head, entry) { + if (member->dma_buf == dma_buf) { + list_del(&member->entry); + kfree(member); + } + } + mutex_unlock(&prime_fpriv->lock); +} +EXPORT_SYMBOL(drm_prime_remove_imported_buf_handle); diff --git a/include/drm/drm.h b/include/drm/drm.h index 34a7b89..64ff02d 100644 --- a/include/drm/drm.h +++ b/include/drm/drm.h @@ -617,6 +617,17 @@ struct drm_get_cap { __u64 value; }; +#define DRM_CLOEXEC O_CLOEXEC +struct drm_prime_handle { + __u32 handle; + + /** Flags.. only applicable for handle->fd */ + __u32 flags; + + /** Returned dmabuf file descriptor */ + __s32 fd; +}; + #include "drm_mode.h" #define DRM_IOCTL_BASE 'd' @@ -673,7 +684,8 @@ struct drm_get_cap { #define DRM_IOCTL_UNLOCK DRM_IOW( 0x2b, struct drm_lock) #define DRM_IOCTL_FINISH DRM_IOW( 0x2c, struct drm_lock) -#define DRM_IOCTL_GEM_PRIME_OPEN DRM_IOWR(0x2e, struct drm_gem_open) +#define DRM_IOCTL_PRIME_HANDLE_TO_FD DRM_IOWR(0x2d, struct drm_prime_handle) +#define DRM_IOCTL_PRIME_FD_TO_HANDLE DRM_IOWR(0x2e, struct drm_prime_handle) #define DRM_IOCTL_AGP_ACQUIRE DRM_IO( 0x30) #define DRM_IOCTL_AGP_RELEASE DRM_IO( 0x31) diff --git a/include/drm/drmP.h b/include/drm/drmP.h index 574bd1c..dd73104 100644 --- a/include/drm/drmP.h +++ b/include/drm/drmP.h @@ -91,6 +91,7 @@ struct drm_device; #define DRM_UT_CORE 0x01 #define DRM_UT_DRIVER 0x02 #define DRM_UT_KMS 0x04 +#define DRM_UT_PRIME 0x08 /* * Three debug levels are defined. * drm_core, drm_driver, drm_kms @@ -150,6 +151,7 @@ int drm_err(const char *func, const char *format, ...); #define DRIVER_IRQ_VBL2 0x800 #define DRIVER_GEM 0x1000 #define DRIVER_MODESET 0x2000 +#define DRIVER_PRIME 0x4000 #define DRIVER_BUS_PCI 0x1 #define DRIVER_BUS_PLATFORM 0x2 @@ -215,6 +217,11 @@ int drm_err(const char *func, const char *format, ...); drm_ut_debug_printk(DRM_UT_KMS, DRM_NAME, \ __func__, fmt, ##args); \ } while (0) +#define DRM_DEBUG_PRIME(fmt, args...) \ + do { \ + drm_ut_debug_printk(DRM_UT_PRIME, DRM_NAME, \ + __func__, fmt, ##args); \ + } while (0) #define DRM_LOG(fmt, args...) \ do { \ drm_ut_debug_printk(DRM_UT_CORE, NULL, \ @@ -238,6 +245,7 @@ int drm_err(const char *func, const char *format, ...); #else #define DRM_DEBUG_DRIVER(fmt, args...) do { } while (0) #define DRM_DEBUG_KMS(fmt, args...) do { } while (0) +#define DRM_DEBUG_PRIME(fmt, args...) do { } while (0) #define DRM_DEBUG(fmt, arg...) do { } while (0) #define DRM_LOG(fmt, arg...) do { } while (0) #define DRM_LOG_KMS(fmt, args...) do { } while (0) @@ -410,6 +418,12 @@ struct drm_pending_event { void (*destroy)(struct drm_pending_event *event); }; +/* initial implementaton using a linked list - todo hashtab */ +struct drm_prime_file_private { + struct list_head head; + struct mutex lock; +}; + /** File private data */ struct drm_file { int authenticated; @@ -437,6 +451,8 @@ struct drm_file { wait_queue_head_t event_wait; struct list_head event_list; int event_space; + + struct drm_prime_file_private prime; }; /** Wait queue */ @@ -652,6 +668,12 @@ struct drm_gem_object { uint32_t pending_write_domain; void *driver_private; + + /* dma buf exported from this GEM object */ + struct dma_buf *export_dma_buf; + + /* dma buf attachment backing this object */ + struct dma_buf_attachment *import_attach; }; #include "drm_crtc.h" @@ -890,6 +912,20 @@ struct drm_driver { int (*gem_open_object) (struct drm_gem_object *, struct drm_file *); void (*gem_close_object) (struct drm_gem_object *, struct drm_file *); + /* prime: */ + /* export handle -> fd (see drm_gem_prime_handle_to_fd() helper) */ + int (*prime_handle_to_fd)(struct drm_device *dev, struct drm_file *file_priv, + uint32_t handle, uint32_t flags, int *prime_fd); + /* import fd -> handle (see drm_gem_prime_fd_to_handle() helper) */ + int (*prime_fd_to_handle)(struct drm_device *dev, struct drm_file *file_priv, + int prime_fd, uint32_t *handle); + /* export GEM -> dmabuf */ + struct dma_buf * (*gem_prime_export)(struct drm_device *dev, + struct drm_gem_object *obj, int flags); + /* import dmabuf -> GEM */ + struct drm_gem_object * (*gem_prime_import)(struct drm_device *dev, + struct dma_buf *dma_buf); + /* vga arb irq handler */ void (*vgaarb_irq)(struct drm_device *dev, bool state); @@ -1509,6 +1545,32 @@ extern int drm_vblank_info(struct seq_file *m, void *data); extern int drm_clients_info(struct seq_file *m, void* data); extern int drm_gem_name_info(struct seq_file *m, void *data); + +extern int drm_gem_prime_handle_to_fd(struct drm_device *dev, + struct drm_file *file_priv, uint32_t handle, uint32_t flags, + int *prime_fd); +extern int drm_gem_prime_fd_to_handle(struct drm_device *dev, + struct drm_file *file_priv, int prime_fd, uint32_t *handle); + +extern int drm_prime_handle_to_fd_ioctl(struct drm_device *dev, void *data, + struct drm_file *file_priv); +extern int drm_prime_fd_to_handle_ioctl(struct drm_device *dev, void *data, + struct drm_file *file_priv); + +extern struct sg_table *drm_prime_pages_to_sg(struct page **pages, int nr_pages); +extern void drm_prime_gem_destroy(struct drm_gem_object *obj, struct sg_table *sg); + + +void drm_prime_init_file_private(struct drm_prime_file_private *prime_fpriv); +void drm_prime_destroy_file_private(struct drm_prime_file_private *prime_fpriv); +int drm_prime_add_imported_buf_handle(struct drm_prime_file_private *prime_fpriv, struct dma_buf *dma_buf, uint32_t handle); +int drm_prime_lookup_imported_buf_handle(struct drm_prime_file_private *prime_fpriv, struct dma_buf *dma_buf, uint32_t *handle); +void drm_prime_remove_imported_buf_handle(struct drm_prime_file_private *prime_fpriv, struct dma_buf *dma_buf); + +int drm_prime_add_dma_buf(struct drm_device *dev, struct drm_gem_object *obj); +int drm_prime_lookup_obj(struct drm_device *dev, struct dma_buf *buf, + struct drm_gem_object **obj); + #if DRM_DEBUG_CODE extern int drm_vma_info(struct seq_file *m, void *data); #endif -- 1.7.7.6

12 years, 1 month

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

by Marek Szyprowski

Hello eveyone, On Linaro Memory Management meeting in Budapest (May 2011) we have discussed about the design of DMA mapping framework. We tried to identify the drawbacks and limitations as well as to provide some a solution for them. The discussion was mainly about ARM architecture, but some of the conclusions need to be applied to cross-architecture code. The first issue we identified is the fact that on some platform (again, mainly ARM) there are several functions for allocating DMA buffers: dma_alloc_coherent, dma_alloc_writecombine and dma_alloc_noncoherent (not functional now). For each of them there is a match dma_free_* function. This gives us quite a lot of functions in the public API and complicates things when we need to have several different implementations for different devices selected in runtime (if IOMMU controller is available only for a few devices in the system). Also the drivers which use less common variants are less portable because of the lacks of dma_alloc_writecombine on other architectures. The solution we found is to introduce a new public dma mapping functions with additional attributes argument: dma_alloc_attrs and dma_free_attrs(). This way all different kinds of architecture specific buffer mappings can be hidden behind the attributes without the need of creating several versions of dma_alloc_ function. dma_alloc_coherent() can be wrapped on top of new dma_alloc_attrs() with NULL attrs parameter. dma_alloc_writecombine and dma_alloc_noncoherent can be implemented as a simple wrappers which sets attributes to DMA_ATTRS_WRITECOMBINE or DMA_ATTRS_NON_CONSISTENT respectively. These new attributes will be implemented only on the architectures that really support them, the others will simply ignore them defaulting to the dma_alloc_coherent equivalent. The next step in dma mapping framework update is the introduction of dma_mmap/dma_mmap_attrs() function. There are a number of drivers (mainly V4L2 and ALSA) that only exports the DMA buffers to user space. Creating a userspace mapping with correct page attributes is not an easy task for the driver. Also the DMA-mapping framework is the only place where the complete information about the allocated pages is available, especially if the implementation uses IOMMU controller to provide a contiguous buffer in DMA address space which is scattered in physical memory space. Usually these drivers don't touch the buffer data at all, so the mapping in kernel virtual address space is not needed. We can introduce DMA_ATTRIB_NO_KERNEL_MAPPING attribute which lets kernel to skip/ignore creation of kernel virtual mapping. This way we can save previous vmalloc area and simply some mapping operation on a few architectures. This patch series is a preparation for the above changes in the public dma mapping API. The main goal is to modify dma_map_ops structure and let all users to use for implementation of the new public funtions. The proof-of-concept patches for ARM architecture have been already posted a few times and now they are working resonably well. They perform conversion to dma_map_ops based implementation and add support for generic IOMMU-based dma mapping implementation. To get them merged we first need to get acceptance for the changes in the common, cross-architecture structures. More information about these patches can be found in the following threads: http://www.spinics.net/lists/linux-mm/msg19856.html http://www.spinics.net/lists/linux-mm/msg21241.html http://lists.linaro.org/pipermail/linaro-mm-sig/2011-September/000571.html http://lists.linaro.org/pipermail/linaro-mm-sig/2011-September/000577.html http://www.spinics.net/lists/linux-mm/msg25490.html The patches are prepared on top of Linux Kernel v3.2-rc6. I would appreciate any comments and help with getting this patch series into linux-next tree. The idea apllied in this patch set have been also presented during the Kernel Summit 2011 and ELC-E 2011 in Prague, in the presentation 'ARM DMA-Mapping Framework Redesign and IOMMU integration'. I'm really sorry if I missed any of the relevant architecture mailing lists. I've did my best to include everyone. Feel free to forward this patchset to all interested developers and maintainers. I've already feel like a nasty spammer. Best regards Marek Szyprowski Samsung Poland R&D Center Patch summary: Andrzej Pietrasiewicz (9): X86: adapt for dma_map_ops changes MIPS: adapt for dma_map_ops changes PowerPC: adapt for dma_map_ops changes IA64: 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 (5): common: dma-mapping: introduce alloc_attrs and free_attrs methods 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/ia64/hp/common/sba_iommu.c | 11 ++++++----- arch/ia64/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/ia64/kernel/pci-swiotlb.c | 9 +++++---- arch/ia64/sn/pci/pci_dma.c | 9 +++++---- arch/microblaze/include/asm/dma-mapping.h | 18 ++++++++++++------ arch/microblaze/kernel/dma.c | 10 ++++++---- 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/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 | 4 ++-- 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 | 12 +++++++----- 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/linux/swiotlb.h | 6 ++++-- include/xen/swiotlb-xen.h | 6 ++++-- lib/swiotlb.c | 5 +++-- 43 files changed, 305 insertions(+), 182 deletions(-) -- 1.7.1.569.g6f426

12 years, 1 month

[GIT PULL] DMA-mapping framework updates for 3.4

by Marek Szyprowski

Hi Linus, Please pull the dma-mapping framework updates for v3.4 since commit c16fa4f2ad19908a47c63d8fa436a1178438c7e7: Linux 3.3 with the top-most commit e749a9f707f1102735e02338fa564be86be3bb69 common: DMA-mapping: add NON-CONSISTENT attribute from the git repository at: git://git.infradead.org/users/kmpark/linux-samsung dma-mapping-next Those patches introduce a new alloc method (with support for memory attributes) in dma_map_ops structure, which will later replace dma_alloc_coherent and dma_alloc_writecombine functions. Thanks! Best regards Marek Szyprowski Samsung Poland R&D Center Patch summary: Andrzej Pietrasiewicz (9): X86: adapt for dma_map_ops changes MIPS: adapt for dma_map_ops changes PowerPC: adapt for dma_map_ops changes IA64: 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 | 9 +++++---- 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 | 16 ++++++++-------- 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 | 4 ++-- 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 | 12 +++++++----- 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/linux/swiotlb.h | 6 ++++-- include/xen/swiotlb-xen.h | 6 ++++-- lib/swiotlb.c | 5 +++-- 47 files changed, 338 insertions(+), 206 deletions(-)

12 years, 1 month

消灭▲财务黑▲洞

by 财务黑洞

12 years, 1 month

[GIT PULL]: dma-buf updates for 3.4

by Sumit Semwal

Hi Linus, Could you please pull the dma-buf updates for 3.4? This includes the following key items: - kernel cpu access support, - flag-passing to dma_buf_fd, - relevant Documentation updates, and - some minor cleanups and fixes. These changes are needed for the drm prime/dma-buf interface code that Dave Airlie plans to submit in this merge window. Thanks, and best regards, ~Sumit. The following changes since commit c16fa4f2ad19908a47c63d8fa436a1178438c7e7: Linux 3.3 (2012-03-18 16:15:34 -0700) are available in the git repository at: git://git.linaro.org/people/sumitsemwal/linux-dma-buf.git for-linus-3.4 Daniel Vetter (3): dma-buf: don't hold the mutex around map/unmap calls dma-buf: add support for kernel cpu access dma_buf: Add documentation for the new cpu access support Dave Airlie (1): dma-buf: pass flags into dma_buf_fd. Laurent Pinchart (4): dma-buf: Constify ops argument to dma_buf_export() dma-buf: Remove unneeded sanity checks dma-buf: Return error instead of using a goto statement when possible dma-buf: Move code out of mutex-protected section in dma_buf_attach() Rob Clark (2): dma-buf: add get_dma_buf() dma-buf: document fd flags and O_CLOEXEC requirement Sumit Semwal (2): dma-buf: add dma_data_direction to unmap dma_buf_op dma-buf: correct dummy function declarations. Documentation/dma-buf-sharing.txt | 120 ++++++++++++++++++++++++++- drivers/base/dma-buf.c | 165 +++++++++++++++++++++++++++++++------ include/linux/dma-buf.h | 97 +++++++++++++++++++-- 3 files changed, 345 insertions(+), 37 deletions(-)

12 years, 1 month

消灭财务黑洞 !

by 财务黑洞

财务黑洞无情-消灭漏洞有道【培训时间】2012年4月13-14日深圳 4月20-21日上海 4月27-28日北京 6月9-10日深圳 6月15-16日上海 7月6-7日北京【培训对象】公司股东、董事长、经理以及企业其他中高层管理人员。【培训费用】￥2800元/人（提供讲义、午餐、发票、茶点等） ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ 【课程背景】邓老师告诉你：如何发现财务健康的DNA密码如何做到：消灭财务漏洞避免财务黑洞确保经营成果中国企业财务黑洞问题诊断与防范行家，消灭财务黑洞专题研究第一人。用百度搜索“消灭财务漏洞”6个字达260多万条，影响巨大！用谷歌搜索“邓鸿老师”4个字达到1000多万条，是否徒有虚名？培训目标： 1、企业财务黑洞是由多方面因素造成的，财务黑洞的封杀要有专业指导、丰富的实践经验和恰当的方式方法。 2、企业的财务工作好坏不单只是财务部的事情，是企业综合管理水平的体现。邓老师以自己多年所经历的，许多老板用昂贵的金钱甚至是生命为代价所换来的丰富案例，策您警醒，让你吃人家之堑长自己之智。 3、经常听到会计人员抱怨：老板不重视财务。你不妨请你的老板来听一场邓老师的《消灭财务黑洞》的课程，也许是你送给老板的最好礼物！也是给自己工作的最好帮助；经常听到我们的会计抱怨：同事不配合、不理解、不支持我们的财务工作。你不妨建议老板请邓老师去给你的公司全体员工上一堂《消灭财务黑洞》的课程，你的工作环境是不是会得到显著改善？你不妨试一试？课程100%为落地可操作的方法与工具，绝对实战、实效、实用！授课方式：专题讲授、互动交流、案例分析 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ 【课程大纲】序言： 1、什么是黑洞？ 2、什么是财务黑洞？ 3、织网与补网一、财务黑洞的八大原发病毒（一）收款黑洞 1、常规收款手段为什么失效？ 2、货款要不回为什么还要倒赔钱？ 3、案例：合同纠纷背后的货款欺诈陷阱 4、消灭财务黑洞： A、结合案件一些证据和日常单据明白问题在哪里？ B、如何解决和防范诊断出来的问题？（二）付款黑洞 1、公司有没有资金紧张的时候？资金紧张怎么办？你是怎么做的？为什么说你的做法是错误的，是在自己制造财务黑洞，或者说是自掘陷阱！ 2、错误表现在两个极端：（1）一个极端是忽悠、再忽悠（有的）到骗；（2）另一个极端是扛、死扛、扛到死，把自己弄得很悲壮 3、消灭财务黑洞：（1）惨淡经营、死扛、扛到死有没有必要？（2）提供两种解决办法，供参考：办法一、你能不能挑出可以帮助你暂时渡过难关的那些供应商？暂时继续占用一下人家的资金。办法二、有没有第三条路可走？第三条路怎么走？案例：企业暂停经营撇债（三）税务黑洞 1、内外两套账，为什么税务一查一个准？ 2、是什么原因？因为有三道坎迈不过去：第一道坎：合同与账本，两张皮不黏！第二道坎：资金账户似迷宫，剪不断来理还乱第三道坎：账实要相符，神仙也犯难 3、面对三道坎，你是不是就束手无策？消灭财务黑洞，道在哪里？案例：桌上放收款单据的故事的后续故事（四）投资黑洞 1、投资前-- 练就火眼金睛问题：（1）没有看清合作方，搞清楚其真实意图，让表面现象所迷惑；（2）对产权状况不清，盲目投资；（3）公司收购的两大猫腻如何识破猫腻？避免陷于巨大财务黑洞？ 2、投资合作中-- 给我一双慧眼，不要聪明人办傻事问题：（1）是投资入股还是借款？（2）问题形成后处理方法要得当 3、投资后-- 半睁半闭眼睛，要吃小亏避免上大当。（五）融资黑洞 1、不懂融资，要多作功课，不要犯吃饭不看菜，裁衣不量体常识错误。表现： 1、喜欢包装，“临时抱佛脚” 2、盲目相信中介，迷信能人和关系功课之一：企业所处的发展阶段不同融资渠道有别功课之二：用好企业现有的有效资源是融资的关键。功课之三：认识资金和其能够提供的金融产品，不要做瞎子摸象 2、为了融资而融资，一条道走到黑表现： a、抛开实业玩概念； b、盲目相信过度包装。 3、企业在融资时如何防骗？（六）沟通黑洞 1、采购绑架财务 2、销售尾巴何其多？某物业管理公司的案例三招解决公司沟通黑洞（七）成本黑洞 1、企业成本核算的基本要求 2、案例：原材料成本 X 2 = 销售价的故事（八）管理黑洞 1、会计由谁来招聘？人事部和老板招聘的会计有什么错？ 2、会计工作能不能胜任由谁来考察？ 3、会计经常换有什么严重后果？ 4、账实严重不相符谁之过？ 5、案例：（1）逾期未提交出口单据，税局认定“内销”，补税和滞纳金等500多万元。（2）单据不齐，1000余万出口退税遇阻。二、财务黑洞根源探究 1、曲突徙薪亡恩泽，焦头烂额为上客。 ----忙救火，疏预防 2、麦克唐纳牧师的故事 ----只知其一，不知其二；或者说：知其然不知其所以然。 3、犯用人之忌！（1）用老乡 a、老乡老乡，背后一枪 b、老乡靠得住，母猪能上树（2）用老婆老婆做出纳，管住了钱还有什么没有管住？ 4、四大认识误区最害人，现在明白来得及。三、消灭财务黑洞之道（一）练就消灭财务黑洞的上乘功法 1、五个前提条件 2、织网与补网，你做何选择？ 3、审查方法介绍（1）业务循环审查法（2）五大审查技术方法介绍（二）四级定位防范财务黑洞咨询系统介绍 A、消灭财务黑洞咨询服务方法 1、发现财务黑洞是一项复杂的系统专业工程 2、抓住8大高发点，以点带面，寻根探源，让财务黑洞无可逃遁。 B、四级定位图介绍?? ? 1级：人（财务）行，制度、流程也行解决办法：执行偏差的案例 2级：人（财务）行，制度流程不行 3级：人（财务）不行，制度流程行 4级：人（财务）不行，制度流程也不行案例：理清了一团乱麻四、警惕财务黑洞的变种病毒案例1：外派黑洞：养虎为患案例2：材料黑洞：空运费大于机器价值案例案例3：保密黑洞：老板被敲诈案例4：收购公司黑洞案例5：某公司海外上市劫 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ 【讲师介绍】邓鸿中国企业财务黑洞问题诊断与防范行家，消灭财务黑洞专题研究第一人 --深圳市福中达投资控股有限公司财务总监 --深圳市多丽电子商务产业园财务顾问 --亚太集团会计师事务所有限公司深圳所合伙人亚太集团会计师事务所有限公司深圳所注册会计师、执业年限12年、会计、审计、财务管理岗位及顾问工作从业年限28年。资深注册会计师、香港城市大学国际会计硕士，亚太集团会计师事务所有限公司深圳总部合伙人。企业各类财务漏洞、财务黑洞问题的咨询诊断与防范行家。资深财务管理、审计、咨询从业者，担任过多家企业财务顾问，从事企业财务管理、咨询和投融资工作达二十多年, 具有较强的综合协调沟通问题能力，主持及参与的项目达三位数以上，具有较为丰富的财务管理、企业投融资、审计、评估、税收筹划、财务税收顾问经验。 ? ? 熟悉国家财务制度和相关政策法规，熟悉国家税收法律法规，熟悉公司改制及上市制度及程序、熟悉财政、税务、工商、劳动人事等政府各部门办事程序及方法，熟悉银行等金融机构投融资技巧并有一定的投融资渠道。有较强的文字功力，能将工作中发现的问题及改进办法整理发表，曾在中国著名《财经》杂志、《会计月刊》、《公司金融》等报刊杂志上发表百多篇文章，《公司金融》杂志更是开辟专栏连载财务黑洞研究方面的系列文章。本人的经验总结性文章《财务黑洞案例实录》在中国会计界最高学府“国家会计学院”“中国会计视野”网站发表一天就达2500多浏览量，创该站记录，时至今日热度不减，第二天就已被收入“中国会计视野”精品文库，仅该网站网友留言就达200多条，转载网站达几万家，上至企业老板，下至大学学生都将该文当做教科书，备受关注和引发热议。在《公司金融》（国内统一刊号：CN44-1563/F 国际标准连续出版刊号：ISSN 1671-6728）杂志上连载的文章有： 1、《私募融资背后的商业谎言》 2009年10月1日总第42期 2、财务黑洞启示录（一）--《内外账的老思维要不得了》 2009年11月1日总第44期 3、财务黑洞启示录（二）--《单据丢失酝酿严重税务后果》2009年11月16日总第45期 4、财务黑洞启示录（三）--《表述模糊引发十年官司》 2009年12月1日总第46期 5、财务黑洞启示录（四）--《合同纠纷背后的货款欺诈陷阱》2010年1月1日总第48期 6、财务黑洞启示录（五）--《友情信任反成投资陷阱》 2010年1月16日总第49期 7、财务黑洞启示录（六）--《资产收购中隐藏的猫腻》 2010年2月1日总第50期培训风格 1.邓鸿老师有很强的现场亲和力、敏锐的学员洞察力以及丰富的授课经验，了解成年人学习的特点，把复杂的问题说得通俗易懂。 2.授课风格既稳重，但又不乏幽默和风趣，采用多样化的互动授课方式，营造轻松愉快的学习气氛，充分调动学员的听课积极性。 3.授课内容既有理论深度，又注重实用效果，使学员在培训后，能在工作中解决实际问题，体现培训真正的价值。培训现场互动性很强，有很强的控场能力，倡导“家常式的互动性强”的授课理念。邓老师提倡实用、实在、实际、实战的培训风格，用专业、专注、方向、方法凝聚学员的满意。 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ 主办单位:中国商业培训网深.圳报.名.热.线：０７５５- - ６１.２８.２５.７１陈小姐上.海报.名.热.线: ０２１- - ５１.８７.３７.０８张先生温馨提示:(每期限40人,如需参加请提前预定) QQ订位!-1078861118 ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡ ▲请将以下报名表内容填写后发送到：chinasypx(a)foxmail.xn--com-s18docw0dhtoqp48a05g9vuvzhmss763etxf01o3s3g! 　　　　　　　　　　　报名回执表　　我单位共_______人报.名参加财务黑洞无情-消灭漏洞有道 4月13-14日深圳□ 4月20-21日上海□ 4月27-28日北京□ 单位名称：_____________________________________________ 联系人：_____________ 联系电话：_______________ 手机：_______________ 图文传真：_____________ 电子信箱：_____________________________________ 参会人：_____________ 参会人：_____________ 参会人：_____________ 参会人：_____________ 参会人：_____________ 参会人：_____________ 总费用：___________ 元整。付款方式：□ 现金　□ 支票　□ 转帐　　（请选择打“√”）备注: 1.请您把报名回执认真填好后回传我司，为确保您报名无误,请您再次电话确认! 2.本课程可根据企业需要组织内训。

12 years, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig March 2012