From: Jason Wang <jasowang@redhat.com>
To: Viktor Prutyanov <viktor@daynix.com>,
mst@redhat.com, marcel.apfelbaum@gmail.com, pbonzini@redhat.com,
peterx@redhat.com, david@redhat.com
Cc: philmd@linaro.org, qemu-devel@nongnu.org, yan@daynix.com,
yuri.benditovich@daynix.com
Subject: Re: [RFC PATCH 1/4] pci: add handling of Enable bit in ATS Control Register
Date: Wed, 26 Apr 2023 13:48:51 +0800 [thread overview]
Message-ID: <995c7ca6-edce-c7c5-919e-f8d1f31aabee@redhat.com> (raw)
In-Reply-To: <f169bd76-c638-edd6-a356-4ce69c19debc@redhat.com>
在 2023/4/26 13:31, Jason Wang 写道:
>
> 在 2023/4/24 19:21, Viktor Prutyanov 写道:
>> According to PCIe Address Translation Services specification 5.1.3.,
>> ATS Control Register has Enable bit to enable/disable ATS.
>> Add a new field for a trigger function which is called at the Enable
>> bit change, so that PCIe devices can handle ATS enable/disable.
>>
>> Signed-off-by: Viktor Prutyanov <viktor@daynix.com>
>> ---
>> hw/pci/pci.c | 1 +
>> hw/pci/pcie.c | 21 +++++++++++++++++++++
>> include/hw/pci/pci_device.h | 3 +++
>> include/hw/pci/pcie.h | 4 ++++
>> 4 files changed, 29 insertions(+)
>>
>> diff --git a/hw/pci/pci.c b/hw/pci/pci.c
>> index 208c16f450..79a47d2589 100644
>> --- a/hw/pci/pci.c
>> +++ b/hw/pci/pci.c
>> @@ -1550,6 +1550,7 @@ void pci_default_write_config(PCIDevice *d,
>> uint32_t addr, uint32_t val_in, int
>> msi_write_config(d, addr, val_in, l);
>> msix_write_config(d, addr, val_in, l);
>> pcie_sriov_config_write(d, addr, val_in, l);
>> + pcie_ats_config_write(d, addr, val_in, l);
>> }
>> /***********************************************************/
>> diff --git a/hw/pci/pcie.c b/hw/pci/pcie.c
>> index 924fdabd15..e0217161e5 100644
>> --- a/hw/pci/pcie.c
>> +++ b/hw/pci/pcie.c
>> @@ -1057,6 +1057,27 @@ void pcie_ats_init(PCIDevice *dev, uint16_t
>> offset, bool aligned)
>> pci_set_word(dev->wmask + dev->exp.ats_cap + PCI_ATS_CTRL,
>> 0x800f);
>> }
>> +void pcie_ats_config_write(PCIDevice *dev, uint32_t address,
>> uint32_t val,
>> + int len)
>> +{
>> + uint32_t off;
>> + uint16_t ats_cap = dev->exp.ats_cap;
>> +
>> + if (!ats_cap || address < ats_cap) {
>> + return;
>> + }
>> + off = address - ats_cap;
>> + if (off >= PCI_EXT_CAP_ATS_SIZEOF) {
>> + return;
>> + }
>> +
>> + if (range_covers_byte(off, len, PCI_ATS_CTRL + 1)) {
>
>
> Do we really need +1 here?
>
> The rest looks good.
>
> Thanks
>
>
>> + if (dev->ats_ctrl_trigger) {
>> + dev->ats_ctrl_trigger(dev, !!(val & PCI_ATS_CTRL_ENABLE));
>> + }
>> + }
Speak too fast.
We have virtio_write_config(), can we hook there? (We've already dealt
with FLR and bus master there)
Thanks
>> +}
>> +
>> /* ACS (Access Control Services) */
>> void pcie_acs_init(PCIDevice *dev, uint16_t offset)
>> {
>> diff --git a/include/hw/pci/pci_device.h b/include/hw/pci/pci_device.h
>> index d3dd0f64b2..2bb1d68f3b 100644
>> --- a/include/hw/pci/pci_device.h
>> +++ b/include/hw/pci/pci_device.h
>> @@ -160,6 +160,9 @@ struct PCIDevice {
>> /* ID of standby device in net_failover pair */
>> char *failover_pair_id;
>> uint32_t acpi_index;
>> +
>> + /* PCI ATS enable/disable trigger */
>> + void (*ats_ctrl_trigger)(PCIDevice *dev, bool enable);
>> };
>> static inline int pci_intx(PCIDevice *pci_dev)
>> diff --git a/include/hw/pci/pcie.h b/include/hw/pci/pcie.h
>> index 798a262a0a..5f2dbd87cf 100644
>> --- a/include/hw/pci/pcie.h
>> +++ b/include/hw/pci/pcie.h
>> @@ -154,4 +154,8 @@ void pcie_cap_slot_unplug_cb(HotplugHandler
>> *hotplug_dev, DeviceState *dev,
>> Error **errp);
>> void pcie_cap_slot_unplug_request_cb(HotplugHandler *hotplug_dev,
>> DeviceState *dev, Error **errp);
>> +
>> +void pcie_ats_config_write(PCIDevice *dev, uint32_t address,
>> uint32_t val,
>> + int len);
>> +
>> #endif /* QEMU_PCIE_H */
next prev parent reply other threads:[~2023-04-26 5:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 11:21 [RFC PATCH 0/4] vhost: register and change IOMMU flag depending on ATS state Viktor Prutyanov
2023-04-24 11:21 ` [RFC PATCH 1/4] pci: add handling of Enable bit in ATS Control Register Viktor Prutyanov
2023-04-26 5:31 ` Jason Wang
2023-04-26 5:48 ` Jason Wang [this message]
2023-05-02 21:35 ` Viktor Prutyanov
2023-04-24 11:21 ` [RFC PATCH 2/4] virtio-pci: add handling of ATS state change Viktor Prutyanov
2023-04-26 5:50 ` Jason Wang
2023-04-24 11:21 ` [RFC PATCH 3/4] memory: add interface for triggering IOMMU notify_flag_changed handler Viktor Prutyanov
2023-04-26 14:20 ` Peter Xu
2023-04-24 11:21 ` [RFC PATCH 4/4] vhost: register and change IOMMU flag depending on ATS state Viktor Prutyanov
2023-04-26 5:54 ` Jason Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=995c7ca6-edce-c7c5-919e-f8d1f31aabee@redhat.com \
--to=jasowang@redhat.com \
--cc=david@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=viktor@daynix.com \
--cc=yan@daynix.com \
--cc=yuri.benditovich@daynix.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).