From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS, T_DKIMWL_WL_HIGH,USER_AGENT_MUTT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 65897C282E1 for ; Fri, 24 May 2019 22:15:23 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3BF0D2184E for ; Fri, 24 May 2019 22:15:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1558736123; bh=S/mRMEkQXFi04Mis9f/sXsoi0IV12RHQlkHVTfheS9c=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=eI8OjQpDf70ZL3hzhnG53DCDywaPyRfT+xs6pWRidq531RLQud/Cx5WOZTbWt+r09 vutpLGxX6ICpj7UbtuM/0hG3e8fgrVpgi4OsgHlNwkK17JgndZcWkh/exF4SjyKiR3 jieUc8fvaRlhTJiN14X8b0XuFcZ4W2SkDcWv/e0o= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404258AbfEXWPS (ORCPT ); Fri, 24 May 2019 18:15:18 -0400 Received: from mail.kernel.org ([198.145.29.99]:53174 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2404176AbfEXWPS (ORCPT ); Fri, 24 May 2019 18:15:18 -0400 Received: from localhost (c-73-47-72-35.hsd1.nh.comcast.net [73.47.72.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A553A20862; Fri, 24 May 2019 22:15:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1558736117; bh=S/mRMEkQXFi04Mis9f/sXsoi0IV12RHQlkHVTfheS9c=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=PkwFpQ4hGAB9aobq0V2zldqyZ6DaPyuZZudvGY7ehHuT9rlCafnqPXBcnOZ9HFcZM QBala4Ythw8IFP0+5XprdpisSJbO7wHKXMThlksnAIoJatpAQCTcRmtMxCUMuBvVs6 QFQ8jubF0K02LFtkLXb3DwOEL0cpw4oJa0wmt+EY= Date: Fri, 24 May 2019 18:15:16 -0400 From: Sasha Levin To: Haiyang Zhang Cc: "bhelgaas@google.com" , "lorenzo.pieralisi@arm.com" , "linux-hyperv@vger.kernel.org" , "linux-pci@vger.kernel.org" , KY Srinivasan , Stephen Hemminger , "olaf@aepfle.de" , vkuznets , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number collision Message-ID: <20190524221516.GD12898@sasha-vm> References: <1558304821-36038-1-git-send-email-haiyangz@microsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <1558304821-36038-1-git-send-email-haiyangz@microsoft.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-hyperv-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-hyperv@vger.kernel.org On Sun, May 19, 2019 at 10:28:37PM +0000, Haiyang Zhang wrote: >Due to Azure host agent settings, the device instance ID's bytes 8 and 9 >are no longer unique. This causes some of the PCI devices not showing up >in VMs with multiple passthrough devices, such as GPUs. So, as recommended >by Azure host team, we now use the bytes 4 and 5 which usually provide >unique numbers. > >In the rare cases of collision, we will detect and find another number >that is not in use. >Thanks to Michael Kelley for proposing this idea. > >Signed-off-by: Haiyang Zhang Queued up for hyperv-fixes, thank you. -- Thanks, Sasha