o :/i&@sVddlmZddlZddlZddlZddlZddlZddlmZm Z ddl m Z ddl m Z ddlZddlmZddlmZddlmZddlmZdd lmZd d lmZmZeeZd Zd ZdAddZ ej!dBddZ"ej!ddZ#dCddZ$d d!Z%d"d#Z&d$d%Z'd&ej(fdDd+d,Z)dEd2d3Z*dFdGd6d7Z+dHd8d9Z,dIdJdSync HIP/CUDA visibility env vars before spawning (ROCm only).Nr_sync_hip_cuda_env_vars)ris_rocmvllm.platforms.rocmr;r:rrr_sync_visible_devices_env_varsss  r>cCstjddkr dSg}tr ddl}|jtjd<|dtr)|dnt r1|dt r9|d |rKt d d |dtjd<dSdS) zWCheck if we need to force the use of the `spawn` multiprocessing start method. VLLM_WORKER_MULTIPROC_METHODspawnNr RAY_ADDRESSz&In a Ray actor and can only be spawnedzCUDA is initializedzXPU is initializedz4WSL is detected and NVML is not compatible with forkzWe must use the `spawn` multiprocessing start method. Overriding VLLM_WORKER_MULTIPROC_METHOD to 'spawn'. See https://docs.vllm.ai/en/latest/usage/troubleshooting.html#python-multiprocessing for more information. Reasons: %sz; )rrrr rayget_runtime_context gcs_addressappendr r r rrjoin)reasonsrBrrr_maybe_force_spawn~s(    rHcCstttj}t|S)aJGet a multiprocessing context with a particular method (spawn or fork). By default we follow the value of the VLLM_WORKER_MULTIPROC_METHOD to determine the multiprocessing method (default is fork). However, under certain conditions, we may enforce spawn and override the value of VLLM_WORKER_MULTIPROC_METHOD. )rHr>r$r?multiprocessing get_context) mp_methodrrrget_mp_contexts rLnamesuffixprefixNonecCsLzddl}Wn tyYdSw|r|d|}||d|dS)z3Set the current process title with optional suffix.rN_z::) setproctitle ImportError)rNrOrPrSrrrset_process_titles  rUfiler worker_namepidintcstdo}tjstjdkstjdkr"|s"d|d|dntd|d|dtdtd jdfd d }d_ _ |_dS)z5Add colored prefix to file output for log decoration.isatty01(z pid=z) ) _original_writesrcs|sdSjr d}|d|}dkr>|d7}||||t|kr.d_dS|}|d|}dks||dd_dS)Nr r TF)start_new_linefindlen)raidxnext_idxrV file_writerPrrwrite_with_prefixs   z&_add_prefix..write_with_prefixTN)rar) hasattrrZr$NO_COLORVLLM_LOGGING_COLORCYANRESETgetattrwriterdr`)rVrWrXis_ttyrkrrir _add_prefixs  rt process_name str | NonecCsFtjsdS|durtj}t}ttj ||ttj ||dS)z8Decorate stdout/stderr with process name and PID prefix.N) r$VLLM_CONFIGURE_LOGGINGrLcurrent_processrNrgetpidrtr&r'stderr)rurXrrr decorate_logss r{c Cszt|}Wn tjyYdSw|jdd}|D]}ttt|j t j Wdn1s5wYqttt|t j WddS1sSwYdS)z Kills all descendant processes of the given pid by sending SIGKILL. Args: pid (int): Process ID of the parent process NT) recursive) psutilProcess NoSuchProcesschildren contextlibsuppressProcessLookupErrorrkillrXsignalSIGKILL)rXparentrchildrrrkill_process_trees   "rtarget_soft_limitc Cstjdr tddSddl}|j}||\}}||krEz ||||fWdSt yD}zt d||WYd}~dSd}~wwdS)Nwinz-Windows detected, skipping ulimit adjustment.rzFound ulimit of %s and failed to automatically increase with error %s. This can cause fd limit errors like `OSError: [Errno 24] Too many open files`. Consider increasing with ulimit -n) r&platform startswithrinforesource RLIMIT_NOFILE getrlimit setrlimit ValueErrorr)rr resource_type current_soft current_harderrr set_ulimits$  rlib_namecCsd}td}|D] }||vr|}nq Wdn1swY|dur)dS|d}||d}|dd}|dd|sQJd|d||S) a' According to according to https://man7.org/linux/man-pages/man5/proc_pid_maps.5.html, the file `/proc/self/maps` contains the memory maps of the process, which includes the shared libraries loaded by the process. We can use this file to find the path of the loaded library. Nz/proc/self/maps/rcz.sorzUnexpected filename: z for library )r*indexstripsplit rpartitionr)r found_lineflinestartpathfilenamerrrfind_loaded_library+s$  r)rr)rrrrrr)r4r5rr)rNrrOrrPrrrQ)rVrrWrrXrYrrQ)N)rurvrrQ)rXrY)r)rrY)rrrrv)/ __future__rrrIrrr&collections.abcrrpathlibrtypingrr} vllm.envsr$ vllm.loggerrvllm.platformsrvllm.platforms.interfacer vllm.ray.lazy_utilsr platform_utilsr r __name__rrorprcontextmanagerr"r3r9r>rHrLVLLM_PROCESS_NAME_PREFIXrUrtr{rrrrrrrsH            # %  $