CUDA Kernels: Use per-operator headers (3/4) #71214

peterbell10 · 2022-01-12T15:45:16Z

Stack from ghstack (oldest at bottom):

Splitting this into multiple PRs to keep the diffs more managable.

Differential Revision: D33949897

Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

pytorch-probot · 2022-01-12T15:45:19Z

CI Flow Status

⚛️ CI Flow

Ruleset - Version: v1
Ruleset - File: https://github.com/pytorch/pytorch/blob/6ef39d0dbc88cf0b295be156bb287e9984245aa9/.github/generated-ciflow-ruleset.json
PR ciflow labels: ciflow/default,ciflow/cuda

Workflows	Labels (bold enabled)	Status
Triggered Workflows
libtorch-linux-xenial-cuda10.2-py3.7-gcc7	`ciflow/all`, `ciflow/cuda`, `ciflow/libtorch`, `ciflow/linux`, `ciflow/trunk`	✅ triggered
libtorch-linux-xenial-cuda11.3-py3.7-gcc7	`ciflow/all`, `ciflow/cuda`, `ciflow/libtorch`, `ciflow/linux`, `ciflow/trunk`	✅ triggered
linux-binary-conda	`ciflow/binaries`, `ciflow/binaries_conda`, `ciflow/default`	✅ triggered
linux-binary-libtorch-cxx11-abi	`ciflow/binaries`, `ciflow/binaries_libtorch`, `ciflow/default`	✅ triggered
linux-binary-libtorch-pre-cxx11	`ciflow/binaries`, `ciflow/binaries_libtorch`, `ciflow/default`	✅ triggered
linux-binary-manywheel	`ciflow/binaries`, `ciflow/binaries_wheel`, `ciflow/default`	✅ triggered
linux-bionic-cuda10.2-py3.9-gcc7	`ciflow/all`, `ciflow/cuda`, `ciflow/linux`, `ciflow/slow`, `ciflow/trunk`	✅ triggered
linux-bionic-py3.7-clang9	`ciflow/all`, `ciflow/cpu`, `ciflow/default`, `ciflow/linux`, `ciflow/noarch`, `ciflow/trunk`, `ciflow/xla`	✅ triggered
linux-docs	`ciflow/all`, `ciflow/cpu`, `ciflow/default`, `ciflow/docs`, `ciflow/linux`, `ciflow/trunk`	✅ triggered
linux-vulkan-bionic-py3.7-clang9	`ciflow/all`, `ciflow/cpu`, `ciflow/default`, `ciflow/linux`, `ciflow/trunk`, `ciflow/vulkan`	✅ triggered
linux-xenial-cuda11.3-py3.7-gcc7	`ciflow/all`, `ciflow/cuda`, `ciflow/default`, `ciflow/linux`, `ciflow/trunk`	✅ triggered
linux-xenial-cuda11.3-py3.7-gcc7-bazel-test	`ciflow/all`, `ciflow/bazel`, `ciflow/cpu`, `ciflow/default`, `ciflow/linux`, `ciflow/trunk`	✅ triggered
linux-xenial-cuda11.3-py3.7-gcc7-no-ops	`ciflow/all`, `ciflow/cuda`, `ciflow/linux`, `ciflow/trunk`	✅ triggered
linux-xenial-py3-clang5-mobile-build	`ciflow/all`, `ciflow/default`, `ciflow/linux`, `ciflow/mobile`, `ciflow/trunk`	✅ triggered
linux-xenial-py3-clang5-mobile-custom-build-static	`ciflow/all`, `ciflow/default`, `ciflow/linux`, `ciflow/mobile`, `ciflow/trunk`	✅ triggered
linux-xenial-py3.7-clang7-asan	`ciflow/all`, `ciflow/cpu`, `ciflow/default`, `ciflow/linux`, `ciflow/sanitizers`, `ciflow/trunk`	✅ triggered
linux-xenial-py3.7-clang7-onnx	`ciflow/all`, `ciflow/cpu`, `ciflow/default`, `ciflow/linux`, `ciflow/onnx`, `ciflow/trunk`	✅ triggered
linux-xenial-py3.7-gcc5.4	`ciflow/all`, `ciflow/cpu`, `ciflow/default`, `ciflow/linux`, `ciflow/trunk`	✅ triggered
linux-xenial-py3.7-gcc7	`ciflow/all`, `ciflow/cpu`, `ciflow/default`, `ciflow/linux`, `ciflow/trunk`	✅ triggered
linux-xenial-py3.7-gcc7-no-ops	`ciflow/all`, `ciflow/cpu`, `ciflow/default`, `ciflow/linux`, `ciflow/trunk`	✅ triggered
periodic-libtorch-linux-bionic-cuda11.5-py3.7-gcc7	`ciflow/all`, `ciflow/cuda`, `ciflow/libtorch`, `ciflow/linux`, `ciflow/scheduled`	✅ triggered
periodic-libtorch-linux-xenial-cuda11.1-py3.7-gcc7	`ciflow/all`, `ciflow/cuda`, `ciflow/libtorch`, `ciflow/linux`, `ciflow/scheduled`	✅ triggered
periodic-linux-bionic-cuda11.5-py3.7-gcc7	`ciflow/all`, `ciflow/cuda`, `ciflow/linux`, `ciflow/scheduled`	✅ triggered
periodic-linux-xenial-cuda10.2-py3-gcc7-slow-gradcheck	`ciflow/all`, `ciflow/cuda`, `ciflow/linux`, `ciflow/scheduled`, `ciflow/slow`, `ciflow/slow-gradcheck`	✅ triggered
periodic-linux-xenial-cuda11.1-py3.7-gcc7-debug	`ciflow/all`, `ciflow/cuda`, `ciflow/linux`, `ciflow/scheduled`	✅ triggered
periodic-win-vs2019-cuda11.1-py3	`ciflow/all`, `ciflow/cuda`, `ciflow/scheduled`, `ciflow/win`	✅ triggered
periodic-win-vs2019-cuda11.5-py3	`ciflow/all`, `ciflow/cuda`, `ciflow/scheduled`, `ciflow/win`	✅ triggered
pytorch-linux-xenial-py3-clang5-android-ndk-r19c-gradle-custom-build-single	`ciflow/all`, `ciflow/android`, `ciflow/cpu`, `ciflow/default`, `ciflow/linux`, `ciflow/trunk`	✅ triggered
pytorch-linux-xenial-py3-clang5-android-ndk-r19c-gradle-custom-build-single-full-jit	`ciflow/all`, `ciflow/android`, `ciflow/cpu`, `ciflow/default`, `ciflow/linux`, `ciflow/trunk`	✅ triggered
win-vs2019-cpu-py3	`ciflow/all`, `ciflow/cpu`, `ciflow/default`, `ciflow/trunk`, `ciflow/win`	✅ triggered
win-vs2019-cuda11.3-py3	`ciflow/all`, `ciflow/cuda`, `ciflow/default`, `ciflow/trunk`, `ciflow/win`	✅ triggered
Skipped Workflows
caffe2-linux-xenial-py3.7-gcc5.4	`ciflow/all`, `ciflow/cpu`, `ciflow/linux`, `ciflow/trunk`	🚫 skipped
docker-builds	`ciflow/all`, `ciflow/trunk`	🚫 skipped
ios-12-5-1-arm64	`ciflow/all`, `ciflow/ios`, `ciflow/macos`, `ciflow/trunk`	🚫 skipped
ios-12-5-1-arm64-coreml	`ciflow/all`, `ciflow/ios`, `ciflow/macos`, `ciflow/trunk`	🚫 skipped
ios-12-5-1-arm64-custom-ops	`ciflow/all`, `ciflow/ios`, `ciflow/macos`, `ciflow/trunk`	🚫 skipped
ios-12-5-1-arm64-full-jit	`ciflow/all`, `ciflow/ios`, `ciflow/macos`, `ciflow/trunk`	🚫 skipped
ios-12-5-1-arm64-metal	`ciflow/all`, `ciflow/ios`, `ciflow/macos`, `ciflow/trunk`	🚫 skipped
ios-12-5-1-x86-64	`ciflow/all`, `ciflow/ios`, `ciflow/macos`, `ciflow/trunk`	🚫 skipped
ios-12-5-1-x86-64-coreml	`ciflow/all`, `ciflow/ios`, `ciflow/macos`, `ciflow/trunk`	🚫 skipped
ios-12-5-1-x86-64-full-jit	`ciflow/all`, `ciflow/ios`, `ciflow/macos`, `ciflow/trunk`	🚫 skipped
linux-bionic-rocm4.5-py3.7	`ciflow/all`, `ciflow/linux`, `ciflow/rocm`, `ciflow/trunk`	🚫 skipped
linux-docs-push	`ciflow/all`, `ciflow/cpu`, `ciflow/linux`, `ciflow/scheduled`	🚫 skipped
macos-10-15-py3-arm64	`ciflow/all`, `ciflow/macos`, `ciflow/trunk`	🚫 skipped
macos-10-15-py3-lite-interpreter-x86-64	`ciflow/all`, `ciflow/macos`, `ciflow/trunk`	🚫 skipped
macos-11-py3-x86-64	`ciflow/all`, `ciflow/macos`, `ciflow/trunk`	🚫 skipped
parallelnative-linux-xenial-py3.7-gcc5.4	`ciflow/all`, `ciflow/cpu`, `ciflow/linux`, `ciflow/trunk`	🚫 skipped
pytorch-linux-xenial-py3-clang5-android-ndk-r19c-build	`ciflow/all`, `ciflow/android`, `ciflow/cpu`, `ciflow/linux`, `ciflow/trunk`	🚫 skipped

