From: Andrew Rybchenko <arybchenko@solarflare.com>
To: Jeff Guo <jia.guo@intel.com>, <stephen@networkplumber.org>,
<bruce.richardson@intel.com>, <ferruh.yigit@intel.com>,
<konstantin.ananyev@intel.com>, <gaetan.rivet@6wind.com>,
<jingjing.wu@intel.com>, <thomas@monjalon.net>,
<motih@mellanox.com>, <matan@mellanox.com>,
<harry.van.haaren@intel.com>, <qi.z.zhang@intel.com>,
<shaopeng.he@intel.com>, <bernard.iremonger@intel.com>,
<anatoly.burakov@intel.com>
Cc: <jblunck@infradead.org>, <shreyansh.jain@nxp.com>, <dev@dpdk.org>,
<helin.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/4] eal: add a new req notifier to eal interrupt
Date: Tue, 2 Oct 2018 09:51:30 +0300 [thread overview]
Message-ID: <b6ac0d84-7cca-dd6f-f6d6-f117a2e69b36@solarflare.com> (raw)
In-Reply-To: <1f0a0bb8-8634-4412-1002-e84362b90fe2@intel.com>
On 10/2/18 7:30 AM, Jeff Guo wrote:
> hi, andrew
>
> thanks for your review again, see comment as below.
>
> On 10/1/2018 5:46 PM, Andrew Rybchenko wrote:
>> On 9/30/18 5:16 PM, Jeff Guo wrote:
>>> Add a new req notifier in eal interrupt for enable vfio hotplug.
>>>
>>> Signed-off-by: Jeff Guo<jia.guo@intel.com>
>>> ---
>>> v2->v1:
>>> no change
>>> ---
>>> lib/librte_eal/common/include/rte_eal_interrupts.h | 1 +
>>> lib/librte_eal/linuxapp/eal/eal_interrupts.c | 71
>>> ++++++++++++++++++++++
>>> 2 files changed, 72 insertions(+)
>>>
>>> diff --git a/lib/librte_eal/common/include/rte_eal_interrupts.h
>>> b/lib/librte_eal/common/include/rte_eal_interrupts.h
>>> index 6eb4932..2c47738 100644
>>> --- a/lib/librte_eal/common/include/rte_eal_interrupts.h
>>> +++ b/lib/librte_eal/common/include/rte_eal_interrupts.h
>>> @@ -35,6 +35,7 @@ enum rte_intr_handle_type {
>>> RTE_INTR_HANDLE_EXT, /**< external handler */
>>> RTE_INTR_HANDLE_VDEV, /**< virtual device */
>>> RTE_INTR_HANDLE_DEV_EVENT, /**< device event handle */
>>> + RTE_INTR_HANDLE_VFIO_REQ, /**< vfio device handle (req) */
>>
>> Alignment looks inconsistent. Is there any reason?
>>
>
> ok, it should be consistent.
>
>
>>> RTE_INTR_HANDLE_MAX /**< count of elements */
>>> };
>>> diff --git a/lib/librte_eal/linuxapp/eal/eal_interrupts.c
>>> b/lib/librte_eal/linuxapp/eal/eal_interrupts.c
>>> index 4076c6d..7f611b3 100644
>>> --- a/lib/librte_eal/linuxapp/eal/eal_interrupts.c
>>> +++ b/lib/librte_eal/linuxapp/eal/eal_interrupts.c
>>> @@ -308,6 +308,64 @@ vfio_disable_msix(const struct rte_intr_handle
>>> *intr_handle) {
>>> return ret;
>>> }
>>> +
>>> +/* enable req notifier */
>>> +static int
>>> +vfio_enable_req(const struct rte_intr_handle *intr_handle)
>>> +{
>>> + int len, ret;
>>> + char irq_set_buf[IRQ_SET_BUF_LEN];
>>
>> I see that it is copied from similar functions in the file, but
>> I'd suggest to initialize it with zeros using '= {};' just to make
>> sure that uninitialized on-stack data never go to kernel.
>>
>>> + struct vfio_irq_set *irq_set;
>>> + int *fd_ptr;
>>> +
>>> + len = sizeof(irq_set_buf);
>>> +
>>> + irq_set = (struct vfio_irq_set *) irq_set_buf;
>>> + irq_set->argsz = len;
>>> + irq_set->count = 1;
>>> + irq_set->flags = VFIO_IRQ_SET_DATA_EVENTFD |
>>> + VFIO_IRQ_SET_ACTION_TRIGGER;
>>> + irq_set->index = VFIO_PCI_REQ_IRQ_INDEX;
>>
>> It looks like it is the only difference (plus error log below) from
>> vfio_enable_msi(). May be it make sense to restructure code
>> to avoid duplication. Obviously it is not critical, but please,
>> consider.
>>
>> Similar comment is applicable to vfio_disable_req() below.
>>
>
> make sense, and i found that there are many duplication could be
> modify here, maybe we could just add param index type to
>
> some common function to enable/disable each type of the
> interrupts/req. I suggest to make other patch set which is aim to modify
>
> eal interrupt to do it. The same as the your above comment about char
> array initialize. Do you agree with that?
Yes, I agree.
>
>>> + irq_set->start = 0;
>>> + fd_ptr = (int *) &irq_set->data;
>>> + *fd_ptr = intr_handle->fd;
>>> +
>>> + ret = ioctl(intr_handle->vfio_dev_fd, VFIO_DEVICE_SET_IRQS,
>>> irq_set);
>>> +
>>> + if (ret) {
>>> + RTE_LOG(ERR, EAL, "Error enabling req interrupts for fd %d\n",
>>> + intr_handle->fd);
>>> + return -1;
>>> + }
>>> +
>>> + return 0;
>>> +}
>>> +
>>> +/* disable req notifier */
>>> +static int
>>> +vfio_disable_req(const struct rte_intr_handle *intr_handle)
>>> +{
>>> + struct vfio_irq_set *irq_set;
>>> + char irq_set_buf[IRQ_SET_BUF_LEN];
>>> + int len, ret;
>>> +
>>> + len = sizeof(struct vfio_irq_set);
>>> +
>>> + irq_set = (struct vfio_irq_set *) irq_set_buf;
>>> + irq_set->argsz = len;
>>> + irq_set->count = 0;
>>> + irq_set->flags = VFIO_IRQ_SET_DATA_NONE |
>>> VFIO_IRQ_SET_ACTION_TRIGGER;
>>> + irq_set->index = VFIO_PCI_REQ_IRQ_INDEX;
>>> + irq_set->start = 0;
>>> +
>>> + ret = ioctl(intr_handle->vfio_dev_fd, VFIO_DEVICE_SET_IRQS,
>>> irq_set);
>>> +
>>> + if (ret)
>>> + RTE_LOG(ERR, EAL, "Error disabling req interrupts for fd
>>> %d\n",
>>> + intr_handle->fd);
>>> +
>>> + return ret;
>>> +}
>>> #endif
>>> static int
>>> @@ -556,6 +614,10 @@ rte_intr_enable(const struct rte_intr_handle
>>> *intr_handle)
>>> if (vfio_enable_intx(intr_handle))
>>> return -1;
>>> break;
>>> + case RTE_INTR_HANDLE_VFIO_REQ:
>>> + if (vfio_enable_req(intr_handle))
>>> + return -1;
>>> + break;
>>> #endif
>>> /* not used at this moment */
>>> case RTE_INTR_HANDLE_DEV_EVENT:
>>> @@ -606,6 +668,11 @@ rte_intr_disable(const struct rte_intr_handle
>>> *intr_handle)
>>> if (vfio_disable_intx(intr_handle))
>>> return -1;
>>> break;
>>> + case RTE_INTR_HANDLE_VFIO_REQ:
>>> + if (vfio_disable_req(intr_handle))
>>> + return -1;
>>> + break;
>>> +
>>> #endif
>>> /* not used at this moment */
>>> case RTE_INTR_HANDLE_DEV_EVENT:
>>> @@ -682,6 +749,10 @@ eal_intr_process_interrupts(struct epoll_event
>>> *events, int nfds)
>>> bytes_read = 0;
>>> call = true;
>>> break;
>>> + case RTE_INTR_HANDLE_VFIO_REQ:
>>> + bytes_read = 0;
>>> + call = true;
>>> + break;
>>> default:
>>> bytes_read = 1;
>>> break;
>>
next prev parent reply other threads:[~2018-10-02 6:52 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 10:51 [dpdk-dev] [PATCH v1 0/5] Enable hotplug in vfio Jeff Guo
2018-08-17 10:51 ` [dpdk-dev] [PATCH v1 1/5] eal: add a new req notifier to eal interrupt Jeff Guo
2018-08-17 10:51 ` [dpdk-dev] [PATCH v1 2/5] eal: add a new req event to device event Jeff Guo
2018-08-20 10:37 ` Andrew Rybchenko
2018-08-21 6:56 ` Jeff Guo
2018-08-21 7:20 ` Andrew Rybchenko
2018-08-21 7:37 ` Jeff Guo
2018-08-17 10:51 ` [dpdk-dev] [PATCH v1 3/5] eal: modify device event callback process func Jeff Guo
2018-09-26 12:20 ` Burakov, Anatoly
2018-09-30 10:30 ` Jeff Guo
2018-09-26 12:20 ` Burakov, Anatoly
2018-09-30 10:31 ` Jeff Guo
2018-08-17 10:51 ` [dpdk-dev] [PATCH v1 4/5] pci: add req handler field to generic pci device Jeff Guo
2018-09-26 12:22 ` Burakov, Anatoly
2018-09-29 6:15 ` Jeff Guo
2018-10-01 7:51 ` Burakov, Anatoly
2018-08-17 10:51 ` [dpdk-dev] [PATCH v1 5/5] vfio: enable vfio hotplug by req notifier handler Jeff Guo
2018-09-26 12:28 ` Burakov, Anatoly
2018-09-29 5:51 ` Jeff Guo
2018-08-20 9:15 ` [dpdk-dev] [PATCH v1 0/5] Enable hotplug in vfio Gaëtan Rivet
2018-08-21 6:45 ` Jeff Guo
2018-08-21 8:17 ` Gaëtan Rivet
2018-09-30 14:16 ` [dpdk-dev] [PATCH v2 0/4] " Jeff Guo
2018-09-30 14:16 ` [dpdk-dev] [PATCH v2 1/4] eal: add a new req notifier to eal interrupt Jeff Guo
2018-10-01 9:46 ` Andrew Rybchenko
2018-10-02 4:30 ` Jeff Guo
2018-10-02 6:51 ` Andrew Rybchenko [this message]
2018-09-30 14:16 ` [dpdk-dev] [PATCH v2 2/4] eal: modify device event callback process func Jeff Guo
2018-10-01 9:46 ` Andrew Rybchenko
2018-10-02 4:45 ` Jeff Guo
2018-10-02 6:53 ` Andrew Rybchenko
2018-09-30 14:16 ` [dpdk-dev] [PATCH v2 3/4] pci: add req handler field to generic pci device Jeff Guo
2018-10-01 9:46 ` Andrew Rybchenko
2018-10-02 6:32 ` Jeff Guo
2018-09-30 14:16 ` [dpdk-dev] [PATCH v2 4/4] vfio: enable vfio hotplug by req notifier handler Jeff Guo
2018-10-01 9:47 ` Andrew Rybchenko
2018-10-02 5:42 ` Jeff Guo
2018-10-02 12:42 ` [dpdk-dev] [PATCH v2 0/4] Enable hotplug in vfio Jeff Guo
2018-10-02 12:42 ` [dpdk-dev] [PATCH v2 1/4] eal: add a new req notifier to eal interrupt Jeff Guo
2018-10-02 12:42 ` [dpdk-dev] [PATCH v2 2/4] eal: modify device event callback process func Jeff Guo
2018-10-02 12:42 ` [dpdk-dev] [PATCH v2 3/4] pci: add req handler field to generic pci device Jeff Guo
2018-10-02 12:42 ` [dpdk-dev] [PATCH v2 4/4] vfio: enable vfio hotplug by req notifier handler Jeff Guo
2018-10-02 12:44 ` [dpdk-dev] [PATCH v3 0/4] Enable hotplug in vfio Jeff Guo
2018-10-02 12:44 ` [dpdk-dev] [PATCH v3 1/4] eal: add a new req notifier to eal interrupt Jeff Guo
2018-10-02 12:45 ` [dpdk-dev] [PATCH v3 2/4] eal: modify device event callback process func Jeff Guo
2018-10-02 12:45 ` [dpdk-dev] [PATCH v3 3/4] pci: add req handler field to generic pci device Jeff Guo
2018-10-02 12:45 ` [dpdk-dev] [PATCH v3 4/4] vfio: enable vfio hotplug by req notifier handler Jeff Guo
2018-10-02 12:58 ` [dpdk-dev] [PATCH v3 0/4] Enable hotplug in vfio Jeff Guo
2018-10-02 12:58 ` [dpdk-dev] [PATCH v3 1/4] eal: add a new req notifier to eal interrupt Jeff Guo
2018-10-02 12:58 ` [dpdk-dev] [PATCH v3 2/4] eal: modify device event callback process func Jeff Guo
2018-10-02 12:58 ` [dpdk-dev] [PATCH v3 3/4] pci: add req handler field to generic pci device Jeff Guo
2018-10-02 12:58 ` [dpdk-dev] [PATCH v3 4/4] vfio: enable vfio hotplug by req notifier handler Jeff Guo
2018-10-02 14:15 ` Burakov, Anatoly
2018-10-04 5:05 ` Jeff Guo
2018-10-04 6:44 ` [dpdk-dev] [PATCH v4 0/4] Enable hotplug in vfio Jeff Guo
2018-10-04 6:44 ` [dpdk-dev] [PATCH v4 1/4] eal: add a new req notifier to eal interrupt Jeff Guo
2018-10-04 6:44 ` [dpdk-dev] [PATCH v4 2/4] eal: modify device event callback process func Jeff Guo
2018-10-04 6:44 ` [dpdk-dev] [PATCH v4 3/4] pci: add req handler field to generic pci device Jeff Guo
2018-10-15 9:12 ` Thomas Monjalon
2018-10-15 10:01 ` Thomas Monjalon
2018-10-04 6:44 ` [dpdk-dev] [PATCH v4 4/4] vfio: enable vfio hotplug by req notifier handler Jeff Guo
2018-10-04 9:11 ` [dpdk-dev] [PATCH v4 0/4] Enable hotplug in vfio Burakov, Anatoly
2018-10-15 21:47 ` Thomas Monjalon
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=b6ac0d84-7cca-dd6f-f6d6-f117a2e69b36@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=anatoly.burakov@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gaetan.rivet@6wind.com \
--cc=harry.van.haaren@intel.com \
--cc=helin.zhang@intel.com \
--cc=jblunck@infradead.org \
--cc=jia.guo@intel.com \
--cc=jingjing.wu@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=matan@mellanox.com \
--cc=motih@mellanox.com \
--cc=qi.z.zhang@intel.com \
--cc=shaopeng.he@intel.com \
--cc=shreyansh.jain@nxp.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).