Re: [PATCH] xen/pci: try to reserve MCFG areas earlier

2019-09-09 Thread Igor Druzhinin
On 09/09/2019 20:19, Boris Ostrovsky wrote: > On 9/8/19 7:37 PM, Igor Druzhinin wrote: >> On 09/09/2019 00:30, Boris Ostrovsky wrote: >>> On 9/8/19 5:11 PM, Igor Druzhinin wrote: On 08/09/2019 19:28, Boris Ostrovsky wrote: > On 9/6/19 7:00 PM, Igor Druzhinin wrote: >> On 06/09/2019 23:

Re: [PATCH] xen/pci: try to reserve MCFG areas earlier

2019-09-09 Thread Boris Ostrovsky
On 9/8/19 7:37 PM, Igor Druzhinin wrote: > On 09/09/2019 00:30, Boris Ostrovsky wrote: >> On 9/8/19 5:11 PM, Igor Druzhinin wrote: >>> On 08/09/2019 19:28, Boris Ostrovsky wrote: On 9/6/19 7:00 PM, Igor Druzhinin wrote: > On 06/09/2019 23:30, Boris Ostrovsky wrote: >> Where is MCFG par

Re: [PATCH] xen/pci: try to reserve MCFG areas earlier

2019-09-08 Thread Igor Druzhinin
On 09/09/2019 00:30, Boris Ostrovsky wrote: > On 9/8/19 5:11 PM, Igor Druzhinin wrote: >> On 08/09/2019 19:28, Boris Ostrovsky wrote: >>> On 9/6/19 7:00 PM, Igor Druzhinin wrote: On 06/09/2019 23:30, Boris Ostrovsky wrote: > Where is MCFG parsed? pci_arch_init()? >> It happens twice: >

Re: [PATCH] xen/pci: try to reserve MCFG areas earlier

2019-09-08 Thread Boris Ostrovsky
On 9/8/19 5:11 PM, Igor Druzhinin wrote: > On 08/09/2019 19:28, Boris Ostrovsky wrote: >> On 9/6/19 7:00 PM, Igor Druzhinin wrote: >>> On 06/09/2019 23:30, Boris Ostrovsky wrote: Where is MCFG parsed? pci_arch_init()? > It happens twice: >>> 1) first time early one in pci_arch_init() that

Re: [PATCH] xen/pci: try to reserve MCFG areas earlier

2019-09-08 Thread Igor Druzhinin
On 08/09/2019 19:28, Boris Ostrovsky wrote: > On 9/6/19 7:00 PM, Igor Druzhinin wrote: >> >> On 06/09/2019 23:30, Boris Ostrovsky wrote: >>> >>> Where is MCFG parsed? pci_arch_init()? It happens twice: >> 1) first time early one in pci_arch_init() that is arch_initcall - that >> time pci_mmcfg

Re: [PATCH] xen/pci: try to reserve MCFG areas earlier

2019-09-08 Thread Boris Ostrovsky
On 9/6/19 7:00 PM, Igor Druzhinin wrote: > > On 06/09/2019 23:30, Boris Ostrovsky wrote: >> On 9/3/19 8:20 PM, Igor Druzhinin wrote: >>> If MCFG area is not reserved in E820, Xen by default will defer its usage >>> until Dom0 registers it explicitly after ACPI parser recognizes it as >>> a reserved

Re: [PATCH] xen/pci: try to reserve MCFG areas earlier

2019-09-06 Thread Igor Druzhinin
On 06/09/2019 23:30, Boris Ostrovsky wrote: > On 9/3/19 8:20 PM, Igor Druzhinin wrote: >> If MCFG area is not reserved in E820, Xen by default will defer its usage >> until Dom0 registers it explicitly after ACPI parser recognizes it as >> a reserved resource in DSDT. Having it reserved in E820

Re: [PATCH] xen/pci: try to reserve MCFG areas earlier

2019-09-06 Thread Boris Ostrovsky
On 9/3/19 8:20 PM, Igor Druzhinin wrote: > If MCFG area is not reserved in E820, Xen by default will defer its usage > until Dom0 registers it explicitly after ACPI parser recognizes it as > a reserved resource in DSDT. Having it reserved in E820 is not > mandatory according to "PCI Firmware Specif

Re: [PATCH] xen/pci: try to reserve MCFG areas earlier

2019-09-04 Thread Jan Beulich
On 04.09.2019 13:36, Igor Druzhinin wrote: > On 04/09/2019 10:08, Jan Beulich wrote: >> On 04.09.2019 02:20, Igor Druzhinin wrote: >>> If MCFG area is not reserved in E820, Xen by default will defer its usage >>> until Dom0 registers it explicitly after ACPI parser recognizes it as >>> a reserved r

Re: [PATCH] xen/pci: try to reserve MCFG areas earlier

2019-09-04 Thread Igor Druzhinin
On 04/09/2019 10:08, Jan Beulich wrote: > On 04.09.2019 02:20, Igor Druzhinin wrote: >> If MCFG area is not reserved in E820, Xen by default will defer its usage >> until Dom0 registers it explicitly after ACPI parser recognizes it as >> a reserved resource in DSDT. Having it reserved in E820 is no

Re: [PATCH] xen/pci: try to reserve MCFG areas earlier

2019-09-04 Thread Jan Beulich
On 04.09.2019 02:20, Igor Druzhinin wrote: > If MCFG area is not reserved in E820, Xen by default will defer its usage > until Dom0 registers it explicitly after ACPI parser recognizes it as > a reserved resource in DSDT. Having it reserved in E820 is not > mandatory according to "PCI Firmware Spec