You can add a comment to the PR and tag @pytorchbot with the following commands:

# ciflow rerun, "ciflow/default" will always be added automatically
@pytorchbot ciflow rerun

# ciflow rerun with additional labels "-l <ciflow/label_name>", which is equivalent to adding these labels manually and trigger the rerun
@pytorchbot ciflow rerun -l ciflow/scheduled -l ciflow/slow

For more information, please take a look at the CI Flow Wiki.

facebook-github-bot · 2022-01-12T15:45:27Z

🔗 Helpful links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/71214
📄 Preview Python docs built from this PR
📄 Preview C++ docs built from this PR
❓Need help or want to give feedback on the CI? Visit our office hours

💊 CI failures summary and remediations

As of commit 27c70a3 (more details on the Dr. CI page):

💚 💚 Looks good so far! There are no failures yet. 💚 💚

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

malfet · 2022-02-02T19:33:47Z

@malfet has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

Splitting this into multiple PRs to keep the diffs more managable. ghstack-source-id: 903c0c4 Pull Request resolved: pytorch#71214

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

malfet · 2022-03-03T21:32:32Z

@malfet has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

Splitting this into multiple PRs to keep the diffs more managable. ghstack-source-id: 64ff7bb Pull Request resolved: pytorch#71214

Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

malfet · 2022-04-07T16:56:35Z

