Skip to content
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.

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

VITIS-10910 Separate Ryzen and Alveo devices in ReportHost List #7856

Merged
merged 3 commits into from
Dec 19, 2023

Conversation

dbenusov
Copy link
Contributor

Problem solved by the commit

The Ryzen and Alveo devices currently share the same list in the ReportHost output. This contains misleading information for Ryzen devices.

Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered

Remove misleading information display for RyzenAI devices.

How problem was solved, alternative solutions (if any) and why they were rejected

Separated the Ryzen and Alveo devices lists in the ReportHost output. If one of each device is present there will be two lists.

Risks (if any) associated the changes in the commit

None.

What has been tested and how, request additional testing if necessary

Ubuntu 22.04

Alveo

dbenusov@xsjdbenusov50:~$ xbutil examine
System Configuration
  OS Name              : Linux
  Release              : 6.5.0-rc1+
  Version              : #10 SMP PREEMPT_DYNAMIC Wed Aug 16 22:28:12 PDT 2023
  Machine              : x86_64
  CPU Cores            : 16
  Memory               : 63990 MB
  Distribution         : Ubuntu 22.04 LTS
  GLIBC                : 2.35
  Model                : Precision 5820 Tower

XRT
  Version              : 2.16.0
  Branch               : master
  Hash                 : 893580509d3f7b0f1fab5a0da6210c709529a740
  Hash Date            : 2023-09-14 11:23:31
  XOCL                 : 2.16.0, 893580509d3f7b0f1fab5a0da6210c709529a740
  XCLMGMT              : 2.16.0, 893580509d3f7b0f1fab5a0da6210c709529a740

Devices present
BDF             :  Shell                            Logic UUID                            Device ID       Device Ready*
-------------------------------------------------------------------------------------------------------------------------
[0000:04:00.1]  :  xilinx_u55c_gen3x16_xdma_base_3  97088961-FEAE-DA91-52A2-1D9DFD63CCEF  user(inst=129)  Yes


* Devices that are not ready will have reduced functionality when using XRT tools

Ryzen (simulated Ryzen device)

dbenusov@xsjdbenusov50:/proj/rdi/staff/dbenusov$ xbutil examine
WARNING: Unexpected xocl version (2.16.0) was found. Expected 2.17.0, to match XRT tools.
System Configuration
  OS Name              : Linux
  Release              : 6.5.0-rc1+
  Version              : #10 SMP PREEMPT_DYNAMIC Wed Aug 16 22:28:12 PDT 2023
  Machine              : x86_64
  CPU Cores            : 16
  Memory               : 63990 MB
  Distribution         : Ubuntu 22.04 LTS
  GLIBC                : 2.35
  Model                : Precision 5820 Tower
  BIOS vendor          : Dell Inc.
  BIOS version         : 2.0.2

XRT
  Version              : 2.17.0
  Branch               : VITIS-10910
  Hash                 : 862cfaded934ef254fbe91e480c991345177eca5
  Hash Date            : 2023-12-11 16:56:50
  XOCL                 : 2.16.0, 893580509d3f7b0f1fab5a0da6210c709529a740
  XCLMGMT              : 2.16.0, 893580509d3f7b0f1fab5a0da6210c709529a740

Devices present
BDF             :  Name                             Device ID       Device Ready*
-----------------------------------------------------------------------------------
[0000:04:00.1]  :  xilinx_u55c_gen3x16_xdma_base_3  user(inst=129)  Yes


* Devices that are not ready will have reduced functionality when using XRT tools

Documentation impact (if any)

None

@gbuildx
Copy link
Collaborator

gbuildx commented Dec 19, 2023

Build Passed!

@dbenusov dbenusov requested a review from stsoe December 19, 2023 17:41
@stsoe stsoe merged commit eaf8282 into Xilinx:master Dec 19, 2023
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants