Linaro-mm-sig

linaro-mm-sig@lists.linaro.org

24 participants
2727 discussions

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(-)

13 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.本课程可根据企业需要组织内训。

13 years, 1 month

企业税务稽查★规避技巧

by 稽查组

��ҵ˰��˰��չ�ܼ��ʵ�� ʱ��ص㣺2012��4��19-20��Ϻ� 2012��4��26-27�ձ�� 2012��4��28-29�� γ̷��ã�2800Ԫ/�ˣ��Ϸѡ��ͼ��ȣ� �ڿζ��󣺲��ܾ��Լ��߼��Ӫ��Ա;��ܼࡢ��ܡ� ˰��˰��ܡ��ʻ�ơ�˰��ƵȾ��ʿ�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� : ˰��ҵ��Ե�һ����ܶ��ҵ��ǰ��˰��ơ��ص㣻�� ҵΪʲô�ᱻ��顢��鲿��Ҫ��ʲô��ô�飿��ĳ��ֻ�ʹ��ҵ��ټ�� ˰��գ� ��2011��ҵ˰��˰��չ�ܼ��ʵ�񡷿γ��Ҫ��⣺ 1��Ϊʲô��ǵ��ҵ�ᱻ��飿��ǵ��ҵû�У� 2��˰��Ҫ��ҵ�Բ飬ʲô��Բ�˰��ز��⣿ 3��ҵ��Щ��˰ҵ��Ƚ��״��⣿��Щ��ڻ��ʱ�ᱻ˰��ص��ע�� 4��Ǳ��ȥ�Ĳ��񱨱��¶��˰��⣿ 5��ڵ��ҵ��Ҫ��Щ˰��⣿ 6��˰��֤�ݵ��Ѽ��Ҫ��Щ�ֶΡ�� 7��ҵ��⣬��ǻ��ʲô��Ĵ�� Ӧ��̼��ܴ��»�С��С�»��ˣ� �ԡԡԡԡԡԡԡ� �� : 1��׼ȷ��ҵ��ٵ�˰��ƣ� 2��˰��鹤��Ļ��򡢻��֪��֪�ˣ��ս�� 3��׼ȷ��ҵ��ٵľ��˰��⼰��ȷ�Ľ��취�� 4��޶Ƚ��˰��գ��ҵ��ʧ�� 5��˰��ǶȽ��񱨱��ǰ��˰��գ� 6��ѡ��ȷ��˰��Ӧ�Բ��ԣ�ʹ��˾�Ͳ�˰��Ա�е��С�ķ��Σ� �ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� : ��T�� һ��֣�˰��ҵӦ�Բ��˰�� һ��˰��Ʒ�� 1��˰��飬��ҵ�ĸ��̬�� 2��˰��ĸ��ƣ� 3��2010��˰��鹤��Ļعˣ� 4��2011��˰��鹤��Ŀ�ꡢ��񼰻��ص�� ˰��뷽�� 1��ҵ��ԭ��ķ�� 2��˰��鹤��̼��鲿��ڲ�ְ�ܻ��֣� 3��˰��鰸�� 4��˰��֤��Ѽ� ��˰��۷��Ӧ�� 1��˰��е�˰�� 2��˰��Υ��Ϊ�ķ�� 3��˰��еĹ�ͨ�� 4��˰��۵ķ�� 5��Σ��صļ�� ġ��˰�� 1��˰��Ĺ��Ҫ�� 2��˰��Ļ�� 3��˰��Ĺ�� 4��˰��ԭ�� 5��˰��ķ�չ 6��ѡ��ķ�� T�� ڶ��֣��ҵ�Բ��볣��˰��Ǳ��˰��շ�� һ��˰��Բ� 1��˰��Բ鶨��붨λ 2��ҵ˰��Բ��Ӧ�Բ�� 3��Ŀ��Բ鼼�� 4��ҵ��Բ鼼�� ֵ˰ҵ�񳣼��⼰��Ҫ��鷽�� 1��˰��˳��⼰��鷽�� 2��˰��Χ��⼰��鷽�� 3��˰�ʳ��⼰��鷽�� 4��˰���⼰��鷽�� 5��˰���⼰��鷽�� 6��ֿ�ƾ֤��⼰��鷽�� 7��˰��泣��⼰��鷽�� Ӫҵ˰ҵ�񳣼��⼰��Ҫ��鷽�� 1��˰�˳��⼰��鷽�� 2��˰��Χ��˰�ʳ��⼰��鷽�� 3��˰Ӫҵ���⼰��鷽�� 4��Ŀ��⼰��鷽�� ġ��ҵ��˰ҵ�񳣼��⼰��Ҫ��鷽�� 1��Ŀ��⼰��鷽�� 2��۳��Ŀ��⼰��鷽�� 3��ʲ��⼰��鷽�� 4��˰��Żݳ��⼰��鷽�� 5��ö��⼰��鷽�� 6��Ӧ��˰���⼰��鷽�� 塢��˰ҵ�񳣼��⼰��Ҫ��鷽�� 1��˰�˳��⼰��鷽�� 2��۽��˳��⼰��鷽�� 3��˰��Χ��⼰��鷽�� 4��˰��볣��⼰��鷽�� 5��˰��볣��⼰��鷽�� 6��˰��ļ�� ˰��ҵ�񳣼��⼰��Ҫ��鷽�� 1��˰��⼰��鷽�� 2�� ˰��⼰��鷽�� 3��Դ˰��⼰��鷽�� 4��ʹ��˰��⼰��鷽�� 5��ӡ��˰��⼰��鷽�� 6��ֵ˰��⼰��鷽�� T�� ֣�˰��Ʋ��չ�� һ��˰׼�򡪻��˰��չ�� 1��Բ�� 2��ʱ�Բ�� ʲ�ҵ��׼��˰��չ�� 1��̶��ʲ� 2��ʲ� 3��ڴ�̯�� 4��Ͷ��ʲ� 5�� ׼��˰��˰�� 1��Ʒ�� 2�� 3��ö��ʲ�ʹ��Ȩ�� ġ��ɱ��û��˰��Ƚϼ��˰�� 1��̶��ʲ�֧��޷ѵĿ۳� 2��Ͷ��֧�� 3��Ӫҵ��֮��ҵ��֧�� 4��Ծ��۳� 5��ʲ��ʧ 6��Ϣ֧�� 7��Ѻ�Ӷ��Ŀ۳� �塢��ҵ��׼��˰�� 1��ǻ��ʲ�� 2��ծ�� 豸Ҫ�� 1��ֳֻ�Ͳ 2��ͶӰ�ǣ��ѵʦ�Ա�� 3��װ��װ�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� ��T�� ʦ��: �´Ӵ��绪�˽�ʦ500ǿ��й��ѧ��̹��˶ʿ��MBA��й�ע��ʦ��CPA��ע��˰��ʦ ��CPT��й�ĿǰΨһ�ݺᡰ��˰��Դ��ս�Թ��ġ��ܡ�ʵս�ɹ��ר�� ѵʦ��й��˰�γ��󻯵�һ�ˡ��´Ӵ��ʦĿǰΪ�й��ܲ��ѵ��л��ѵ��ɹ�� Ͱ�ֱ��ҡ��ҷ�չ��ĸ�ίԱ�ᡰ��й��ί�ᡢ�۳ɻ��ѧԺ��й��ѧ ѧ��˰�ﻮʦ��֤��Ŀ��й��ҵ��ϻ��֤��Ŀ��Ƹ��ʦ��о�Ժ��Ƹ��ڡ��㽭�� ѧ�ܲðࡢ�Ϻ��ͨ��ѧ��̩��ѧԺ��ѧԺ��Ƹ��ʦ��ν��ｭ��֬��Ʒ��ܡ� ��ﻯ��˾��ܾ��ݴ󹫻��ʦ��ϯע��ʦ��Ϻ��ͨ��Ƽ��޹�˾ ��ϯ��٣�CFO��̩��ͨҩҵ��޹�˾��ܼࡣ��ͨ��ѯ��˰�ﻮ��ʱ��ҵ�ڲ� ��ƶ��ơ��Ŀ��Է��Ŀ��ʵȣ��Ⱥ�Ϊȫ��ʮ��ҵ�ṩ��ѯ��Ϊ��ټ��ҵ�� ҵ��ѵ��񣬴��ɹ��ٰ��δ��͹��Ρ��ġ��˰��չ��˰�ﻮ�� ʵս��ҵ��˰��Ӧ�Բ��Լ�ʵʩ��ĺ��˰��˰��շ��ز��ҵ�� ֵ˰��ʵ��˰�ﻮ��ɡ��и��߸��˰��˰�ﻮ��ǲ��Ĳ�� Ӧ��˿��ͻ��ù��ڲ��չ��»��׼��Ӧ�þ�Ҫ��ȫ��Ԥ�� ҵ�Ĳ��ɱ��ʤʵս��ҵ�ɱ��ơ��ղ��ʵ��˰�ﻮ�� ڲ��ڲ��Ƽ��շ��ȿγ��ҵ��ʿ�� ַ��ͻ��й��š��й�ʯ�͡��й�ʯ��й��С��й��С��ӽ��긣��š� ��ǿͳ��µ��ɽ��硢��֯���ǻ��ѹ��¡��л�� 칤��ϡ��˴Ｏ�š�ӥ�μ��š��Ƶꡢ��Ʒ��з�չ��ĸ�ίԱ�ᡢ̨��о�� ó��ίԱ�ᡢ��ּ��š��š��˹ɷݡ��ҩҵ��ǡ��ȷɳ�ҵ��ɭ̩��硢 ��̩ʵҵ��˴��ߡ��򻪷��Ρ��ص�ء��㽭��ѧ��ݴ�ѧ��ݽ��ѧԺ��Ϻ��ͨ�� ѧ��Ԫ��š��š��ͨ�ͳ��Ϲ��ܡ��ҩҵ��̵ؼ��š��չ��ï��š� �󻪼��š��ɭ��Ϻ��̲ݼ��š��ǵ��Ƽ��Ͽ��š��й����缯�š��ļ�� ɷݡ��й��Ϸ�ȼ��š��ҵ��š��ǹ��衢��ϲ��š��뼯�š��㱦�ɷݡ�� ơ�ơ��֤ȯ�� ڿη��ڶг��Ĭ��ǳ��ʵս��ʵ�á�ʵЧ�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� �� .��.��.֯��ŵ˹��ҵ��ѯ��޹�˾ �� .�� .��.��.�ߣ��- - ��.��.��.�� С�� .�� .��.��.��: �� - - ��.��.��.�� ԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡԡ� ��뽫��±��д��͵��chinasypx@foxmail.com��Ա��ڵ�һʱ��ϵ! �� ִ �� ҵ�λ��_______�˱�.��μӡ��ҵ˰��˰��չ�ܼ��ʵ�� λ��ƣ�_____________________________________________ �� ϵ �ˣ�_____________ ��ϵ�绰��_______________ �ֻ��_______________ ͼ�Ĵ��棺_____________ ��䣺_____________________________________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ˣ�_____________ �� ã�___________ Ԫ�� ʽ�� 𡡡� ֧ Ʊ�� ת �ʡ��ѡ��򡰡̡�� ע: 1.��ѱ��ִ��ú�ش��˾��Ϊȷ��,��ٴε绰ȷ��! 2.��γ̿ɸ��ҵ��Ҫ��֯��ѵ��

13 years, 1 month

[PATCH] dma-buf: Correct dummy function declarations.

by Sumit Semwal

While testing, I found that we need to correct some of the dummy declarations. When I send my pull request to Linus, I wish to squash these changes into the original patches from Daniel. Could you please review? Best regards, ~Sumit ========= Dummy functions for the newly added cpu access ops are needed for compilation when dma-buf framework is not compiled-in. Also, the introduction of flags in dma_buf_fd needs to be added to dummy functions as well. Signed-off-by: Sumit Semwal <sumit.semwal(a)linaro.org> --- include/linux/dma-buf.h | 26 +++++++++++++------------- 1 files changed, 13 insertions(+), 13 deletions(-) diff --git a/include/linux/dma-buf.h b/include/linux/dma-buf.h index f08028e..779aaf9 100644 --- a/include/linux/dma-buf.h +++ b/include/linux/dma-buf.h @@ -189,7 +189,7 @@ static inline struct dma_buf *dma_buf_export(void *priv, return ERR_PTR(-ENODEV); } -static inline int dma_buf_fd(struct dma_buf *dmabuf) +static inline int dma_buf_fd(struct dma_buf *dmabuf, int flags) { return -ENODEV; } @@ -216,36 +216,36 @@ static inline void dma_buf_unmap_attachment(struct dma_buf_attachment *attach, return; } -static inline int dma_buf_begin_cpu_access(struct dma_buf *, - size_t, size_t, - enum dma_data_direction) +static inline int dma_buf_begin_cpu_access(struct dma_buf *dmabuf, + size_t start, size_t len, + enum dma_data_direction dir) { return -ENODEV; } -static inline void dma_buf_end_cpu_access(struct dma_buf *, - size_t, size_t, - enum dma_data_direction) +static inline void dma_buf_end_cpu_access(struct dma_buf *dmabuf, + size_t start, size_t len, + enum dma_data_direction dir) { } -static inline void *dma_buf_kmap_atomic(struct dma_buf *, unsigned long) +static inline void *dma_buf_kmap_atomic(struct dma_buf *db, unsigned long pnum) { return NULL; } -static inline void dma_buf_kunmap_atomic(struct dma_buf *, unsigned long, - void *) +static inline void dma_buf_kunmap_atomic(struct dma_buf *db, unsigned long pnum, + void *vaddr) { } -static inline void *dma_buf_kmap(struct dma_buf *, unsigned long) +static inline void *dma_buf_kmap(struct dma_buf *db, unsigned long pnum) { return NULL; } -static inline void dma_buf_kunmap(struct dma_buf *, unsigned long, - void *) +static inline void dma_buf_kunmap(struct dma_buf *db, unsigned long pnum, + void *vaddr) { } #endif /* CONFIG_DMA_SHARED_BUFFER */ -- 1.7.5.4

