pcie: get rid of range checks
RFC PATCH 1/1 pcie: get rid of range checks
config cycle operations should be idempotent, so there's no need to complicate code with range checks.
---
Untested. Pls comment.
hw/pcie.c | 96 ++++++++++++++++++++++++++++++------------------------------- 1 files changed, 47 insertions(+), 49 deletions(-)
hw/pcie.c +47 -49
@@ -302,59 +302,57 @@ void pcie_cap_slot_write_config(PCIDevice *dev, addr, val, len, sltctl_prev, sltctl, sltsta);/* SLTCTL */ -if (ranges_overlap (addr, len, pos +PCI_EXP_SLTCTL ,2 )) { -PCIE_DEV_PRINTF (dev,"sltctl: 0x%02" PRIx16" -> 0x%02" PRIx16"\n" , - sltctl_prev, sltctl); -if (pci_word_test_and_clear_mask (exp_cap +PCI_EXP_SLTCTL , -PCI_EXP_SLTCTL_EIC )) { - sltsta ^=PCI_EXP_SLTSTA_EIS ;/* toggle PCI_EXP_SLTSTA_EIS bit */ -pci_set_word (exp_cap +PCI_EXP_SLTSTA , sltsta); -PCIE_DEV_PRINTF (dev,"PCI_EXP_SLTCTL_EIC: " -"sltsta -> 0x%02" PRIx16"\n" , - sltsta); - } - -/* -* The events control bits might be enabled or disabled, -* Check if the software notificastion condition is satisfied -* or disatisfied. -* -* 6.7.3.4 Software Notification of Hot-plug events -*/ -if (pci_msi_enabled (dev)) { -bool msi_trigger = - (sltctl &PCI_EXP_SLTCTL_HPIE ) && - ((sltctl_prev ^ sltctl) & sltctl &/* stlctl: 0 -> 1 */ - sltsta &PCI_EXP_HP_EV_SUPPORTED ); -if (msi_trigger) { -pci_msi_notify (dev,pcie_cap_flags_get_vector (dev)); - } - }else { -int int_level = - (sltctl &PCI_EXP_SLTCTL_HPIE ) && - (sltctl & sltsta &PCI_EXP_HP_EV_SUPPORTED ); -qemu_set_irq (dev->irq[dev->exp.hpev_intx], int_level); - } +PCIE_DEV_PRINTF (dev,"sltctl: 0x%02" PRIx16" -> 0x%02" PRIx16"\n" , + sltctl_prev, sltctl); +if (pci_word_test_and_clear_mask (exp_cap +PCI_EXP_SLTCTL , +PCI_EXP_SLTCTL_EIC )) { + sltsta ^=PCI_EXP_SLTSTA_EIS ;/* toggle PCI_EXP_SLTSTA_EIS bit */ +pci_set_word (exp_cap +PCI_EXP_SLTSTA , sltsta); +PCIE_DEV_PRINTF (dev,"PCI_EXP_SLTCTL_EIC: " +"sltsta -> 0x%02" PRIx16"\n" , + sltsta); + } -if (!((sltctl_prev ^ sltctl) &PCI_EXP_SLTCTL_SUPPORTED )) { -PCIE_DEV_PRINTF (dev, -"sprious command completion slctl " -"0x%" PRIx16" -> 0x%" PRIx16"\n" , - sltctl_prev, sltctl); +/* +* The events control bits might be enabled or disabled, +* Check if the software notificastion condition is satisfied +* or disatisfied. +* +* 6.7.3.4 Software Notification of Hot-plug events +*/ +if (pci_msi_enabled (dev)) { +bool msi_trigger = + (sltctl &PCI_EXP_SLTCTL_HPIE ) && + ((sltctl_prev ^ sltctl) & sltctl &/* stlctl: 0 -> 1 */ + sltsta &PCI_EXP_HP_EV_SUPPORTED ); +if (msi_trigger) { +pci_msi_notify (dev,pcie_cap_flags_get_vector (dev)); } + }else { +int int_level = + (sltctl &PCI_EXP_SLTCTL_HPIE ) && + (sltctl & sltsta &PCI_EXP_HP_EV_SUPPORTED ); +qemu_set_irq (dev->irq[dev->exp.hpev_intx], int_level); + } -/* command completion. -* Real hardware might take a while to complete -* requested command because physical movement would be involved -* like locking the electromechanical lock. -* However in our case, command is completed instantaneously above, -* so send a command completion event right now. -* -* 6.7.3.2 Command Completed Events -*/ -/* set command completed bit */ -pcie_cap_slot_event (dev,PCI_EXP_HP_EV_CCI ); +if (!((sltctl_prev ^ sltctl) &PCI_EXP_SLTCTL_SUPPORTED )) { +PCIE_DEV_PRINTF (dev, +"sprious command completion slctl " +"0x%" PRIx16" -> 0x%" PRIx16"\n" , + sltctl_prev, sltctl); } + +/* command completion. +* Real hardware might take a while to complete +* requested command because physical movement would be involved +* like locking the electromechanical lock. +* However in our case, command is completed instantaneously above, +* so send a command completion event right now. +* +* 6.7.3.2 Command Completed Events +*/ +/* set command completed bit */ +pcie_cap_slot_event (dev,PCI_EXP_HP_EV_CCI ); }void pcie_cap_slot_push_attention_button (PCIDevice *dev)
Signature · 1 line
1.7.3-rc1
Quoted 128 lines · Isaku Yamahata
Some comments below.
Quoted 80 lines · Michael S. Tsirkin
config cycle operations should be idempotent, so there's no need to complicate code with range checks.
Signed-off-by Michael S. Tsirkin <[email protected]>---
Untested. Pls comment.
hw/pcie.c | 96 ++++++++++++++++++++++++++++++------------------------------- 1 files changed, 47 insertions(+), 49 deletions(-)hw/pcie.c +22
-38@@ -302,59 +302,57 @@ void pcie_cap_slot_write_config(PCIDevice *dev, addr, val, len, sltctl_prev, sltctl, sltsta);/* SLTCTL */ -if (ranges_overlap (addr, len, pos +PCI_EXP_SLTCTL ,2 )) { -PCIE_DEV_PRINTF (dev,"sltctl: 0x%02" PRIx16" -> 0x%02" PRIx16"\n" , - sltctl_prev, sltctl); -if (pci_word_test_and_clear_mask (exp_cap +PCI_EXP_SLTCTL , -PCI_EXP_SLTCTL_EIC )) { - sltsta ^=PCI_EXP_SLTSTA_EIS ;/* toggle PCI_EXP_SLTSTA_EIS bit */ -pci_set_word (exp_cap +PCI_EXP_SLTSTA , sltsta); -PCIE_DEV_PRINTF (dev,"PCI_EXP_SLTCTL_EIC: " -"sltsta -> 0x%02" PRIx16"\n" , - sltsta); - } - -/* -* The events control bits might be enabled or disabled, -* Check if the software notificastion condition is satisfied -* or disatisfied. -* -* 6.7.3.4 Software Notification of Hot-plug events -*/ -if (pci_msi_enabled (dev)) { -bool msi_trigger = - (sltctl &PCI_EXP_SLTCTL_HPIE ) && - ((sltctl_prev ^ sltctl) & sltctl &/* stlctl: 0 -> 1 */ - sltsta &PCI_EXP_HP_EV_SUPPORTED ); -if (msi_trigger) { -pci_msi_notify (dev,pcie_cap_flags_get_vector (dev)); - } - }else { -int int_level = - (sltctl &PCI_EXP_SLTCTL_HPIE ) && - (sltctl & sltsta &PCI_EXP_HP_EV_SUPPORTED ); -qemu_set_irq (dev->irq[dev->exp.hpev_intx], int_level); - } +PCIE_DEV_PRINTF (dev,"sltctl: 0x%02" PRIx16" -> 0x%02" PRIx16"\n" , + sltctl_prev, sltctl); +if (pci_word_test_and_clear_mask (exp_cap +PCI_EXP_SLTCTL , +PCI_EXP_SLTCTL_EIC )) { + sltsta ^=PCI_EXP_SLTSTA_EIS ;/* toggle PCI_EXP_SLTSTA_EIS bit */ +pci_set_word (exp_cap +PCI_EXP_SLTSTA , sltsta); +PCIE_DEV_PRINTF (dev,"PCI_EXP_SLTCTL_EIC: " +"sltsta -> 0x%02" PRIx16"\n" , + sltsta); + } -if (!((sltctl_prev ^ sltctl) &PCI_EXP_SLTCTL_SUPPORTED )) { -PCIE_DEV_PRINTF (dev, -"sprious command completion slctl " -"0x%" PRIx16" -> 0x%" PRIx16"\n" , - sltctl_prev, sltctl); +/* +* The events control bits might be enabled or disabled, +* Check if the software notificastion condition is satisfied +* or disatisfied. +* +* 6.7.3.4 Software Notification of Hot-plug events +*/ +if (pci_msi_enabled (dev)) { +bool msi_trigger = + (sltctl &PCI_EXP_SLTCTL_HPIE ) && + ((sltctl_prev ^ sltctl) & sltctl &/* stlctl: 0 -> 1 */ + sltsta &PCI_EXP_HP_EV_SUPPORTED );hw/pcie.c void pcie_cap_slot_write_config(PCIDevice *dev, · line 337
Quoted 10 lines
hw/pcie.c +8
-0+if (msi_trigger) { +pci_msi_notify (dev,pcie_cap_flags_get_vector (dev)); } + }else { +int int_level = + (sltctl &PCI_EXP_SLTCTL_HPIE ) && + (sltctl & sltsta &PCI_EXP_HP_EV_SUPPORTED ); +qemu_set_irq (dev->irq[dev->exp.hpev_intx], int_level); + }The above two changes look okay.
Quoted 19 lines
hw/pcie.c +7
-11-/* command completion. -* Real hardware might take a while to complete -* requested command because physical movement would be involved -* like locking the electromechanical lock. -* However in our case, command is completed instantaneously above, -* so send a command completion event right now. -* -* 6.7.3.2 Command Completed Events -*/ -/* set command completed bit */ -pcie_cap_slot_event (dev,PCI_EXP_HP_EV_CCI ); +if (!((sltctl_prev ^ sltctl) &PCI_EXP_SLTCTL_SUPPORTED )) { +PCIE_DEV_PRINTF (dev, +"sprious command completion slctl " +"0x%" PRIx16" -> 0x%" PRIx16"\n" , + sltctl_prev, sltctl); } + +/* command completion. hw/pcie.c void pcie_cap_slot_write_config(PCIDevice *dev, · line 355
Quoted 10 lines
hw/pcie.c +10
-0+* Real hardware might take a while to complete +* requested command because physical movement would be involved +* like locking the electromechanical lock. +* However in our case, command is completed instantaneously above, +* so send a command completion event right now. +* +* 6.7.3.2 Command Completed Events +*/ +/* set command completed bit */ +pcie_cap_slot_event (dev,PCI_EXP_HP_EV_CCI );
Quoted 4 lines
But this isn't correct.
A single command to the slot means a single write to the slot control register. With this patch, the interrupt is raised at every time the configuration space is written no matter which offset is used.
I think no, because the logic behind pcie_cap_slot_event guarantees that interrupt is only sent when something changes. What am I missing?
Quoted 11 lines
Quoted 5 lines
From 6.7.3.2
Software issues a command to a hot-plug capable Downstream Port by issuing a write transaction that targets any portion of the Port's Slot Control register. A single write to the Slot Control register is considered to be a single command...
Quoted 2 lines
The Port must process the command normally even if the status field is already set when the command is issued.
With this clause, I don't see any other better way than range check unfortunately.
That would definitely be right if we did anything with the command besides just sending an interrupt. In that case, command processing could would go to within range overlap, the rest would stay without.
Quoted 2 lines
Signature · 1 line
yamahata
Some comments below.
Quoted 80 lines · Michael S. Tsirkin
config cycle operations should be idempotent, so there's no need to complicate code with range checks.
Signed-off-by Michael S. Tsirkin <[email protected]>---
Untested. Pls comment.
hw/pcie.c | 96 ++++++++++++++++++++++++++++++------------------------------- 1 files changed, 47 insertions(+), 49 deletions(-)hw/pcie.c +22
-38@@ -302,59 +302,57 @@ void pcie_cap_slot_write_config(PCIDevice *dev, addr, val, len, sltctl_prev, sltctl, sltsta);/* SLTCTL */ -if (ranges_overlap (addr, len, pos +PCI_EXP_SLTCTL ,2 )) { -PCIE_DEV_PRINTF (dev,"sltctl: 0x%02" PRIx16" -> 0x%02" PRIx16"\n" , - sltctl_prev, sltctl); -if (pci_word_test_and_clear_mask (exp_cap +PCI_EXP_SLTCTL , -PCI_EXP_SLTCTL_EIC )) { - sltsta ^=PCI_EXP_SLTSTA_EIS ;/* toggle PCI_EXP_SLTSTA_EIS bit */ -pci_set_word (exp_cap +PCI_EXP_SLTSTA , sltsta); -PCIE_DEV_PRINTF (dev,"PCI_EXP_SLTCTL_EIC: " -"sltsta -> 0x%02" PRIx16"\n" , - sltsta); - } - -/* -* The events control bits might be enabled or disabled, -* Check if the software notificastion condition is satisfied -* or disatisfied. -* -* 6.7.3.4 Software Notification of Hot-plug events -*/ -if (pci_msi_enabled (dev)) { -bool msi_trigger = - (sltctl &PCI_EXP_SLTCTL_HPIE ) && - ((sltctl_prev ^ sltctl) & sltctl &/* stlctl: 0 -> 1 */ - sltsta &PCI_EXP_HP_EV_SUPPORTED ); -if (msi_trigger) { -pci_msi_notify (dev,pcie_cap_flags_get_vector (dev)); - } - }else { -int int_level = - (sltctl &PCI_EXP_SLTCTL_HPIE ) && - (sltctl & sltsta &PCI_EXP_HP_EV_SUPPORTED ); -qemu_set_irq (dev->irq[dev->exp.hpev_intx], int_level); - } +PCIE_DEV_PRINTF (dev,"sltctl: 0x%02" PRIx16" -> 0x%02" PRIx16"\n" , + sltctl_prev, sltctl); +if (pci_word_test_and_clear_mask (exp_cap +PCI_EXP_SLTCTL , +PCI_EXP_SLTCTL_EIC )) { + sltsta ^=PCI_EXP_SLTSTA_EIS ;/* toggle PCI_EXP_SLTSTA_EIS bit */ +pci_set_word (exp_cap +PCI_EXP_SLTSTA , sltsta); +PCIE_DEV_PRINTF (dev,"PCI_EXP_SLTCTL_EIC: " +"sltsta -> 0x%02" PRIx16"\n" , + sltsta); + } -if (!((sltctl_prev ^ sltctl) &PCI_EXP_SLTCTL_SUPPORTED )) { -PCIE_DEV_PRINTF (dev, -"sprious command completion slctl " -"0x%" PRIx16" -> 0x%" PRIx16"\n" , - sltctl_prev, sltctl); +/* +* The events control bits might be enabled or disabled, +* Check if the software notificastion condition is satisfied +* or disatisfied. +* +* 6.7.3.4 Software Notification of Hot-plug events +*/ +if (pci_msi_enabled (dev)) { +bool msi_trigger = + (sltctl &PCI_EXP_SLTCTL_HPIE ) && + ((sltctl_prev ^ sltctl) & sltctl &/* stlctl: 0 -> 1 */ + sltsta &PCI_EXP_HP_EV_SUPPORTED );
hw/pcie.c void pcie_cap_slot_write_config(PCIDevice *dev, · line 337
Quoted 10 lines
hw/pcie.c +8
-0+if (msi_trigger) { +pci_msi_notify (dev,pcie_cap_flags_get_vector (dev)); } + }else { +int int_level = + (sltctl &PCI_EXP_SLTCTL_HPIE ) && + (sltctl & sltsta &PCI_EXP_HP_EV_SUPPORTED ); +qemu_set_irq (dev->irq[dev->exp.hpev_intx], int_level); + }
The above two changes look okay.
Quoted 19 lines
hw/pcie.c +7
-11-/* command completion. -* Real hardware might take a while to complete -* requested command because physical movement would be involved -* like locking the electromechanical lock. -* However in our case, command is completed instantaneously above, -* so send a command completion event right now. -* -* 6.7.3.2 Command Completed Events -*/ -/* set command completed bit */ -pcie_cap_slot_event (dev,PCI_EXP_HP_EV_CCI ); +if (!((sltctl_prev ^ sltctl) &PCI_EXP_SLTCTL_SUPPORTED )) { +PCIE_DEV_PRINTF (dev, +"sprious command completion slctl " +"0x%" PRIx16" -> 0x%" PRIx16"\n" , + sltctl_prev, sltctl); } + +/* command completion.
hw/pcie.c void pcie_cap_slot_write_config(PCIDevice *dev, · line 355
Quoted 10 lines
hw/pcie.c +10
-0+* Real hardware might take a while to complete +* requested command because physical movement would be involved +* like locking the electromechanical lock. +* However in our case, command is completed instantaneously above, +* so send a command completion event right now. +* +* 6.7.3.2 Command Completed Events +*/ +/* set command completed bit */ +pcie_cap_slot_event (dev,PCI_EXP_HP_EV_CCI );
But this isn't correct.
A single command to the slot means a single write to the slot control register. With this patch, the interrupt is raised at every time the configuration space is written no matter which offset is used.
Quoted 5 lines
From 6.7.3.2
Software issues a command to a hot-plug capable Downstream Port by issuing a write transaction that targets any portion of the Port's Slot Control register. A single write to the Slot Control register is considered to be a single command
...
Quoted 2 lines
The Port must process the command normally even if the status field is already set when the command is issued.
With this clause, I don't see any other better way than range check unfortunately.
Signature · 1 line
yamahata