mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sridhar Pitchai <Sridhar.Pitchai@microsoft.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Haiyang Zhang <haiyangz@microsoft.com>,
	Stephen Hemminger <sthemmin@microsoft.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Michael Kelley \(EOSG\)" <Michael.H.Kelley@microsoft.com>,
	Jake Oshins <jakeo@microsoft.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>
Subject: Re: [PATCH v5] PCI: hv: Make sure the bus domain is really unique
Date: Fri, 30 Mar 2018 19:35:04 +0000	[thread overview]
Message-ID: <105A3FAC-23AF-40F9-8B83-F00DED14EC43@microsoft.com> (raw)
In-Reply-To: <4BF97B43-5339-4750-9704-23D6AAC4A01E@microsoft.com>

  >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 is to have a consistent
  >and short name for the device. But commit 4a9b0933bdfc ("PCI: hv: Use
  >device serial number as PCI domain") will not guarantee unique domain id.
  >For example, if the serial number of the device is 0 and there exists a
  >PCI bus with domain 0 already, this will cause the PCI bus registration
  >with kernel fails.
  >
  >commit 4a9b0933bdfc ("PCI: hv: Use device serial number as PCI
  >domain") need to be reverted. Also, we no longer need it as commit
  >4a1626dd233e ("netvsc: transparent VF management") remove the
  >need for it.
  >
  >Revert commit 4a9b0933bdfc ("PCI: hv: Use device serial number as PCI
  >domain") so we can reliably support multiple devices being assigned to
  >a guest.
  >
  >This revert should only be backported to kernels that contain commit
  >4a1626dd233e ("netvsc: transparent VF management").
  >
  >Fixes: 4a9b0933bdfc ("PCI: hv: Use device serial number as PCI domain")
  >Signed-off-by: Sridhar Pitchai <sridhar.pitchai@microsoft.com>
  >Cc: stable@vger.kernel.org
  >
  >---
  >Changes in v5:
  >* fix the commit comment. [Lorenzo Pieralisi, Bjorn Helgaas]
  >* fixed the patch white space.
  >---
  > drivers/pci/host/pci-hyperv.c | 11 -----------
  > 1 file changed, 11 deletions(-)
  >
  >diff --git a/drivers/pci/host/pci-hyperv.c b/drivers/pci/host/pci-hyperv.c
  >index 2faf38eab785..ac67e56e451a 100644
  >--- a/drivers/pci/host/pci-hyperv.c
  >+++ b/drivers/pci/host/pci-hyperv.c
  >@@ -1518,17 +1518,6 @@ static struct hv_pci_dev *new_pcichild_device(struct hv_pcibus_device *hbus,
  > 	get_pcichild(hpdev, hv_pcidev_ref_childlist);
  > 	spin_lock_irqsave(&hbus->device_list_lock, flags);
  > 
  >-	/*
  >-	 * When a device is being added to the bus, we set the PCI domain
  >-	 * number to be the device serial number, which is non-zero and
  >-	 * unique on the same VM.  The serial numbers start with 1, and
  >-	 * increase by 1 for each device.  So device names including this
  >-	 * can have shorter names than based on the bus instance UUID.
  >-	 * Only the first device serial number is used for domain, so the
  >-	 * domain number will not change after the first device is added.
  >-	 */
  >-	if (list_empty(&hbus->children))
  >-		hbus->sysdata.domain = desc->ser;
  > 	list_add_tail(&hpdev->list_entry, &hbus->children);
  > 	spin_unlock_irqrestore(&hbus->device_list_lock, flags);
  > 	return hpdev;
  >-- 
>2.14.1

Hi Lorenzo,
Did you get a chance to look at the patch v5. Please let me know if
anything I need to address further.

Thanks
Sridhar 

_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  reply	other threads:[~2018-03-30 19:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 17:34 Sridhar Pitchai
2018-03-30 19:35 ` Sridhar Pitchai [this message]
2018-03-30 21:23   ` Bjorn Helgaas
2018-03-31  0:49     ` Sridhar Pitchai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=105A3FAC-23AF-40F9-8B83-F00DED14EC43@microsoft.com \
    --to=sridhar.pitchai@microsoft.com \
    --cc=Michael.H.Kelley@microsoft.com \
    --cc=bhelgaas@google.com \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=jakeo@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=sthemmin@microsoft.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®