On 9/13/2016 7:20 PM, Sinan Kaya wrote:
> On 9/13/2016 5:53 PM, Bjorn Helgaas wrote:
>>> + pci_bus_restore(dev->bus);
>> This path eventually writes the Bridge Control register:
>>
>> pci_reset_bridge_secondary_bus
>> pcibios_reset_secondary_bus
>> pci_reset_secondary_bus
>>
On 9/13/2016 7:20 PM, Sinan Kaya wrote:
> On 9/13/2016 5:53 PM, Bjorn Helgaas wrote:
>>> + pci_bus_restore(dev->bus);
>> This path eventually writes the Bridge Control register:
>>
>> pci_reset_bridge_secondary_bus
>> pcibios_reset_secondary_bus
>> pci_reset_secondary_bus
>>
On 9/13/2016 5:53 PM, Bjorn Helgaas wrote:
>> +pci_bus_restore(dev->bus);
> This path eventually writes the Bridge Control register:
>
> pci_reset_bridge_secondary_bus
> pcibios_reset_secondary_bus
> pci_reset_secondary_bus
> pci_write_config_word(dev, PCI_BRIDGE_CONTROL,
On 9/13/2016 5:53 PM, Bjorn Helgaas wrote:
>> +pci_bus_restore(dev->bus);
> This path eventually writes the Bridge Control register:
>
> pci_reset_bridge_secondary_bus
> pcibios_reset_secondary_bus
> pci_reset_secondary_bus
> pci_write_config_word(dev, PCI_BRIDGE_CONTROL,
On Thu, Sep 01, 2016 at 07:00:00PM -0400, Sinan Kaya wrote:
> A secondary bus reset causes settings to be lost by all downstream
> devices on the tree. The code is currently saving and restoring device
> states only when called from the VFIO path via pci_probe_reset_bus
> and pci_reset_bus
On Thu, Sep 01, 2016 at 07:00:00PM -0400, Sinan Kaya wrote:
> A secondary bus reset causes settings to be lost by all downstream
> devices on the tree. The code is currently saving and restoring device
> states only when called from the VFIO path via pci_probe_reset_bus
> and pci_reset_bus
Hi Bjorn,
On 9/13/2016 12:42 PM, Bjorn Helgaas wrote:
>
> This comment is no longer correct (you don't leave the devices in
> power-on state).
Sorry about that, I can fix the comment.
>
>> + */
>> +void pci_reset_bridge_secondary_bus(struct pci_dev *dev)
>> +{
>> +
Hi Bjorn,
On 9/13/2016 12:42 PM, Bjorn Helgaas wrote:
>
> This comment is no longer correct (you don't leave the devices in
> power-on state).
Sorry about that, I can fix the comment.
>
>> + */
>> +void pci_reset_bridge_secondary_bus(struct pci_dev *dev)
>> +{
>> +
On Thu, Sep 01, 2016 at 07:00:00PM -0400, Sinan Kaya wrote:
> A secondary bus reset causes settings to be lost by all downstream
> devices on the tree. The code is currently saving and restoring device
> states only when called from the VFIO path via pci_probe_reset_bus
> and pci_reset_bus
On Thu, Sep 01, 2016 at 07:00:00PM -0400, Sinan Kaya wrote:
> A secondary bus reset causes settings to be lost by all downstream
> devices on the tree. The code is currently saving and restoring device
> states only when called from the VFIO path via pci_probe_reset_bus
> and pci_reset_bus
A secondary bus reset causes settings to be lost by all downstream
devices on the tree. The code is currently saving and restoring device
states only when called from the VFIO path via pci_probe_reset_bus
and pci_reset_bus functions.
Moving the save and restore into pci_reset_bridge_secondary_bus
A secondary bus reset causes settings to be lost by all downstream
devices on the tree. The code is currently saving and restoring device
states only when called from the VFIO path via pci_probe_reset_bus
and pci_reset_bus functions.
Moving the save and restore into pci_reset_bridge_secondary_bus
12 matches
Mail list logo
