>>> On 20.08.18 at 11:38, wrote:
> On 2018/8/20 15:45, Jan Beulich wrote:
> On 20.08.18 at 05:38, wrote:
>>> I'm thinking about moving below piece of code earlier too, and I checked
>>> pci_mmcfg_check_hostbridge() carefully, it's secure, what do you think
>>> about that?
>>>
>>>
On 2018/8/20 15:45, Jan Beulich wrote:
On 20.08.18 at 05:38, wrote:
On 2018/8/17 20:28, Jan Beulich wrote:
On 17.08.18 at 09:01, wrote:
pci_conf_read8() needs pci mmcfg mapping to work on multiple pci segments
system such as HPE Superdome-Flex.
Move acpi_mmcfg_init() call in
>>> On 20.08.18 at 05:38, wrote:
> On 2018/8/17 20:28, Jan Beulich wrote:
> On 17.08.18 at 09:01, wrote:
>>> pci_conf_read8() needs pci mmcfg mapping to work on multiple pci segments
>>> system such as HPE Superdome-Flex.
>>>
>>> Move acpi_mmcfg_init() call in acpi_boot_init() before calling
On 2018/8/17 20:28, Jan Beulich wrote:
On 17.08.18 at 09:01, wrote:
pci_conf_read8() needs pci mmcfg mapping to work on multiple pci segments
system such as HPE Superdome-Flex.
Move acpi_mmcfg_init() call in acpi_boot_init() before calling
acpi_parse_dmar() so that when pci_conf_read8() is
Ok, that make sense for me. Thanks for your detailed explanation, I will
rewrite the patch next week.
Sent from mobile
2018年8月17日 20:28于 Jan Beulich 写道：
>
> >>> On 17.08.18 at 09:01, wrote:
> > pci_conf_read8() needs pci mmcfg mapping to work on multiple pci segments
> > system such as HPE
>>> On 17.08.18 at 09:01, wrote:
> pci_conf_read8() needs pci mmcfg mapping to work on multiple pci segments
> system such as HPE Superdome-Flex.
>
> Move acpi_mmcfg_init() call in acpi_boot_init() before calling
> acpi_parse_dmar() so that when pci_conf_read8() is called in
>
pci_conf_read8() needs pci mmcfg mapping to work on multiple pci segments
system such as HPE Superdome-Flex.
Move acpi_mmcfg_init() call in acpi_boot_init() before calling
acpi_parse_dmar() so that when pci_conf_read8() is called in
acpi_parse_dev_scope(), we already have the mapping set up.