13 years, 1 month

dma-buf pull request content

by Sumit Semwal

Hello all, I intend to send the pull request to Linus by Monday - the set below looks to me to be the current content that it'd have on top of 3.3. [You can view this in for-next branch at git://git.linaro.org/people/sumitsemwal/linux-dma-buf.git] I think I could take the userspace mmap patch if we reach a consensus on which one to take (Rob's?, Daniel's?) - I guess we are most likely to agree on Daniel's, with possibly the suggestion from Rob about including IOCTLS but leaving them out of dmabuf ops for this release. Daniel, Rob: would you think I can have an agreed-upon patch by tomorrow afternoon? Then I could push it into for-next by tomorrow, and send a pull request by Monday? Also, if you think I've missed out something, please let me know. 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 (1): dma-buf: add dma_data_direction to unmap dma_buf_op -- Thanks and regards, Sumit Semwal Linaro Kernel Engineer - Graphics working group Linaro.org │ Open source software for ARM SoCs

13 years, 1 month

[PATCH] dma-buf: document fd flags and O_CLOEXEC requirement

by Rob Clark

From: Rob Clark <rob(a)ti.com> Otherwise subsystems will get this wrong and end up with a second export ioctl with the flag and O_CLOEXEC support added. Signed-off-by: Rob Clark <rob(a)ti.com> Reviewed-by: Daniel Vetter <daniel.vetter(a)ffwll.ch> --- Updated version of Daniel's original documentation patch with (hopefully) improved wording, and a better description of the motivation. Documentation/dma-buf-sharing.txt | 18 ++++++++++++++++++ 1 files changed, 18 insertions(+), 0 deletions(-) diff --git a/Documentation/dma-buf-sharing.txt b/Documentation/dma-buf-sharing.txt index 225f96d..3b51134 100644 --- a/Documentation/dma-buf-sharing.txt +++ b/Documentation/dma-buf-sharing.txt @@ -223,6 +223,24 @@ Miscellaneous notes: - Any exporters or users of the dma-buf buffer sharing framework must have a 'select DMA_SHARED_BUFFER' in their respective Kconfigs. +- In order to avoid fd leaks on exec, the FD_CLOEXEC flag must be set + on the file descriptor. This is not just a resource leak, but a + potential security hole. It could give the newly exec'd application + access to buffers, via the leaked fd, to which it should otherwise + not be permitted access. + + The problem with doing this via a separate fcntl() call, versus doing it + atomically when the fd is created, is that this is inherently racy in a + multi-threaded app[3]. The issue is made worse when it is library code + opening/creating the file descriptor, as the application may not even be + aware of the fd's. + + To avoid this problem, userspace must have a way to request O_CLOEXEC + flag be set when the dma-buf fd is created. So any API provided by + 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(). + References: [1] struct dma_buf_ops in include/linux/dma-buf.h [2] All interfaces mentioned above defined in include/linux/dma-buf.h +[3] https://lwn.net/Articles/236486/ -- 1.7.5.4

