From: Greg KH <greg@kroah.com>
To: Sadanand Warrier <sadanandwarrier@gmail.com>
Cc: Kernelnewbies@kernelnewbies.org
Subject: Re: PCIe hotplug
Date: Thu, 13 Feb 2020 09:48:46 -0800 [thread overview]
Message-ID: <20200213174846.GA3688355@kroah.com> (raw)
In-Reply-To: <CADJuq2yaNG_FFr8F1msq3VnC2CnLq=Sye8FBf8CXpJhrDYgCnQ@mail.gmail.com>
On Thu, Feb 13, 2020 at 12:40:59PM -0500, Sadanand Warrier wrote:
> Hi
> I had question about PCIe hotplug. We have hardware that is connected
> to the host by means of two PCIe switches. i.e. the host sees a PCIe switch
> connected to one of its buses and on the far side of that switch another
> PCIe switch which has a PCIe device.
> It is possible that this device does not train its host facing PCIe
> links before the server enumerates down its PCI bus and reaches those
> links. It is also possible the PCIe switch to which the device is attached
> has not been able to train its own links before server enumeration.
> Is PCIe hotplug built to work on schemes like this? Let us assume that
> the hardware has been designed to trasmit a presence signal once the links
> are trained but this could happen after the server enumeration?
Look at the PCIe hotplug spec, it should answer all of your questions
about this.
> Incidentally does the server take advantage of the BIOS/UEFI enumeration?
Yes, of course, how else would the kernel be able to enumerate PCI
devices? :)
thanks,
greg k-h
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-02-13 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 17:40 PCIe hotplug Sadanand Warrier
2020-02-13 17:48 ` Greg KH [this message]
2020-02-13 19:50 ` Sadanand Warrier
-- strict thread matches above, loose matches on Subject: below --
2017-03-29 13:34 Ludwig Petrosyan
2017-03-29 20:20 ` Bjorn Helgaas
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=20200213174846.GA3688355@kroah.com \
--to=greg@kroah.com \
--cc=Kernelnewbies@kernelnewbies.org \
--cc=sadanandwarrier@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.