linux-kernel - Re: [PATCH v5 5/7] vfio/nvgrace-gpu: split the code to wait for GPU ready

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID:
 <SA1PR12MB71998B6D31AEC03DF7A8E6F6B0D1A@SA1PR12MB7199.namprd12.prod.outlook.com>
Date: Tue, 25 Nov 2025 02:53:11 +0000
From: Ankit Agrawal <ankita@...dia.com>
To: Shameer Kolothum <skolothumtho@...dia.com>, "jgg@...pe.ca" <jgg@...pe.ca>,
	Yishai Hadas <yishaih@...dia.com>, "kevin.tian@...el.com"
	<kevin.tian@...el.com>, "alex@...zbot.org" <alex@...zbot.org>, Aniket Agashe
	<aniketa@...dia.com>, Vikram Sethi <vsethi@...dia.com>, Matt Ochs
	<mochs@...dia.com>
CC: "Yunxiang.Li@....com" <Yunxiang.Li@....com>, "yi.l.liu@...el.com"
	<yi.l.liu@...el.com>, "zhangdongdong@...incomputing.com"
	<zhangdongdong@...incomputing.com>, Avihai Horon <avihaih@...dia.com>,
	"bhelgaas@...gle.com" <bhelgaas@...gle.com>, "peterx@...hat.com"
	<peterx@...hat.com>, "pstanner@...hat.com" <pstanner@...hat.com>, Alistair
 Popple <apopple@...dia.com>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Neo Jia
	<cjia@...dia.com>, Kirti Wankhede <kwankhede@...dia.com>, "Tarun Gupta
 (SW-GPU)" <targupta@...dia.com>, Zhi Wang <zhiw@...dia.com>, Dan Williams
	<danw@...dia.com>, Dheeraj Nigam <dnigam@...dia.com>, Krishnakant Jaju
	<kjaju@...dia.com>
Subject: Re: [PATCH v5 5/7] vfio/nvgrace-gpu: split the code to wait for GPU
 ready

Thanks Shameer for the reviewed-by.

>> +     do {
>> +             if ((ioread32(io + C2C_LINK_BAR0_OFFSET) ==
>> STATUS_READY) &&
>> +                 (ioread32(io + HBM_TRAINING_BAR0_OFFSET) ==
>> STATUS_READY)) {
>> +                     ret = 0;
>> +                     goto ready_check_exit;
>
> You could return directly here and avoid that goto.

Yeah, I have a bad habit of overusing goto. I'll update it to return.