13 years, 1 month

[PATCH 1/4] dma-buf: don't hold the mutex around map/unmap calls

by Daniel Vetter

The mutex protects the attachment list and hence needs to be held around the callbakc to the exporters (optional) attach/detach functions. Holding the mutex around the map/unmap calls doesn't protect any dma_buf state. Exporters need to properly protect any of their own state anyway (to protect against calls from their own interfaces). So this only makes the locking messier (and lockdep easier to anger). Therefore let's just drop this. v2: Rebased on top of latest dma-buf-next git. Signed-off-by: Daniel Vetter <daniel.vetter(a)ffwll.ch> Reviewed-by: Rob Clark <rob.clark(a)linaro.org> --- drivers/base/dma-buf.c | 5 ----- include/linux/dma-buf.h | 2 +- 2 files changed, 1 insertions(+), 6 deletions(-) diff --git a/drivers/base/dma-buf.c b/drivers/base/dma-buf.c index 3c8c023..5641b9c 100644 --- a/drivers/base/dma-buf.c +++ b/drivers/base/dma-buf.c @@ -258,9 +258,7 @@ struct sg_table *dma_buf_map_attachment(struct dma_buf_attachment *attach, if (WARN_ON(!attach || !attach->dmabuf)) return ERR_PTR(-EINVAL); - mutex_lock(&attach->dmabuf->lock); sg_table = attach->dmabuf->ops->map_dma_buf(attach, direction); - mutex_unlock(&attach->dmabuf->lock); return sg_table; } @@ -282,10 +280,7 @@ void dma_buf_unmap_attachment(struct dma_buf_attachment *attach, if (WARN_ON(!attach || !attach->dmabuf || !sg_table)) return; - mutex_lock(&attach->dmabuf->lock); attach->dmabuf->ops->unmap_dma_buf(attach, sg_table, direction); - mutex_unlock(&attach->dmabuf->lock); - } EXPORT_SYMBOL_GPL(dma_buf_unmap_attachment); diff --git a/include/linux/dma-buf.h b/include/linux/dma-buf.h index bc4203dc..24e0f48 100644 --- a/include/linux/dma-buf.h +++ b/include/linux/dma-buf.h @@ -88,7 +88,7 @@ struct dma_buf { struct file *file; struct list_head attachments; const struct dma_buf_ops *ops; - /* mutex to serialize list manipulation and other ops */ + /* mutex to serialize list manipulation and attach/detach */ struct mutex lock; void *priv; }; -- 1.7.7.5

