From: Alex Williamson <alex.williamson@redhat.com>
To: Diana Craciun <diana.craciun@oss.nxp.com>
Cc: kvm@vger.kernel.org, bharatb.linux@gmail.com,
linux-kernel@vger.kernel.org, eric.auger@redhat.com
Subject: Re: [PATCH v5 10/10] vfio/fsl-mc: Add support for device reset
Date: Fri, 2 Oct 2020 14:50:27 -0600 [thread overview]
Message-ID: <20201002145027.35519087@x1.home> (raw)
In-Reply-To: <20200929090339.17659-11-diana.craciun@oss.nxp.com>
On Tue, 29 Sep 2020 12:03:39 +0300
Diana Craciun <diana.craciun@oss.nxp.com> wrote:
> Currently only resetting the DPRC container is supported which
> will reset all the objects inside it. Resetting individual
> objects is possible from the userspace by issueing commands
> towards MC firmware.
>
> Signed-off-by: Diana Craciun <diana.craciun@oss.nxp.com>
> ---
> drivers/vfio/fsl-mc/vfio_fsl_mc.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/vfio/fsl-mc/vfio_fsl_mc.c b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> index 0aff99cdf722..e1b2dea8a5fe 100644
> --- a/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> +++ b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> @@ -299,7 +299,19 @@ static long vfio_fsl_mc_ioctl(void *device_data, unsigned int cmd,
> }
> case VFIO_DEVICE_RESET:
> {
> - return -ENOTTY;
> + int ret;
> + struct fsl_mc_device *mc_dev = vdev->mc_dev;
> +
> + /* reset is supported only for the DPRC */
> + if (!is_fsl_mc_bus_dprc(mc_dev))
> + return -ENOTTY;
> +
> + ret = dprc_reset_container(mc_dev->mc_io, 0,
> + mc_dev->mc_handle,
> + mc_dev->obj_desc.id,
> + DPRC_RESET_OPTION_NON_RECURSIVE);
> + return ret;
> +
> }
> default:
> return -ENOTTY;
This should also result in setting the VFIO_DEVICE_FLAGS_RESET bit in
vfio_device_info.flags for the appropriate devices. Thanks,
Alex
prev parent reply other threads:[~2020-10-02 20:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 9:03 [PATCH v5 00/10] vfio/fsl-mc: VFIO support for FSL-MC device Diana Craciun
2020-09-29 9:03 ` [PATCH v5 01/10] vfio/fsl-mc: Add VFIO framework skeleton for fsl-mc devices Diana Craciun
2020-09-29 9:03 ` [PATCH v5 02/10] vfio/fsl-mc: Scan DPRC objects on vfio-fsl-mc driver bind Diana Craciun
2020-10-02 17:24 ` Alex Williamson
2020-10-05 17:24 ` Diana Craciun OSS
2020-09-29 9:03 ` [PATCH v5 03/10] vfio/fsl-mc: Implement VFIO_DEVICE_GET_INFO ioctl Diana Craciun
2020-09-29 9:03 ` [PATCH v5 04/10] vfio/fsl-mc: Implement VFIO_DEVICE_GET_REGION_INFO ioctl call Diana Craciun
2020-09-29 9:03 ` [PATCH v5 05/10] vfio/fsl-mc: Allow userspace to MMAP fsl-mc device MMIO regions Diana Craciun
2020-09-29 9:03 ` [PATCH v5 06/10] vfio/fsl-mc: Added lock support in preparation for interrupt handling Diana Craciun
2020-09-29 9:03 ` [PATCH v5 07/10] vfio/fsl-mc: Add irq infrastructure for fsl-mc devices Diana Craciun
2020-09-29 9:03 ` [PATCH v5 08/10] vfio/fsl-mc: trigger an interrupt via eventfd Diana Craciun
2020-09-29 11:27 ` kernel test robot
2020-10-02 20:29 ` Alex Williamson
2020-09-29 9:03 ` [PATCH v5 09/10] vfio/fsl-mc: Add read/write support for fsl-mc devices Diana Craciun
2020-10-02 20:50 ` Alex Williamson
2020-10-05 17:29 ` Diana Craciun OSS
2020-09-29 9:03 ` [PATCH v5 10/10] vfio/fsl-mc: Add support for device reset Diana Craciun
2020-10-02 20:50 ` Alex Williamson [this message]
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=20201002145027.35519087@x1.home \
--to=alex.williamson@redhat.com \
--cc=bharatb.linux@gmail.com \
--cc=diana.craciun@oss.nxp.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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