[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2 0/3] hw/pci: PCI resource reserve capability

From: Liu, Jing2
Subject: Re: [Qemu-devel] [PATCH v2 0/3] hw/pci: PCI resource reserve capability
Date: Fri, 17 Aug 2018 11:39:47 +0800
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1

Hi Laszlo,
Thanks very much for your reminder.
Looking forward to comments from all!


On 8/17/2018 12:17 AM, Laszlo Ersek wrote:

On 08/16/18 11:28, Jing Liu wrote:
This patch serial is about PCI resource reserve capability.

First patch refactors the resource reserve fields in GenPCIERoorPort
structure out to another new structure, called "PCIResReserve". Modify
the parameter list of pci_bridge_qemu_reserve_cap_init().

Then we add the teardown function called pci_bridge_qemu_reserve_cap_uninit().

Last we enable the resource reserve capability for legacy PCI bridge
so that firmware can reserve additional resources for the bridge.

Change Log:
v2 -> v1
* add refactoring patch
* add teardown function
* some other fixes

Jing Liu (3):
   hw/pci: factor PCI reserve resources to a separate structure
   hw/pci: add teardown function for PCI resource reserve capability
   hw/pci: add PCI resource reserve capability to legacy PCI bridge

  hw/pci-bridge/gen_pcie_root_port.c | 32 +++++++++++++-------------
  hw/pci-bridge/pci_bridge_dev.c     | 25 ++++++++++++++++++++
  hw/pci/pci_bridge.c                | 47 +++++++++++++++++++++-----------------
  include/hw/pci/pci_bridge.h        | 18 +++++++++++----
  4 files changed, 80 insertions(+), 42 deletions(-)

just some meta comments for now:

- I've added Marcel; please keep him CC'd on this set (and the SeaBIOS
counterpart, [SeaBIOS] [PATCH v2 0/3] pci: resource reserve capability

- my task queue has blown up and I'm unsure when I'll get to reviewing
this set. The same applies to the SeaBIOS counterpart.

This is just to say that you should feel free to go ahead and work with
the (sub)maintainers; I'll try to get back to this as time allows, but
don't wait for me.

If further versions are necessary, I'd appreciate being CC'd on those,
just so I know what to look at when I find the time again.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]