[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180412132003.GC145698@bhelgaas-glaptop.roam.corp.google.com>
Date: Thu, 12 Apr 2018 08:20:04 -0500
From: Bjorn Helgaas <helgaas@...nel.org>
To: Lorenzo Pieralisi <lorenzo.pieralisi@....com>
Cc: Sridhar Pitchai <Sridhar.Pitchai@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Dexuan Cui <decui@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
Jake Oshins <jakeo@...rosoft.com>,
KY Srinivasan <kys@...rosoft.com>,
"Michael Kelley (EOSG)" <Michael.H.Kelley@...rosoft.com>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v7] Revert "PCI: hv: Use device serial number as PCI
domain"
On Thu, Apr 12, 2018 at 10:17:42AM +0100, Lorenzo Pieralisi wrote:
> On Thu, Apr 12, 2018 at 02:44:42AM +0000, Sridhar Pitchai wrote:
> > When Linux runs as a guest VM in Hyper-V and Hyper-V adds the virtual PCI
> > bus to the guest, Hyper-V always provides unique PCI domain.
> >
> > commit 4a9b0933bdfc ("PCI: hv: Use device serial number as PCI domain")
> > overrode unique domain with the serial number of the first device added to
> > the virtual PCI bus.
> >
> > The reason for that patch was to have a consistent and short name for the
> > device, but Hyper-V doesn't provide unique serial numbers. Using non-unique
> > serial numbers as domain IDs leads to duplicate device addresses, which
> > causes PCI bus registration to fail.
> >
> > Revert commit 4a9b0933bdfc ("PCI: hv: Use device serial number as PCI
> > domain") so we can reliably support multiple devices being assigned to
> > a guest.
> >
> > Fixes: 4a9b0933bdfc ("PCI: hv: Use device serial number as PCI domain")
> > Signed-off-by: Sridhar Pitchai <sridhar.pitchai@...rosoft.com>
> > Cc: stable@...r.kernel.org
>
> I am still not happy with this patch.
>
> - You do not explain at all the dependency on commit 0c195567a8f6 and
> you should because that's fundamental, if that patch is not present
> this revert breaks the kernel as per previous discussions[1].
> - You are sending this patch to all stable kernels that contain the
> commit you are fixing - some that may not contain the commit above
> (that was merged in v4.14), you are breaking those kernels, if not
> explain me why please
If there's a dependency on 0c195567a8f6, I totally agree that
needs to be cleared up. I was assuming that turned out to be
irrelevant.
> [1] https://marc.info/?l=linux-pci&m=152158684221212&w=2
Powered by blists - more mailing lists