Hi,
> Maybe we don't want to allocate IO at all,
> So value 0 would say do not allocate.
>
> But we can disable IO by other means.
Indeed. As IO is optional for pcie we don't need a qemu-specific
extension for that.
cheers,
Gerd
On Fri, 2017-07-21 at 13:28 -0400, Kevin O'Connor wrote:
> On Fri, Jul 21, 2017 at 03:15:46PM +0300, Marcel Apfelbaum wrote:
> > On 21/07/2017 13:04, Gerd Hoffmann wrote:
> > > I'd prefer to have a single vendor capability for all resource
> > > allocation hints provided by qemu.
> >
> > Sure,
On 21/07/2017 20:28, Kevin O'Connor wrote:
On Fri, Jul 21, 2017 at 03:15:46PM +0300, Marcel Apfelbaum wrote:
On 21/07/2017 13:04, Gerd Hoffmann wrote:
I'd prefer to have a single vendor capability for all resource
allocation hints provided by qemu.
Sure, the capability looking something like:
On Fri, Jul 21, 2017 at 03:15:46PM +0300, Marcel Apfelbaum wrote:
> On 21/07/2017 13:04, Gerd Hoffmann wrote:
> > I'd prefer to have a single vendor capability for all resource
> > allocation hints provided by qemu.
> Sure, the capability looking something like:
>
>[flags:
On 21/07/2017 15:42, Gerd Hoffmann wrote:
On Fri, 2017-07-21 at 15:15 +0300, Marcel Apfelbaum wrote:
On 21/07/2017 13:04, Gerd Hoffmann wrote:
Hi,
What about window sizes? IIRC there was a plan to provide
allocation
hints for them too ...
Yes, is in my TODO list, however not as part
On Fri, 2017-07-21 at 15:15 +0300, Marcel Apfelbaum wrote:
> On 21/07/2017 13:04, Gerd Hoffmann wrote:
> > Hi,
> >
> > > > What about window sizes? IIRC there was a plan to provide
> > > > allocation
> > > > hints for them too ...
> > >
> > > Yes, is in my TODO list, however not as part of
On 21/07/2017 13:04, Gerd Hoffmann wrote:
Hi,
What about window sizes? IIRC there was a plan to provide
allocation
hints for them too ...
Yes, is in my TODO list, however not as part of Aleksandr's series
which aims to provide PCIe-PCI bridge hotplug support.
I'd prefer to have a
Hi,
> > What about window sizes? IIRC there was a plan to provide
> > allocation
> > hints for them too ...
>
> Yes, is in my TODO list, however not as part of Aleksandr's series
> which aims to provide PCIe-PCI bridge hotplug support.
I'd prefer to have a single vendor capability for all
On 20/07/2017 9:52, Gerd Hoffmann wrote:
On Wed, 2017-07-19 at 16:20 +0300, Aleksandr Bezzubikov wrote:
Now PCI bridges (and PCIE root port too) get a bus range number in
system init,
basing on currently plugged devices. That's why when one wants to
hotplug another bridge,
it needs his child
On Wed, 2017-07-19 at 16:20 +0300, Aleksandr Bezzubikov wrote:
> Now PCI bridges (and PCIE root port too) get a bus range number in
> 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
10 matches
Mail list logo
