From: "Wang, Bin" <bin.wang-at-intel.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v7] libavfilter/x86/vf_convolution: add sobel filter optimization and unit test with intel AVX512 VNNI Date: Mon, 14 Nov 2022 15:18:58 +0000 Message-ID: <BN6PR11MB174621467F5B9134EBCB420E9B059@BN6PR11MB1746.namprd11.prod.outlook.com> (raw) In-Reply-To: <0325e6b2-782c-1891-277a-a40d88039f17@gmail.com> > >> On 11/14/2022 10:30 AM, Wang, Bin wrote: > >>>> By using xmm# you're not taking into account any x86inc SWAPing, so > >>>> this is using xmm0 and xmm1 where the single scalar float input > >>>> arguments reside (at least on unix64), instead of xm0 and xm1 > >>>> (xmm16 and xmm17) where the broadcasted scalars were stored. > >>>> This, again, only worked by chance on unix64 because you're using > >>>> scalar fmadd, and shouldn't work at all on win64. > >>>> > >>>> Also, all these as is are being encoded as VEX, not EVEX, but it > >>>> should be fine leaving them untouched instead of using xm#, since > >>>> they will be shorter (five bytes instead of six for some) by using > >>>> the lower, > >> non callee-saved regs. > >>> > >>> Thanks for the help. I'm not familiar with WIN64 asm. So what I need > >>> to do is > >> change the WIN64 swap from: > >>> SWAP xmm0, xmm2 > >>> SWAP xmm1, xmm3 > >>> To: > >>> VBROADCASTSS m0, xmm2 > >>> VBROADCASTSS m1, xmm3 > >>> > >>> Is that correct? > >> > >> Yes, that will ultimately broadcast the two scalars in xmm2 and xmm3 > >> to > >> zmm16 and zmm17. > >> After that what you need to do is either change the fmaddss > >> instruction to use > >> xm0 and xm1 macros instead of xmm0 and xmm1 (so xmm16 and xmm17 > with > >> EVEX encoding is used), or much like the broadcast above use xmm2 and > >> xmm3 explicitly on win64, so it remains VEX encoded. > > > > So, to fix the issue, does this 2 changes looks good for you? > > First change the WIN64 swap from: > > SWAP xmm0, xmm2 > > SWAP xmm1, xmm3 > > To: > > VBROADCASTSS m0, xmm2 > > VBROADCASTSS m1, xmm3 > > > > Second change the fmaddss from: > > fmaddss xmm4, xmm4, xmm0, xmm1 > > To: > > fmaddss xmm4, xmm4, xm0, xm1 > > Yes. Appreciate for your help, I commit new patch here: https://patchwork.ffmpeg.org/project/ffmpeg/patch/20221114143551.9740-1-bin.wang@intel.com/ > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org > with subject "unsubscribe". _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2022-11-14 15:22 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-04 8:29 bin.wang-at-intel.com 2022-11-07 5:24 ` Xiang, Haihao 2022-11-11 3:00 ` Xiang, Haihao 2022-11-14 2:12 ` Xiang, Haihao 2022-11-14 2:42 ` James Almer 2022-11-14 5:58 ` Wang, Bin 2022-11-14 11:34 ` James Almer 2022-11-14 12:54 ` James Almer 2022-11-14 13:30 ` Wang, Bin 2022-11-14 13:35 ` James Almer 2022-11-14 13:54 ` Wang, Bin 2022-11-14 14:31 ` James Almer 2022-11-14 15:18 ` Wang, Bin [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=BN6PR11MB174621467F5B9134EBCB420E9B059@BN6PR11MB1746.namprd11.prod.outlook.com \ --to=bin.wang-at-intel.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git