From: Dave Jiang <dave.jiang@intel.com>
To: Fenghua Yu <fenghua.yu@intel.com>, Vinod Koul <vkoul@kernel.org>
Cc: <dmaengine@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Tony Zhu <tony.zhu@intel.com>
Subject: Re: [PATCH v2] dmaengine: idxd: Clear PRS disable flag when disabling IDXD device
Date: Wed, 12 Jul 2023 10:58:47 -0700 [thread overview]
Message-ID: <56681a68-a2cc-6bd1-3e29-dfc02bc07add@intel.com> (raw)
In-Reply-To: <20230712174220.3434989-1-fenghua.yu@intel.com>
On 7/12/23 10:42, Fenghua Yu wrote:
> Disabling IDXD device doesn't reset Page Request Service (PRS)
> disable flag to its initial value 0. This may cause user confusion
> because once PRS is disabled user will see PRS still remains the
> previous setting (i.e. disabled) via sysfs interface even after the
> device is disabled.
>
> To eliminate the confusion, reset PRS disable flag when the device
> is disabled.
>
> Tested-by: Tony Zhu <tony.zhu@intel.com>
> Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
Should there be a Fixes tag?
> ---
> v2:
> - Fix Tony's email typo
>
> drivers/dma/idxd/device.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/dma/idxd/device.c b/drivers/dma/idxd/device.c
> index 5abbcc61c528..71dfb2c13066 100644
> --- a/drivers/dma/idxd/device.c
> +++ b/drivers/dma/idxd/device.c
> @@ -387,6 +387,7 @@ static void idxd_wq_disable_cleanup(struct idxd_wq *wq)
> clear_bit(WQ_FLAG_DEDICATED, &wq->flags);
> clear_bit(WQ_FLAG_BLOCK_ON_FAULT, &wq->flags);
> clear_bit(WQ_FLAG_ATS_DISABLE, &wq->flags);
> + clear_bit(WQ_FLAG_PRS_DISABLE, &wq->flags);
I wonder if it's better if we just do wq->flags = 0? I don't see any
bits we need to preserve. Do you?
> memset(wq->name, 0, WQ_NAME_SIZE);
> wq->max_xfer_bytes = WQ_DEFAULT_MAX_XFER;
> idxd_wq_set_max_batch_size(idxd->data->type, wq, WQ_DEFAULT_MAX_BATCH);
next prev parent reply other threads:[~2023-07-12 17:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 17:42 Fenghua Yu
2023-07-12 17:58 ` Dave Jiang [this message]
2023-07-12 19:07 ` Fenghua Yu
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=56681a68-a2cc-6bd1-3e29-dfc02bc07add@intel.com \
--to=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.zhu@intel.com \
--cc=vkoul@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
all inboxes | Powered by JetHome®