From: Angus Chen <angus.chen@jaguarmicro.com>
To: Jason Wang <jasowang@redhat.com>
Cc: "mst@redhat.com" <mst@redhat.com>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"lingshan.zhu@intel.com" <lingshan.zhu@intel.com>
Subject: RE: [PATCH] virtio_pci: modify ENOENT to EINVAL
Date: Thu, 10 Nov 2022 03:30:59 +0000 [thread overview]
Message-ID: <TY2PR06MB342458CA2B7B5B8FDCD3366185019@TY2PR06MB3424.apcprd06.prod.outlook.com> (raw)
In-Reply-To: <CACGkMEs6ZTrf0NMXGuM=VYZC+zAujigiTG2CgE8gAdvxHc2Q7A@mail.gmail.com>
Hi Jason.
> -----Original Message-----
> From: Jason Wang <jasowang@redhat.com>
> Sent: Wednesday, November 2, 2022 1:34 PM
> To: Angus Chen <angus.chen@jaguarmicro.com>
> Cc: mst@redhat.com; virtualization@lists.linux-foundation.org;
> linux-kernel@vger.kernel.org; lingshan.zhu@intel.com
> Subject: Re: [PATCH] virtio_pci: modify ENOENT to EINVAL
>
> On Tue, Nov 1, 2022 at 7:17 PM Angus Chen <angus.chen@jaguarmicro.com>
> wrote:
> >
> > Virtio_crypto use max_data_queues+1 to setup vqs,
> > we use vp_modern_get_num_queues to protect the vq range in setup_vq.
> > We could enter index >= vp_modern_get_num_queues(mdev) in setup_vq
> > if common->num_queues is not set well,and it return -ENOENT.
> > It is better to use -EINVAL instead.
>
> I'm not sure I get this. It would be better to describe:
>
> 1) what kind of issues can we see if we return -ENOENT
> 2) why -EINVAL can help in this case
>
> Thanks
Thank you for your reply.
We use a robot to test our dpu to get the return value of probe.
We often get ENOENT form ' setup_vq ' function because of device error.
Most of time, my device can't handle queue_enable well.
This time,we get 'ENOENT' because the device set max_data_queues bigger than num_queues.
I think EINVAL is used when the value of some parameter is wrong.
Btw,it not a big deal,I can modify the robot to workaround.
>
> >
> > Signed-off-by: Angus Chen <angus.chen@jaguarmicro.com>
> > ---
> > drivers/virtio/virtio_pci_modern.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/virtio/virtio_pci_modern.c
> b/drivers/virtio/virtio_pci_modern.c
> > index c3b9f2761849..edf2e18014cd 100644
> > --- a/drivers/virtio/virtio_pci_modern.c
> > +++ b/drivers/virtio/virtio_pci_modern.c
> > @@ -303,7 +303,7 @@ static struct virtqueue *setup_vq(struct
> virtio_pci_device *vp_dev,
> > int err;
> >
> > if (index >= vp_modern_get_num_queues(mdev))
> > - return ERR_PTR(-ENOENT);
> > + return ERR_PTR(-EINVAL);
> >
> > /* Check if queue is either not available or already active. */
> > num = vp_modern_get_queue_size(mdev, index);
> > --
> > 2.25.1
> >
next prev parent reply other threads:[~2022-11-10 3:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 11:16 Angus Chen
2022-11-02 5:34 ` Jason Wang
2022-11-10 3:30 ` Angus Chen [this message]
2022-11-10 3:47 ` Jason Wang
2022-11-10 5:04 ` Michael S. Tsirkin
2022-11-10 5:19 ` 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=TY2PR06MB342458CA2B7B5B8FDCD3366185019@TY2PR06MB3424.apcprd06.prod.outlook.com \
--to=angus.chen@jaguarmicro.com \
--cc=jasowang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/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
all inboxes | Powered by JetHome®