Hi Thomas,
Thomas Huth writes:
> Hi Nikunj,
>
> On Wed, 22 Apr 2015 16:27:20 +0530
> Nikunj A Dadhania wrote:
>
>> PCI Enumeration has been part of SLOF. Now with hotplug code addition
>> in Qemu, it makes more sense to have this code a one place, i.e. Qemu.
>
> s/Qemu/QEMU/ and s/code a one p
On Sat, 2015-04-25 at 17:31 +1000, Alexey Kardashevskiy wrote:
> We need BAR setup in 2 cases: when SLOF needs to boot from a PCI device
> (and SLOF can do BAR setup) and when we do PCI hotplug - and BARs are set
> by the guest, otherwise we hit races here (Michael Roth can tell more). So
> as f
On 04/25/2015 05:30 AM, Thomas Huth wrote:
Hi Nikunj,
On Wed, 22 Apr 2015 16:27:20 +0530
Nikunj A Dadhania wrote:
PCI Enumeration has been part of SLOF. Now with hotplug code addition
in Qemu, it makes more sense to have this code a one place, i.e. Qemu.
s/Qemu/QEMU/ and s/code a one pla
Hi Nikunj,
On Wed, 22 Apr 2015 16:27:20 +0530
Nikunj A Dadhania wrote:
> PCI Enumeration has been part of SLOF. Now with hotplug code addition
> in Qemu, it makes more sense to have this code a one place, i.e. Qemu.
s/Qemu/QEMU/ and s/code a one place/code in one place/ ?
> Adding routines t
PCI Enumeration has been part of SLOF. Now with hotplug code addition
in Qemu, it makes more sense to have this code a one place, i.e. Qemu.
Adding routines to walk through the device nodes created by Qemu. SLOF
will configure the device/bridges and program the BARs for
communicating with the devi
