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

[Enhancement] Add torch mluops check before calling mluOpsxxx interface #2871

Merged
merged 2 commits into from
Aug 3, 2023

Conversation

ClowDragon
Copy link
Contributor

@ClowDragon ClowDragon commented Jul 18, 2023

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.

Motivation

insert TORCH_MLUOP_CHECK macro to make sure all mluOp interface return MLUOP_STATUS_SUCCESS

Modification

add TORCH_MLUOP_CHECK before all mluOpxxx interface under mmcv/ops/csrc/pytorch/mlu directory

BC-breaking (Optional)

Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
No.
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.

Use cases (Optional)

If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.

Checklist

Before PR:

  • I have read and followed the workflow indicated in the CONTRIBUTING.md to create this PR.
  • Pre-commit or linting tools indicated in CONTRIBUTING.md are used to fix the potential lint issues.
  • Bug fixes are covered by unit tests, the case that causes the bug should be added in the unit tests.
  • New functionalities are covered by complete unit tests. If not, please add more unit test to ensure the correctness.
  • The documentation has been modified accordingly, including docstring or example tutorials.

After PR:

  • If the modification has potential influence on downstream or other related projects, this PR should be tested with some of those projects, like MMDet or MMCls.
  • CLA has been signed and all committers have signed the CLA in this PR.

@CLAassistant
Copy link

CLAassistant commented Jul 18, 2023

CLA assistant check
All committers have signed the CLA.

@ClowDragon ClowDragon changed the title feat(op_check): add torch mluops check before call mluOpsxxx interface [Enhancement] Add torch mluops check before call mluOpsxxx interface Jul 24, 2023
@OpenMMLab-Assistant-004

Hi @ClowDragon,

We'd like to express our appreciation for your valuable contributions to the mmcv. Your efforts have significantly aided in enhancing the project's quality.
It is our pleasure to invite you to join our community thorugh Discord_Special Interest Group (SIG) channel. This is a great place to share your experiences, discuss ideas, and connect with other like-minded people. To become a part of the SIG channel, send a message to the moderator, OpenMMLab, briefly introduce yourself and mention your open-source contributions in the #introductions channel. Our team will gladly facilitate your entry. We eagerly await your presence. Please follow this link to join us: ​https://discord.gg/UjgXkPWNqA.

If you're on WeChat, we'd also love for you to join our community there. Just add our assistant using the WeChat ID: openmmlabwx. When sending the friend request, remember to include the remark "mmsig + Github ID".

Thanks again for your awesome contribution, and we're excited to have you as part of our community!

@zhouzaida zhouzaida added the MLU label Aug 3, 2023
@zhouzaida zhouzaida changed the title [Enhancement] Add torch mluops check before call mluOpsxxx interface [Enhancement] Add torch mluops check before calling mluOpsxxx interface Aug 3, 2023
@zhouzaida zhouzaida merged commit ad7284e into open-mmlab:main Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants