From: Dave Jiang <dave.jiang@intel.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org
Cc: Fenghua Yu <fenghua.yu@intel.com>, Vinod Koul <vkoul@kernel.org>,
Fengqian Gao <fengqian.gao@intel.com>,
"Shen, Xiaochen" <xiaochen.shen@intel.com>
Subject: Re: [PATCH 0/2] dmaengine: idxd: Fix up re-enabling device workqueues
Date: Mon, 19 Sep 2022 15:07:10 -0700 [thread overview]
Message-ID: <f43b7882-0d78-3977-9c42-665b21c1d03f@intel.com> (raw)
In-Reply-To: <20220919215553.600246-1-jsnitsel@redhat.com>
On 9/19/2022 2:55 PM, Jerry Snitselaar wrote:
> Currently if a software reset is attempted on an idxd device
> the workqueues will not be re-enabled, because it will see
> incorrectly see that wq->state is already set to IDXD_WQ_ENABLED.
> So set the workqueue state to disabled in idxd_wq_disable_cleanup(),
> and use a bitmap to track which workqueues have been enabled so they
> can be re-enabled during device re-initialization.
>
> Cc: Fenghua Yu <fenghua.yu@intel.com>
> Cc: Dave Jiang <dave.jiang@intel.com>
> Cc: Vinod Koul <vkoul@kernel.org>
For the series,
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
Thank you Jerry!
> Jerry Snitselaar (2):
> dmaengine: idxd: Set wq state to disabled in idxd_wq_disable_cleanup()
> dmaengine: idxd: track enabled workqueues in bitmap
>
> drivers/dma/idxd/device.c | 4 +++-
> drivers/dma/idxd/idxd.h | 2 ++
> drivers/dma/idxd/init.c | 6 ++++++
> drivers/dma/idxd/irq.c | 4 ++--
> drivers/dma/idxd/sysfs.c | 1 +
> 5 files changed, 14 insertions(+), 3 deletions(-)
>
prev parent reply other threads:[~2022-09-19 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 21:55 Jerry Snitselaar
2022-09-19 21:55 ` [PATCH 1/2] dmaengine: idxd: Set wq state to disabled in idxd_wq_disable_cleanup() Jerry Snitselaar
2022-09-19 21:55 ` [PATCH 2/2] dmaengine: idxd: track enabled workqueues in bitmap Jerry Snitselaar
2022-09-28 15:21 ` Jerry Snitselaar
2022-09-28 15:38 ` Dave Jiang
2022-09-19 22:07 ` Dave Jiang [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=f43b7882-0d78-3977-9c42-665b21c1d03f@intel.com \
--to=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=fengqian.gao@intel.com \
--cc=jsnitsel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.org \
--cc=xiaochen.shen@intel.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
all inboxes | Powered by JetHome®