13 years, 1 month

[PATCH] [RFC] dma-buf: mmap support

by Daniel Vetter

Let's have some competition here for dma_buf mmap support ;-) Compared to Rob Clarke'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 taht 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. Comments, reviews and flames highly welcome. Cheers, Daniel --- Documentation/dma-buf-sharing.txt | 84 +++++++++++++++++++++++++++++++++--- drivers/base/dma-buf.c | 64 +++++++++++++++++++++++++++- include/linux/dma-buf.h | 16 +++++++ 3 files changed, 156 insertions(+), 8 deletions(-) diff --git a/Documentation/dma-buf-sharing.txt b/Documentation/dma-buf-sharing.txt index a6d4c37..c42a4a5 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 ------------------- diff --git a/drivers/base/dma-buf.c b/drivers/base/dma-buf.c index 07cbbc6..f3b923c 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_areat_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 ee7ef99..d254630 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, @@ -247,6 +256,13 @@ static inline void dma_buf_kunmap(struct dma_buf *, unsigned long, void *) { } + +static inline int dma_buf_mmap(struct dma_buf *, + struct vm_area_struct *vma, + unsigned long pgoff) +{ + return -ENODEV; +} #endif /* CONFIG_DMA_SHARED_BUFFER */ #endif /* __DMA_BUF_H__ */ -- 1.7.7.5

13 years, 1 month

税务风险~规避技~巧与实务

by 企业税务稽查

13 years, 1 month

[PATCH 0/4] Miscellaneous dma-buf patches

by Laurent Pinchart

Hi Sumit, Here are 4 dma-buf patches that fix small issues. 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() drivers/base/dma-buf.c | 26 +++++++++++--------------- include/linux/dma-buf.h | 8 ++++---- 2 files changed, 15 insertions(+), 19 deletions(-) -- Regards, Laurent Pinchart

13 years, 1 month

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig