Skip to content

Conversation

@VishalX
Copy link
Contributor

@VishalX VishalX commented Jul 18, 2025

Short term solution for IO binding issue with update_inplace method of OrtValue.

Description

With ORT 1.23 (main), there seem to be an issue with IOBind feature with 4k aligned preferred allocator.
Remove the 4k alignment requirement for now for a temp fix.

Motivation and Context

  • Fixes issues with IO Binding for few critical models.
  • Will bring back 4k alignment when we have a appropriate fix in.

@snnn
Copy link
Contributor

snnn commented Jul 18, 2025

/azp run Linux QNN CI Pipeline, Win_TRT_Minimal_CUDA_Test_CI, Windows ARM64 QNN CI Pipeline, Windows x64 QNN CI Pipeline, Windows GPU Doc Gen CI Pipeline

@azure-pipelines
Copy link

Azure Pipelines successfully started running 5 pipeline(s).

@HectorSVC HectorSVC requested review from Copilot and yuslepukhin July 18, 2025 15:37
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR removes 4K memory alignment requirements from the VitisAI execution provider as a temporary fix for IO binding issues with the update_inplace method of OrtValue in ORT 1.23.

  • Removes kAlloc4KAlignment parameter from OrtDevice constructor in the execution provider initialization
  • Removes kAlloc4KAlignment parameter from OrtDevice constructor in the preferred allocators creation method

@HectorSVC HectorSVC added the ep:VitisAI issues related to Vitis AI execution provider label Jul 18, 2025
@HectorSVC
Copy link
Contributor

/azp run Linux QNN CI Pipeline, Win_TRT_Minimal_CUDA_Test_CI, Windows ARM64 QNN CI Pipeline, Windows x64 QNN CI Pipeline, Windows GPU Doc Gen CI Pipeline

@azure-pipelines
Copy link

Azure Pipelines successfully started running 5 pipeline(s).

@VishalX VishalX force-pushed the vitisai/alloc-4kalign-fix-iobind branch 2 times, most recently from 6de0401 to d8ad2b6 Compare July 21, 2025 16:46
@VishalX VishalX requested review from HectorSVC and yuslepukhin July 21, 2025 16:53
Copy link
Member

@yuslepukhin yuslepukhin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@HectorSVC
Copy link
Contributor

/azp run Linux QNN CI Pipeline, Win_TRT_Minimal_CUDA_Test_CI, Windows ARM64 QNN CI Pipeline, Windows x64 QNN CI Pipeline, Windows GPU Doc Gen CI Pipeline

@azure-pipelines
Copy link

Azure Pipelines successfully started running 5 pipeline(s).

@HectorSVC HectorSVC merged commit 46c3b2c into microsoft:main Jul 21, 2025
86 of 93 checks passed
@VishalX VishalX deleted the vitisai/alloc-4kalign-fix-iobind branch July 22, 2025 04:43
qti-yuduo pushed a commit to CodeLinaro/onnxruntime that referenced this pull request Aug 8, 2025
Short term solution for IO binding issue with `update_inplace` method of `OrtValue`.

### Description
With ORT 1.23 (main), there seem to be an issue with IOBind feature with 4k aligned preferred allocator.
Remove the 4k alignment requirement for now for a temp fix.

### Motivation and Context
- Fixes issues with IO Binding for few critical models.
- Will bring back 4k alignment when we have a appropriate fix in.
sanketkaleoss pushed a commit to sanketkaleoss/onnxruntime that referenced this pull request Aug 11, 2025
Short term solution for IO binding issue with `update_inplace` method of `OrtValue`.

### Description
With ORT 1.23 (main), there seem to be an issue with IOBind feature with 4k aligned preferred allocator.
Remove the 4k alignment requirement for now for a temp fix.

### Motivation and Context
- Fixes issues with IO Binding for few critical models.
- Will bring back 4k alignment when we have a appropriate fix in.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ep:VitisAI issues related to Vitis AI execution provider

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants