All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Alexander Bezzubikov <zuban32s@gmail.com>,
	qemu-devel@nongnu.org, ehabkost@redhat.com, seabios@seabios.org,
	Kevin OConnor <kevin@koconnor.net>,
	Gerd Hoffmann <kraxel@redhat.com>,
	pbonzini@redhat.com, Igor Mammedov <imammedo@redhat.com>,
	rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v3 5/5] docs: update documentation considering PCIE-PCI bridge
Date: Wed, 2 Aug 2017 16:16:35 +0200	[thread overview]
Message-ID: <9e36b7d6-bff3-b046-6053-162fb75ca0a0@redhat.com> (raw)
In-Reply-To: <20170802164551-mutt-send-email-mst@kernel.org>

On 08/02/17 15:47, Michael S. Tsirkin wrote:
> On Wed, Aug 02, 2017 at 12:23:46AM +0200, Laszlo Ersek wrote:
>> On 08/01/17 23:39, Michael S. Tsirkin wrote:
>>> On Wed, Aug 02, 2017 at 12:33:12AM +0300, Alexander Bezzubikov wrote:
>>>> 2017-08-01 23:31 GMT+03:00 Laszlo Ersek <lersek@redhat.com>:
>>>>> (Whenever my comments conflict with Michael's or Marcel's, I defer to them.)
>>>>>
>>>>> On 07/29/17 01:37, Aleksandr Bezzubikov wrote:
>>>>>> Signed-off-by: Aleksandr Bezzubikov <zuban32s@gmail.com>
>>>>>> ---
>>>>>>  docs/pcie.txt            |  46 ++++++++++--------
>>>>>>  docs/pcie_pci_bridge.txt | 121 +++++++++++++++++++++++++++++++++++++++++++++++
>>>>>>  2 files changed, 147 insertions(+), 20 deletions(-)
>>>>>>  create mode 100644 docs/pcie_pci_bridge.txt
>>>>>>
>>>>>> diff --git a/docs/pcie.txt b/docs/pcie.txt
>>>>>> index 5bada24..338b50e 100644
>>>>>> --- a/docs/pcie.txt
>>>>>> +++ b/docs/pcie.txt
>>>>>> @@ -46,7 +46,7 @@ Place only the following kinds of devices directly on the Root Complex:
>>>>>>      (2) PCI Express Root Ports (ioh3420), for starting exclusively PCI Express
>>>>>>          hierarchies.
>>>>>>
>>>>>> -    (3) DMI-PCI Bridges (i82801b11-bridge), for starting legacy PCI
>>>>>> +    (3) PCIE-PCI Bridge (pcie-pci-bridge), for starting legacy PCI
>>>>>>          hierarchies.
>>>>>>
>>>>>>      (4) Extra Root Complexes (pxb-pcie), if multiple PCI Express Root Buses
>>>>>
>>>>> When reviewing previous patches modifying / adding this file, I
>>>>> requested that we spell out "PCI Express" every single time. I'd like to
>>>>> see the same in this patch, if possible.
>>>>
>>>> OK, I didn't know it.
>>>>
>>>>>
>>>>>> @@ -55,18 +55,18 @@ Place only the following kinds of devices directly on the Root Complex:
>>>>>>     pcie.0 bus
>>>>>>     ----------------------------------------------------------------------------
>>>>>>          |                |                    |                  |
>>>>>> -   -----------   ------------------   ------------------   --------------
>>>>>> -   | PCI Dev |   | PCIe Root Port |   | DMI-PCI Bridge |   |  pxb-pcie  |
>>>>>> -   -----------   ------------------   ------------------   --------------
>>>>>> +   -----------   ------------------   -------------------   --------------
>>>>>> +   | PCI Dev |   | PCIe Root Port |   | PCIE-PCI Bridge |   |  pxb-pcie  |
>>>>>> +   -----------   ------------------   -------------------   --------------
>>>>>>
>>>>>>  2.1.1 To plug a device into pcie.0 as a Root Complex Integrated Endpoint use:
>>>>>>            -device <dev>[,bus=pcie.0]
>>>>>>  2.1.2 To expose a new PCI Express Root Bus use:
>>>>>>            -device pxb-pcie,id=pcie.1,bus_nr=x[,numa_node=y][,addr=z]
>>>>>> -      Only PCI Express Root Ports and DMI-PCI bridges can be connected
>>>>>> +      Only PCI Express Root Ports, PCIE-PCI bridges and DMI-PCI bridges can be connected
>>>>>
>>>>> It would be nice if we could keep the flowing text wrapped to 80 chars.
>>>>>
>>>>> Also, here you add the "PCI Express-PCI" bridge to the list of allowed
>>>>> controllers (and you keep DMI-PCI as permitted), but above DMI was
>>>>> replaced. I think these should be made consistent -- we should make up
>>>>> our minds if we continue to recommend the DMI-PCI bridge or not. If not,
>>>>> then we should eradicate all traces of it. If we want to keep it at
>>>>> least for compatibility, then it should remain as fully documented as it
>>>>> is now.
>>>>
>>>> Now I'm beginning to think that we shouldn't keep the DMI-PCI bridge
>>>> even for compatibility and may want to use a new PCIE-PCI bridge
>>>> everywhere (of course, except some cases when users are
>>>> sure they need exactly DMI-PCI bridge for some reason)
>>>
>>> Can dmi-pci support shpc? why doesn't it? For compatibility?
>>
>> I don't know why, but the fact that it doesn't is the reason libvirt
>> settled on auto-creating a dmi-pci bridge and a pci-pci bridge under
>> that for Q35. The reasoning was (IIRC Laine's words correctly) that the
>> dmi-pci bridge cannot receive hotplugged devices, while the pci-pci
>> bridge cannot be connected to the root complex. So both were needed.
>>
>> Thanks
>> Laszlo
> 
> OK. Is it true that dmi-pci + pci-pci under it will allow hotplug
> on Q35 if we just flip the bit in _OSC?

Marcel, what say you?... :)

  reply	other threads:[~2017-08-02 14:16 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-28 23:37 [Qemu-devel] [PATCH v3 0/5] Generic PCIE-PCI Bridge Aleksandr Bezzubikov
2017-07-28 23:37 ` [Qemu-devel] [PATCH v3 1/5] hw/i386: allow SHPC for Q35 machine Aleksandr Bezzubikov
2017-07-31 11:03   ` Marcel Apfelbaum
2017-08-03 12:52   ` Michael S. Tsirkin
2017-08-03 12:55     ` Alexander Bezzubikov
2017-08-03 13:05     ` Marcel Apfelbaum
2017-07-28 23:37 ` [Qemu-devel] [PATCH v3 2/5] hw/pci: introduce pcie-pci-bridge device Aleksandr Bezzubikov
2017-07-31 11:23   ` Marcel Apfelbaum
2017-07-31 18:40     ` Alexander Bezzubikov
2017-08-01 15:32       ` Michael S. Tsirkin
2017-08-01 15:45         ` Marcel Apfelbaum
2017-08-01 15:51           ` Michael S. Tsirkin
2017-08-01 15:59             ` Marcel Apfelbaum
2017-07-28 23:37 ` [Qemu-devel] [PATCH v3 3/5] hw/pci: introduce bridge-only vendor-specific capability to provide some hints to firmware Aleksandr Bezzubikov
2017-07-31 11:29   ` Marcel Apfelbaum
2017-07-31 18:43     ` Alexander Bezzubikov
2017-07-28 23:37 ` [Qemu-devel] [PATCH v3 4/5] hw/pci: add QEMU-specific PCI capability to Generic PCI Express Root Port Aleksandr Bezzubikov
2017-07-31 11:43   ` Marcel Apfelbaum
2017-07-31 18:45     ` Alexander Bezzubikov
2017-07-28 23:37 ` [Qemu-devel] [PATCH v3 5/5] docs: update documentation considering PCIE-PCI bridge Aleksandr Bezzubikov
2017-07-31 11:56   ` Marcel Apfelbaum
2017-08-01 20:31   ` Laszlo Ersek
2017-08-01 21:33     ` Alexander Bezzubikov
2017-08-01 21:39       ` Michael S. Tsirkin
2017-08-01 22:23         ` Laszlo Ersek
2017-08-02 12:30           ` Marcel Apfelbaum
2017-08-02 13:47           ` Michael S. Tsirkin
2017-08-02 14:16             ` Laszlo Ersek [this message]
2017-08-02 14:21               ` Marcel Apfelbaum
2017-08-02 15:36                 ` Marcel Apfelbaum
2017-08-02 16:26                   ` Michael S. Tsirkin
2017-08-02 17:58                     ` Marcel Apfelbaum
2017-08-03  2:41                       ` Laine Stump
2017-08-03 10:29                         ` Marcel Apfelbaum
2017-08-03 13:58                           ` Laine Stump
2017-08-03 18:59                             ` Marcel Apfelbaum

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=9e36b7d6-bff3-b046-6053-162fb75ca0a0@redhat.com \
    --to=lersek@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=kevin@koconnor.net \
    --cc=kraxel@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=seabios@seabios.org \
    --cc=zuban32s@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.