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=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 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 67016C32754 for ; Tue, 6 Aug 2019 18:55:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 30465216B7 for ; Tue, 6 Aug 2019 18:55:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1565117735; bh=OFNe4cx5n7BU2ztYRPRilOpQxiFFszGkU5k0ee0lgwI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=FkIGE3BC08cZ4H5igCfBVEUgBgeVBc4RFs3n3S/pyO/Yf8nfZbmZSNMnDoJJWqpc7 HeX6LuOtgpXjsAonSlcTeo+7QfrEXk9QX6/BN/L5Oxad5F0N2SMRe/zcw0NXpWVbh1 1PInAAF0iRpQ1UL7P3ht6Pm49G9TQAjVCUY0YzEU= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726579AbfHFSze (ORCPT ); Tue, 6 Aug 2019 14:55:34 -0400 Received: from mail.kernel.org ([198.145.29.99]:44932 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725906AbfHFSzd (ORCPT ); Tue, 6 Aug 2019 14:55:33 -0400 Received: from localhost (unknown [69.71.4.100]) (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 2953C214C6; Tue, 6 Aug 2019 18:55:33 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1565117733; bh=OFNe4cx5n7BU2ztYRPRilOpQxiFFszGkU5k0ee0lgwI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ieZfYW/7dJMqNDvD9xxwr0JT47lTdC+yJlm6ytFcnzJjm/i/jrJA6K0168204MM/N ayRy1CbN1vbTA29bBkP8khNiy/BUjQ/OYqX7a3KKjUvT/21aBfG9Mva5qgqSJnKsp7 05tCt9lcWijPAmqgRpGSU+GWdvVbeIYpiANB0wBw= Date: Tue, 6 Aug 2019 13:55:31 -0500 From: Bjorn Helgaas To: Sasha Levin Cc: Haiyang Zhang , "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: <20190806185531.GS151852@google.com> References: <1564771954-9181-1-git-send-email-haiyangz@microsoft.com> <20190805183657.GD17747@sasha-vm> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190805183657.GD17747@sasha-vm> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 05, 2019 at 02:36:57PM -0400, Sasha Levin wrote: > On Fri, Aug 02, 2019 at 06:52:56PM +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 > > Acked-by: Sasha Levin > > Bjorn, will you take it through the PCI tree or do you want me to take > it through hyper-v? Lorenzo usually applies patches to drivers/pci/controller/*, so that would be my preference. Bjorn