sg.ddlZdZdZdZGddZy)Nc6tjjS)z1Return whether PyTorch is built with MKL support.)torch_Chas_mklN/var/www/html/venv/lib/python3.12/site-packages/torch/backends/mkl/__init__.py is_availabler s 88  rc"eZdZdZdZdZdZy)verbosea? On-demand oneMKL verbosing functionality. To make it easier to debug performance issues, oneMKL can dump verbose messages containing execution information like duration while executing the kernel. The verbosing functionality can be invoked via an environment variable named `MKL_VERBOSE`. However, this methodology dumps messages in all steps. Those are a large amount of verbose messages. Moreover, for investigating the performance issues, generally taking verbose messages for one single iteration is enough. This on-demand verbosing functionality makes it possible to control scope for verbose message dumping. In the following example, verbose messages will be dumped out for the second inference only. .. highlight:: python .. code-block:: python import torch model(data) with torch.backends.mkl.verbose(torch.backends.mkl.VERBOSE_ON): model(data) Args: level: Verbose level - ``VERBOSE_OFF``: Disable verbosing - ``VERBOSE_ON``: Enable verbosing c||_y)N)enable)selfrs r __init__zverbose.__init__+s  rc|jtk(rytjjj |j}|sJd|S)NzSFailed to set MKL into verbose mode. Please consider to disable this verbose scope.)r VERBOSE_OFFrr_verbosemkl_set_verbose)rsts r __enter__zverbose.__enter__.sI ;;+ %  XX   . .t{{ ;  a ` a  rc^tjjjty)NF)rrrrr)rexc_typeexc_valexc_tbs r __exit__zverbose.__exit__7s ))+6rN)__name__ __module__ __qualname____doc__rrrrrr r r s8rr )rr r VERBOSE_ONr rrr r"s#    ++r