tree 15a71853e8f1f54aea5855899ff1cfaa79b469cd
parent ca258bcd0dea4d22b4dddc9ef05382d6bd61afd3
author MaheshRavishankar <1663364+MaheshRavishankar@users.noreply.github.com> 1656637453 -0700
committer GitHub <noreply@github.com> 1656637453 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJivkgOCRBK7hj4Ov3rIwAAZ/cIAEkiX8I4r62UFjdRs21ve1cS
 /UZYUNMeqYTwFbldQSNG7Zv+shh2ueMsVvfOGZKNnbweD0V3sr4S59ytURdFi2B0
 wvviqF9WhaO/FTGMxvi6N50nW7HZuS38MNaDfq6AwFc0SfhWLvWxyCPdjheLspO9
 5llgTR3LUS6qhOlGGADoePwh+kkQLXYkSCkyN9d+BUyLUZrXPAG/6XXqsIoi/zqS
 qcJvUyhKaZ7c043TO1Vvp0tzxXqPuyhep7xg80LxlYYv0bs5kGHDioy2Z7zvzy0h
 33r34kzmFNpkCUGApqo3/HId2u7d50gz0oYBY/P8TTcmawtI0kHOPxcSM2xABto=
 =7CkG
 -----END PGP SIGNATURE-----
 

Add `flow.dispatch.default_workgroup_count` op. (#9681)

This commit adds an operation flow.dispatch.default_workgroup_count that
captures the relationship between the workload and workgroup_count at
the Flow level. This is populated now at the Flow level and carried
through to the HAL layer. There the backends lower this operation to
the actual computation that returns the workgroup count.

There could be many such ops. The current operation is just reflacting
the computation that is done today in the backend. In future more such
operations and corresponding lowerings in the backends could be added.

With this change, the backend expects the workgroup_count region to
be populated always.