dlpack interface with dpctl fails on CPU (in both ways)

[fcharras]

Describe the bug

• From dpctl to pytorch:

  import dpctl.tensor as dpt
  import intel_extension_for_pytorch
  import torch
  array_dpctl_cpu = dpt.reshape(dpt.arange(1000, device="cpu", dtype=dpt.float32), (4, 250))
  array_torch_cpu = torch.from_dlpack(array_dpctl_cpu)

  fails with:

  RuntimeError: Data pointer is not bound to the default context of the specific device.
  

• from pytorch to dpctl:

  import dpctl.tensor as dpt
  import intel_extension_for_pytorch
  import torch
  array_torch_cpu = torch.arange(1000, dtype=torch.float32, device="cpu").reshape(4, 250)
  array_dpctl_cpu = dpt.from_dlpack(array_torch_cpu)

  fails with

  BufferError: The DLPack tensor resides on unsupported device.
  

Should those conversions be possible ?

I cross-posted this issue with dpctl repository at IntelPython/dpctl#1240 .

Versions

Environment informations:

Collecting environment information...
PyTorch version: 1.13.0a0+git49444c3
PyTorch CXX11 ABI: Yes
IPEX version: 1.13.120+gitb243ae3
IPEX commit: b243ae39
Build type: Release

OS: Ubuntu 22.04.2 LTS (x86_64)
GCC version: (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Clang version: N/A
IGC version: 2023.1.0 (2023.1.0.20230320)
CMake version: version 3.26.3
Libc version: glibc-2.35

Python version: 3.10.10 | packaged by conda-forge | (main, Mar 24 2023, 20:08:06) [GCC 11.3.0] (64-bit runtime)
Python platform: Linux-6.3.2-arch1-1-x86_64-with-glibc2.35
Is XPU available: True
DPCPP runtime version: N/A
MKL version: N/A
GPU models and configuration: 
[0] _DeviceProperties(name='Intel(R) Iris(R) Xe Graphics [0x9a49]', platform_name='Intel(R) Level-Zero', dev_type='gpu, support_fp64=0, total_memory=12544MB, max_compute_units=96, gpu_eu_count=96)
Intel OpenCL ICD version: 22.43.24595.30
Level Zero version: 1.3.24595.30

CPU:
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Address sizes:                   39 bits physical, 48 bits virtual
Byte Order:                      Little Endian
CPU(s):                          8
On-line CPU(s) list:             0-7
Vendor ID:                       GenuineIntel
Model name:                      11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
CPU family:                      6
Model:                           140
Thread(s) per core:              2
Core(s) per socket:              4
Socket(s):                       1
Stepping:                        1
CPU max MHz:                     4700.0000
CPU min MHz:                     400.0000
BogoMIPS:                        5608.00
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l2 invpcid_single cdp_l2 ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves split_lock_detect dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid movdiri movdir64b fsrm avx512_vp2intersect md_clear ibt flush_l1d arch_capabilities
Virtualization:                  VT-x
L1d cache:                       192 KiB (4 instances)
L1i cache:                       128 KiB (4 instances)
L2 cache:                        5 MiB (4 instances)
L3 cache:                        12 MiB (1 instance)
NUMA node(s):                    1
NUMA node0 CPU(s):               0-7
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Mmio stale data:   Not affected
Vulnerability Retbleed:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Enhanced / Automatic IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected

Versions of relevant libraries:
[pip3] intel-extension-for-pytorch==1.13.120+gitb243ae3
[pip3] numpy==1.24.3
[pip3] torch==1.13.0a0+git49444c3
[pip3] torchvision==0.14.1a0+5e8e2f1
[conda] intel-extension-for-pytorch 1.13.120+gitb243ae3          pypi_0    pypi
[conda] mkl                       2023.1.0            intel_46342    intel
[conda] mkl-dpcpp                 2023.1.0            intel_46342    intel
[conda] numpy                     1.23.5          py310h53a5b5f_0    conda-forge
[conda] torch                     1.13.0a0+git49444c3          pypi_0    pypi
[conda] torchvision               0.14.1a0+5e8e2f1          pypi_0    pypi

[gujinghui]

Not sure this is workable on CPU.
But, the error message in first case is confused me.
Will take a look.

[guangyey]

Hi @fcharras, may I know what the below codes print?

import torch
import intel_extension_for_pytorch
torch.xpu.has_multi_context()

I assume it will print True.
If yes, the first case result is expected. Dlpack is not supported in multi-context mode. You can re-build IPEX from the source code with USE_MULTI_CONTEXT=OFF BUILD_WITH_XPU=ON python setup.py install
And I am not sure is it reasonable in the second case.

[fcharras]

has_multi_context actually prints False.

I build from source using the compile_bundle.sh a couple weeks ago.

My environment is a bit particular because I use binaries I compiled for Gen12LP and tgllp AOT.

I'll report the results on the Flex series once I've managed to overcome current issues with the compile_bundle script.

[guangyey]

Ok, in my opinion, the reason is the tensor created by dpctl is allocated by a different sycl context from the runtime's context in IPEX. I strongly recommend that create a tensor using torch API.

[fcharras]

It would have been practical for me to be able to keep the dpctl workflow I had already in place but I agree it's probably a marginal usecase at the time being. I'll be fine using exclusively the torch API. Feel free to close this issue.