@malfet has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

Summary: Pull Request resolved: #71214 Splitting this into multiple PRs to keep the diffs more managable. Test Plan: Imported from OSS Reviewed By: ngimel Differential Revision: D33949897 Pulled By: malfet fbshipit-source-id: 3ba6b4b8083fe97e11644688f9d90a4ec217fedc

CUDA Kernels: Use per-operator headers (3/4)

2d32c9b

Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

pytorch-probot bot added the ciflow/default label Jan 12, 2022

facebook-github-bot added the cla signed label Jan 12, 2022

peterbell10 added the ciflow/cuda label Jan 12, 2022

pytorchbot added the open source label Jan 12, 2022

Update on "CUDA Kernels: Use per-operator headers (3/4)"

325bb3a

Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

peterbell10 added 4 commits January 12, 2022 19:04

Update on "CUDA Kernels: Use per-operator headers (3/4)"

0c132db

Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

Update on "CUDA Kernels: Use per-operator headers (3/4)"

d2bee37

Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

Update on "CUDA Kernels: Use per-operator headers (3/4)"

29f0e4b

Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

Update on "CUDA Kernels: Use per-operator headers (3/4)"

a93d6ea

Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

Update on "CUDA Kernels: Use per-operator headers (3/4)"

6ef39d0

Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

Rebase and fix merge conflicts on "CUDA Kernels: Use per-operator hea…

582c3b1

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

peterbell10 requested a review from malfet January 24, 2022 02:08

peterbell10 marked this pull request as ready for review January 24, 2022 02:08

peterbell10 added 2 commits January 31, 2022 19:47

Rebase and fix merge conflicts on "CUDA Kernels: Use per-operator hea…

03243c3

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

Update on "CUDA Kernels: Use per-operator headers (3/4)"

268f2f6

Splitting this into multiple PRs to keep the diffs more managable. [ghstack-poisoned]

malfet approved these changes Feb 2, 2022

