Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MetaSchedule][M4a] Rewrite-Cooperative-Fetch #10081

Merged
merged 1 commit into from
Jan 29, 2022

Conversation

Hzfengsy
Copy link
Member

It is one of the PostProc for mate-schedule. Please see the tracking issue #8473

Co-authored-by: Junru Shao [email protected]
Co-authored-by: Xiyou Zhou [email protected]
Co-authored-by: Bohan Hou [email protected]
Co-authored-by: Ruihang Lai [email protected]
Co-authored-by: Hongyi Jin [email protected]
Co-authored-by: Wuwei Lin [email protected]

cc @junrushao1994 @comaniac

@Hzfengsy Hzfengsy changed the title [MetaSchedule] postproc: rewrite_cooperative_fetch [MetaSchedule][M4a] Rewrite cooperative fetch Jan 27, 2022
@junrushao junrushao changed the title [MetaSchedule][M4a] Rewrite cooperative fetch [MetaSchedule][M4a] Rewrite-Cooperative-Fetch Jan 27, 2022
@junrushao
Copy link
Member

Hey please rebase to the latest main

@Hzfengsy Hzfengsy force-pushed the rewrite-cooperative-fetch branch from d90b791 to 4c3ba47 Compare January 28, 2022 06:44
Copy link
Contributor

@MasterJH5574 MasterJH5574 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Only have some nits. Thank you Siyuan!

src/meta_schedule/postproc/rewrite_cooperative_fetch.cc Outdated Show resolved Hide resolved
src/meta_schedule/postproc/rewrite_cooperative_fetch.cc Outdated Show resolved Hide resolved
src/meta_schedule/postproc/rewrite_cooperative_fetch.cc Outdated Show resolved Hide resolved
@Hzfengsy Hzfengsy force-pushed the rewrite-cooperative-fetch branch from 4c3ba47 to ce52b56 Compare January 29, 2022 05:53
Co-authored-by: Junru Shao <[email protected]>
Co-authored-by: Xiyou Zhou <[email protected]>
Co-authored-by: Bohan Hou <[email protected]>
Co-authored-by: Ruihang Lai <[email protected]>
Co-authored-by: Hongyi Jin <[email protected]>
Co-authored-by: Wuwei Lin <[email protected]>
@Hzfengsy Hzfengsy force-pushed the rewrite-cooperative-fetch branch from ce52b56 to 70c014e Compare January 29, 2022 06:27
@spectrometerHBH spectrometerHBH merged commit 538347e into apache:main Jan 29, 2022
ylc pushed a commit to ylc/tvm that referenced this pull request Feb 16, 2022
Co-authored-by: Junru Shao <[email protected]>
Co-authored-by: Xiyou Zhou <[email protected]>
Co-authored-by: Bohan Hou <[email protected]>
Co-authored-by: Ruihang Lai <[email protected]>
Co-authored-by: Hongyi Jin <[email protected]>
Co-authored-by: Wuwei Lin <[email protected]>

Co-authored-by: Junru Shao <[email protected]>
Co-authored-by: Xiyou Zhou <[email protected]>
Co-authored-by: Bohan Hou <[email protected]>
Co-authored-by: Ruihang Lai <[email protected]>
Co-authored-by: Hongyi Jin <[email protected]>
Co-authored-by: Wuwei Lin <[email protected]>
tir::ParseThreadBinding(sch, inst, "threadIdx.y")) {
thread_extent_y = new_thread_extent.value()->value;
} else if (Optional<tir::BlockRV> block_rv = tir::ParseAnnotate(sch, inst, &vector_lane)) {
ICHECK_NE(thread_extent_x, -1);
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this check necessary here? I am hitting this check with a simple matmul_fp16 example with rules and postprocs like in test_meta_schedule_tune_tir and I wonder if more details about this check can be elaborated here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it means threadIdx.x isn't bound in previous instructions, which isn't supposed to happen (and that's why it's an ICHECK instead of CHECK). Could you check the trace->insts and see why threadIdx.x doesn't exist previously

@Hzfengsy Hzfengsy deleted the rewrite-cooperative-fetch branch February 2, 2024 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants