8000 ZeroTensor with 'cuda' device doesn't correctly set the CUDA dispatch key · Issue #71160 · pytorch/pytorch · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

ZeroTensor with 'cuda' device doesn't correctly set the CUDA dispatch key #71160

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.

Sign up for GitHub

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

Jump to bottom
Closed
anjali411 opened this issue Jan 11, 2022 · 1 comment
Closed

ZeroTensor with 'cuda' device doesn't correctly set the CUDA dispatch key #71160

anjali411 opened this issue Jan 11, 2022 · 1 comment
Labels
triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module ZeroTensor

Comments

@anjali411
Copy link
Contributor
anjali411 commented Jan 11, 2022 •
edited
Loading

🐛 Describe the bug

>>> torch._efficientzerotensor(3, device='cuda').is_cuda
False

Versions

Master

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @lezcano @Varal7
@anjali411 anjali411 added triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module module: autograd Related to torch.autograd, and the autograd engine in general labels Jan 11, 2022
@anjali411
Copy link
Contributor Author

Additionally the cuda device index is also not set which causes device checks to fail when the op is registered as fallthrough.

>>> y=torch.randn(4, device='cuda')
>>> z=torch._efficientzerotensor(4, device='cuda')
>>> y.device
device(type='cuda', index=0)
>>> z.device
device(type='cuda')

@anjali411 anjali411 added ZeroTensor and removed module: autograd Related to torch.autograd, and the autograd engine in general labels Jan 19, 2022
@anjali411 anjali411 mentioned this issue Jan 24, 2022
Closed
anjali411 added a commit that referenced this issue Jan 24, 2022
@anjali411
Update base for Update on "Set correct device id on efficientzerotens…
768fa97 
…ors"


Fixes #71160 

[ghstack-poisoned]
anjali411 added a commit that referenced this issue Jan 24, 2022
@anjali411
Update on "Set correct device id on efficientzerotensors"
0c745c3 
Fixes #71160 

[ghstack-poisoned]
@soulitzer soulitzer mentioned this issue Jan 24, 2022
Closed
anjali411 added a commit that referenced this issue Jan 25, 2022
@anjali411
Update base for Update on "Set correct device id on efficientzerotens…
82bf7e1 
…ors"


Fixes #71160 #69925

