On 26/07/2017 21:49, Michael S. Tsirkin wrote:
On Wed, Jul 26, 2017 at 07:22:42PM +0300, Marcel Apfelbaum wrote:
On 26/07/2017 18:20, Laszlo Ersek wrote:
On 07/26/17 08:48, Marcel Apfelbaum wrote:
On 25/07/2017 18:46, Laszlo Ersek wrote:
[snip]
(2) Bus range reservation, and hotplugging
On 26/07/2017 21:31, Laszlo Ersek wrote:
On 07/26/17 18:22, Marcel Apfelbaum wrote:
On 26/07/2017 18:20, Laszlo Ersek wrote:
[snip]
However, what does the hot-pluggability of the PCIe-PCI bridge buy us?
In other words, what does it buy us when we do not add the PCIe-PCI
bridge immediately
On Wed, Jul 26, 2017 at 07:22:42PM +0300, Marcel Apfelbaum wrote:
> On 26/07/2017 18:20, Laszlo Ersek wrote:
> > On 07/26/17 08:48, Marcel Apfelbaum wrote:
> > > On 25/07/2017 18:46, Laszlo Ersek wrote:
> >
> > [snip]
> >
> > > > (2) Bus range reservation, and hotplugging bridges. What's the
> >
On 07/26/17 18:22, Marcel Apfelbaum wrote:
> On 26/07/2017 18:20, Laszlo Ersek wrote:
[snip]
>> However, what does the hot-pluggability of the PCIe-PCI bridge buy us?
>> In other words, what does it buy us when we do not add the PCIe-PCI
>> bridge immediately at guest startup, as an integrated
On 26/07/2017 18:20, Laszlo Ersek wrote:
On 07/26/17 08:48, Marcel Apfelbaum wrote:
On 25/07/2017 18:46, Laszlo Ersek wrote:
[snip]
(2) Bus range reservation, and hotplugging bridges. What's the
motivation? Our recommendations in "docs/pcie.txt" suggest flat
hierarchies.
It remains flat.
On 07/26/17 08:48, Marcel Apfelbaum wrote:
> On 25/07/2017 18:46, Laszlo Ersek wrote:
[snip]
>> (2) Bus range reservation, and hotplugging bridges. What's the
>> motivation? Our recommendations in "docs/pcie.txt" suggest flat
>> hierarchies.
>>
>
> It remains flat. You have one single PCIE-PCI
On 25/07/2017 18:46, Laszlo Ersek wrote:
On 07/23/17 00:11, Aleksandr Bezzubikov wrote:
Now PCI bridges get a bus range number on a system init, basing on
currently plugged devices. That's why when one wants to hotplug
another bridge, it needs his child bus, which the parent is unable to
On 07/23/17 00:11, Aleksandr Bezzubikov wrote:
> Now PCI bridges get a bus range number on a system init, basing on
> currently plugged devices. That's why when one wants to hotplug
> another bridge, it needs his child bus, which the parent is unable to
> provide (speaking about virtual device).
Now PCI bridges get a bus range number on a system init,
basing on currently plugged devices. That's why when one wants to hotplug
another bridge,
it needs his child bus, which the parent is unable to provide (speaking about
virtual device).
The suggested workaround is to have vendor-specific