View reviewed changes

peterbell10 added 2 commits February 7, 2022 20:33

Rebase on master on "CUDA Kernels: Use per-operator headers (3/4)"

169a4d1

Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

Rebase and fix merge conflicts on "CUDA Kernels: Use per-operator hea…

d3452c8

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

peterbell10 added a commit to peterbell10/pytorch that referenced this pull request Feb 8, 2022

CUDA Kernels: Use per-operator headers (3/4)

78fa505

Splitting this into multiple PRs to keep the diffs more managable. ghstack-source-id: 903c0c4 Pull Request resolved: pytorch#71214

peterbell10 added 4 commits February 14, 2022 14:51

Rebase and fix merge conflicts on "CUDA Kernels: Use per-operator hea…

f87b712

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

Rebase and fix merge conflicts on "CUDA Kernels: Use per-operator hea…

c6defae

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

Rebase and fix merge conflicts on "CUDA Kernels: Use per-operator hea…

346270b

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

Rebase and fix merge conflicts on "CUDA Kernels: Use per-operator hea…

1311a9c

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

Rebase and fix merge conflicts on "CUDA Kernels: Use per-operator hea…

83ac8b4

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

peterbell10 added a commit to peterbell10/pytorch that referenced this pull request Mar 17, 2022

CUDA Kernels: Use per-operator headers (3/4)

7d7f054

Splitting this into multiple PRs to keep the diffs more managable. ghstack-source-id: 64ff7bb Pull Request resolved: pytorch#71214

peterbell10 added a commit to peterbell10/pytorch that referenced this pull request Mar 21, 2022

CUDA Kernels: Use per-operator headers (3/4)

aba2216

Splitting this into multiple PRs to keep the diffs more managable. ghstack-source-id: 64ff7bb Pull Request resolved: pytorch#71214

Rebase on "CUDA Kernels: Use per-operator headers (3/4)"

0b536ee

Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

suo removed the ciflow/default label Mar 22, 2022

Rebase and fix merge conflicts on "CUDA Kernels: Use per-operator hea…

37b036e

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

Rebase and fix merge conflicts on "CUDA Kernels: Use per-operator hea…

0ab68d5

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

Rebase and fix merge conflicts on "CUDA Kernels: Use per-operator hea…

27c70a3

…ders (3/4)" Splitting this into multiple PRs to keep the diffs more managable. Differential Revision: [D33949897](https://our.internmc.facebook.com/intern/diff/D33949897) [ghstack-poisoned]

pytorchmergebot closed this in cd62bbf Apr 7, 2022

peterbell10 added the topic: not user facing topic category label Apr 7, 2022

facebook-github-bot deleted the gh/peterbell10/254/head branch April 11, 2022 14:17

WBobby mentioned this pull request Aug 17, 2022

Add ROCm5.2.3/AMDGPU support for PyTorch WBobby/pytorch#2

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

CUDA Kernels: Use per-operator headers (3/4) #71214

CUDA Kernels: Use per-operator headers (3/4) #71214

Uh oh!

peterbell10 commented Jan 12, 2022 •

edited

Loading

Uh oh!

pytorch-probot bot commented Jan 12, 2022 •

edited by pytorch-bot bot

Loading

⚛️ CI Flow

Uh oh!

facebook-github-bot commented Jan 12, 2022 •

edited

Loading

Uh oh!

malfet commented Feb 2, 2022

Uh oh!

malfet commented Mar 3, 2022

Uh oh!

malfet commented Apr 7, 2022

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

CUDA Kernels: Use per-operator headers (3/4) #71214

CUDA Kernels: Use per-operator headers (3/4) #71214

Uh oh!

Conversation

peterbell10 commented Jan 12, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pytorch-probot bot commented Jan 12, 2022 • edited by pytorch-bot bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚛️ CI Flow

Uh oh!

facebook-github-bot commented Jan 12, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔗 Helpful links

💊 CI failures summary and remediations

Uh oh!

malfet commented Feb 2, 2022

Uh oh!

malfet commented Mar 3, 2022

Uh oh!

malfet commented Apr 7, 2022

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

peterbell10 commented Jan 12, 2022 •

edited

Loading

pytorch-probot bot commented Jan 12, 2022 •

edited by pytorch-bot bot

Loading

facebook-github-bot commented Jan 12, 2022 •

edited

Loading