Differential Revision: [D33768645](https://our.internmc.facebook.com/intern/diff/D33768645)

[ghstack-poisoned]
anjali411 added a commit that referenced this issue Jan 25, 2022
@anjali411
Update on "Set correct device id on efficientzerotensors"
baeaa43 
Fixes #71160 #69925

Differential Revision: [D33768645](https://our.internmc.facebook.com/intern/diff/D33768645)

[ghstack-poisoned]
facebook-github-bot pushed a commit that referenced this issue Jan 25, 2022
@anjali411 @facebook-github-bot
Set correct device id on efficientzerotensors (#71611)
3af98a4 
Summary:
Pull Request resolved: #71611

Fixes #71160

Test Plan: Imported from OSS

Reviewed By: pbelevich, ngimel

Differential Revision: D33768645

Pulled By: anjali411

fbshipit-source-id: 66ce9907630b65a12c0775077147a7e72ff4cee4
pytorchmergebot pushed a commit that referenced this issue Jan 25, 2022
@anjali411 @pytorchmergebot
Set correct device id on efficientzerotensors (#71611)
5dd6cd5 
Summary:
Pull Request resolved: #71611

Fixes #71160

Test Plan: Imported from OSS

Reviewed By: pbelevich, ngimel

Differential Revision: D33768645

Pulled By: anjali411

fbshipit-source-id: 66ce9907630b65a12c0775077147a7e72ff4cee4
(cherry picked from commit 3af98a4)
anjali411 added a commit that referenced this issue Jan 26, 2022
@anjali411
Update base for Update on "Set correct device id on efficientzerotens…
dabd60a 
…ors"


Fixes #71160 #69925


[ghstack-poisoned]
anjali411 added a commit that referenced this issue Jan 26, 2022
@anjali411
Update on "Set correct device id on efficientzerotensors"
77edd87 
Fixes #71160 #69925


[ghstack-poisoned]
anjali411 added a commit that referenced this issue Jan 28, 2022
@anjali411
Update base for Update on "Set correct device id on efficientzerotens…
d2a7ccf 
…ors"


Fixes #71160 #69925


[ghstack-poisoned]
anjali411 added a commit that referenced this issue Jan 28, 2022
@anjali411
Update on "Set correct device id on efficientzerotensors"
ec0fd76 
Fixes #71160 #69925


[ghstack-poisoned]
anjali411 added a commit that referenced this issue Jan 28, 2022
@anjali411
Update base for Update on "Set correct device id on efficientzerotens…
44742f0 
…ors"


Fixes #71160 #69925


[ghstack-poisoned]
anjali411 added a commit that referenced this issue Jan 28, 2022
@anjali411
Update on "Set correct device id on efficientzerotensors"
3e96c8f 
Fixes #71160 #69925


[ghstack-poisoned]
anjali411 added a commit that referenced this issue Jan 28, 2022
@anjali411
Update base for Update on "Set correct device id on efficientzerotens…
3066e90 
…ors"


Fixes #71160 #69925

Differential Revision: [D33834916](https://our.internmc.facebook.com/intern/diff/D33834916)

[ghstack-poisoned]
anjali411 added a commit that referenced this issue Jan 28, 2022
@anjali411
Update on "Set correct device id on efficientzerotensors"
74f009d 
Fixes #71160 #69925

Differential Revision: [D33834916](https://our.internmc.facebook.com/intern/diff/D33834916)

[ghstack-poisoned]
@anjali411 anjali411 reopened this Jan 28, 2022
anjali411 added a commit that referenced this issue Jan 28, 2022
@anjali411
Update base for Update on "Set correct device id on efficientzerotens…
91845c1 
…ors"


Fixes #71160 #69925

Differential Revision: [D33834916](https://our.internmc.facebook.com/intern/diff/D33834916)

[ghstack-poisoned]
anjali411 added a commit that referenced this issue Jan 28, 2022
@anjali411
Update on "Set correct device id on efficientzerotensors"
bca92dc 
Fixes #71160 #69925

Differential Revision: [D33834916](https://our.internmc.facebook.com/intern/diff/D33834916)

[ghstack-poisoned]
anjali411 added a commit that referenced this issue Jan 28, 2022
@anjali411
Update base for Update on "Set correct device id on efficientzerotens…
9fdb810 
…ors"


Fixes #71160 #69925

Differential Revision: [D33834916](https://our.internmc.facebook.com/intern/diff/D33834916)

[ghstack-poisoned]
anjali411 added a commit that referenced this issue Jan 28, 2022
@anjali411
Update on "Set correct device id on efficientzerotensors"
94ba4ea 
Fixes #71160 #69925

Differential Revision: [D33834916](https://our.internmc.facebook.com/intern/diff/D33834916)

[ghstack-poisoned]
facebook-github-bot pushed a commit that referenced this issue Jan 30, 2022
@anjali411 @facebook-github-bot
Set correct device id on efficientzerotensors (#71611)
f6e86f8 
Summary:
Pull Request resolved: #71611

Fixes #71160 #69925

Test Plan: Imported from OSS

Reviewed By: george-qi

Differential Revision: D33834916

Pulled By: anjali411

fbshipit-source-id: 11cec343e95e2ee188ab7576f26f64aa19317891
pytorchmergebot pushed a commit that referenced this issue Jan 30, 2022
@anjali411 @pytorchmergebot
Set correct device id on efficientzerotensors (#71611)
a18cfb7 
Summary:
Pull Request resolved: #71611

Fixes #71160 #69925

Test Plan: Imported from OSS

Reviewed By: george-qi

Differential Revision: D33834916

Pulled By: anjali411

fbshipit-source-id: 11cec343e95e2ee188ab7576f26f64aa19317891
(cherry picked from commit f6e86f8)
anjali411 added a commit that referenced this issue Feb 2, 2022
@anjali411
Update base for Update on "Set correct device id on efficientzerotens…
16f7967 
…ors"


Fixes #71160 #69925 #69913

Differential Revision: [D33897543](https://our.internmc.facebook.com/intern/diff/D33897543)

[ghstack-poisoned]
anjali411 added a commit that referenced this issue Feb 2, 2022
@anjali411
Update on "Set correct device id on efficientzerotensors"
dcc9164 
Fixes #71160 #69925 #69913

Differential Revision: [D33897543](https://our.internmc.facebook.com/intern/diff/D33897543)

[ghstack-poisoned]
anjali411 added a commit that referenced this issue Feb 2, 2022
@anjali411
Update base for Update on "Set correct device id on efficientzerotens…
a4dc624 
…ors"


Fixes #71160 #69925 #69913

Differential Revision: [D33897543](https://our.internmc.facebook.com/intern/diff/D33897543)

[ghstack-poisoned]
anjali411 added a commit that referenced this issue Feb 2, 2022
@anjali411
Update on "Set correct device id on efficientzerotensors"
970d238 
Fixes #71160 #69925 #69913

Differential Revision: [D33897543](https://our.internmc.facebook.com/intern/diff/D33897543)

[ghstack-poisoned]
anjali411 added a commit that referenced this issue Feb 2, 2022
@anjali411
Update base for Update on "Set correct device id on efficientzerotens…
5522c94 
…ors"


Fixes #71160 #69925 #69913

Differential Revision: [D33897543](https://our.internmc.facebook.com/intern/diff/D33897543)

[ghstack-poisoned]
anjali411 added a commit that referenced this issue Feb 2, 2022
@anjali411
Update on "Set correct device id on efficientzerotensors"
cf911cf 
Fixes #71160 #69925 #69913

Differential Revision: [D33897543](https://our.internmc.facebook.com/intern/diff/D33897543)

[ghstack-poisoned]
facebook-github-bot pushed a commit that referenced this issue Feb 2, 2022
@anjali411 @facebook-github-bot
Set correct device id on efficientzerotensors (#71611)
643e666 
Summary:
Pull Request resolved: #71611

Fixes #71160 #69925 #69913

Test Plan: Imported from OSS

Reviewed By: VitalyFedyunin

Differential Revision: D33897543

Pulled By: anjali411

fbshipit-source-id: f1d8608c351876b8c2619da5ef891f74bad30ab5
pytorchmergebot pushed a commit that referenced this issue Feb 2, 2022
@anjali411 @pytorchmergebot
Set correct device id on efficientzerotensors (#71611)
f607af1 
Summary:
Pull Request resolved: #71611

Fixes #71160 #69925 #69913

Test Plan: Imported from OSS

Reviewed By: VitalyFedyunin

Differential Revision: D33897543

Pulled By: anjali411

fbshipit-source-id: f1d8608c351876b8c2619da5ef891f74bad30ab5
(cherry picked from commit 643e666)
cyyever pushed a commit to cyyever/pytorch_private that referenced this issue Feb 3, 2022
@anjali411 @cyyever
Set correct device id on efficientzerotensors (#71611)
62f8091 
Summary:
Pull Request resolved: pytorch/pytorch#71611

Fixes pytorch/pytorch#71160

Test Plan: Imported from OSS

Reviewed By: pbelevich, ngimel

Differential Revision: D33768645

Pulled By: anjali411

fbshipit-source-id: 66ce9907630b65a12c0775077147a7e72ff4cee4
(cherry picked from commit 3af98a4)
cyyever pushed a commit to cyyever/pytorch_private that referenced this issue Feb 3, 2022
@anjali411 @cyyever
Set correct device id on efficientzerotensors (#71611)
78d9346 
Summary:
Pull Request resolved: pytorch/pytorch#71611

Fixes pytorch/pytorch#71160 pytorch/pytorch#69925

Test Plan: Imported from OSS

Reviewed By: george-qi

Differential Revision: D33834916

Pulled By: anjali411

fbshipit-source-id: 11cec343e95e2ee188ab7576f26f64aa19317891
(cherry picked from commit f6e86f8)
cyyever pushed a commit to cyyever/pytorch_private that referenced this issue Feb 3, 2022
@anjali411 @cyyever
Set correct device id on efficientzerotensors (#71611)
3078daf 
Summary:
Pull Request resolved: pytorch/pytorch#71611

Fixes pytorch/pytorch#71160 pytorch/pytorch#69925 #69913

Test Plan: Imported from OSS

Reviewed By: VitalyFedyunin

Differential Revision: D33897543

Pulled By: anjali411

fbshipit-source-id: f1d8608c351876b8c2619da5ef891f74bad30ab5
(cherry picked from commit 643e666)
cyyever pushed a commit to cyyever/pytorch_private that referenced this issue Feb 3, 2022
@anjali411 @cyyever
Set correct device id on efficientzerotensors (#71611)
d04067d 
Summary:
Pull Request resolved: pytorch/pytorch#71611

Fixes pytorch/pytorch#71160

Test Plan: Imported from OSS

Reviewed By: pbelevich, ngimel

Differential Revision: D33768645

Pulled By: anjali411

fbshipit-source-id: 66ce9907630b65a12c0775077147a7e72ff4cee4
(cherry picked from commit 3af98a4)
cyyever pushed a commit to cyyever/pytorch_private that referenced this issue Feb 3, 2022
@anjali411 @cyyever
Set correct device id on efficientzerotensors (#71611)
4160a7d 
Summary:
Pull Request resolved: pytorch/pytorch#71611

Fixes pytorch/pytorch#71160 pytorch/pytorch#69925

Test Plan: Imported from OSS

Reviewed By: george-qi

Differential Revision: D33834916

Pulled By: anjali411

fbshipit-source-id: 11cec343e95e2ee188ab7576f26f64aa19317891
(cherry picked from commit f6e86f8)
cyyever pushed a commit to cyyever/pytorch_private that referenced this issue Feb 3, 2022
@anjali411 @cyyever
Set correct device id on efficientzerotensors (#71611)
a16cf3d 
Summary:
Pull Request resolved: pytorch/pytorch#71611

Fixes pytorch/pytorch#71160 pytorch/pytorch#69925 #69913

Test Plan: Imported from OSS

Reviewed By: VitalyFedyunin

Differential Revision: D33897543

Pulled By: anjali411

fbshipit-source-id: f1d8608c351876b8c2619da5ef891f74bad30ab5
(cherry picked from commit 643e666)
cyyever pushed a commit to cyyever/pytorch_private that referenced this issue Feb 9, 2022
@anjali411 @cyyever
Set correct device id on efficientzerotensors (#71611)
99cb0b6 
Summary:
Pull Request resolved: pytorch/pytorch#71611

Fixes pytorch/pytorch#71160

Test Plan: Imported from OSS

Reviewed By: pbelevich, ngimel

Differential Revision: D33768645

Pulled By: anjali411

fbshipit-source-id: 66ce9907630b65a12c0775077147a7e72ff4cee4
(cherry picked from commit 3af98a4)
cyyever pushed a commit to cyyever/pytorch_private that referenced this issue Feb 9, 2022
@anjali411 @cyyever
Set correct device id on efficientzerotensors (#71611)
299b7cc 
Summary:
Pull Request resolved: pytorch/pytorch#71611

Fixes pytorch/pytorch#71160 pytorch/pytorch#69925

Test Plan: Imported from OSS

Reviewed By: george-qi

Differential Revision: D33834916

Pulled By: anjali411

fbshipit-source-id: 11cec343e95e2ee188ab7576f26f64aa19317891
(cherry picked from commit f6e86f8)
cyyever pushed a commit to cyyever/pytorch_private that referenced this issue Feb 9, 2022
@anjali411 @cyyever
Set correct device id on efficientzerotensors (#71611)
d48261c 
Summary:
Pull Request resolved: pytorch/pytorch#71611

Fixes pytorch/pytorch#71160 pytorch/pytorch#69925 #69913

Test Plan: Imported from OSS

Reviewed By: VitalyFedyunin

Differential Revision: D33897543

Pulled By: anjali411

fbshipit-source-id: f1d8608c351876b8c2619da5ef891f74bad30ab5
(cherry picked from commit 643e666)
cyyever pushed a commit to cyyever/pytorch_private that referenced this issue Feb 9, 2022
@anjali411 @cyyever
Set correct device id on efficientzerotensors (#71611)
11c6611 
Summary:
Pull Request resolved: pytorch/pytorch#71611

Fixes pytorch/pytorch#71160

Test Plan: Imported from OSS

Reviewed By: pbelevich, ngimel

Differential Revision: D33768645

Pulled By: anjali411

fbshipit-source-id: 66ce9907630b65a12c0775077147a7e72ff4cee4
(cherry picked from commit 3af98a4)
cyyever pushed a commit to cyyever/pytorch_private that referenced this issue Feb 9, 2022
@anjali411 @cyyever
Set correct device id on efficientzerotensors (#71611)
5e5a03e 
Summary:
Pull Request resolved: pytorch/pytorch#71611

Fixes pytorch/pytorch#71160 pytorch/pytorch#69925

Test Plan: Imported from OSS

Reviewed By: george-qi

Differential Revision: D33834916

Pulled By: anjali411

fbshipit-source-id: 11cec343e95e2ee188ab7576f26f64aa19317891
(cherry picked from commit f6e86f8)
cyyever pushed a commit to cyyever/pytorch_private that referenced this issue Feb 9, 2022
@anjali411 @cyyever
Set correct device id on efficientzerotensors (#71611)
5319382 
Summary:
Pull Request resolved: pytorch/pytorch#71611

Fixes pytorch/pytorch#71160 pytorch/pytorch#69925 #69913

Test Plan: Imported from OSS

Reviewed By: VitalyFedyunin

Differential Revision: D33897543

Pulled By: anjali411

fbshipit-source-id: f1d8608c351876b8c2619da5ef891f74bad30ab5
(cherry picked from commit 643e666)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module ZeroTensor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@anjali411
0