From: Markus Elfring <Markus.Elfring@web.de>
To: Hillf Danton <hdanton@sina.com>, iommu@lists.linux-foundation.org
Cc: Kevin Tian <kevin.tian@intel.com>,
Yan Zhao <yan.y.zhao@intel.com>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Alex Williamson <alex.williamson@redhat.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [RFC PATCH] vfio: type1: fix kthread use case
Date: Tue, 7 Jul 2020 08:04:54 +0200 [thread overview]
Message-ID: <f29f7008-6489-0db3-86b3-5f83f5ed7770@web.de> (raw)
In-Reply-To: <20200707011420.1416-1-hdanton@sina.com>
…
> +++ b/drivers/vfio/vfio_iommu_type1.c
> @@ -2798,7 +2798,7 @@ static int vfio_iommu_type1_dma_rw_chunk
…
> - bool kthread = current->mm == NULL;
> + bool kthread_load_mm;
> size_t offset;
How do you think about to reduce the scope for such variables?
https://refactoring.com/catalog/reduceScopeOfVariable.html
…
> @@ -2812,11 +2812,12 @@ static int vfio_iommu_type1_dma_rw_chunk
…
> if (!mm)
> return -EPERM;
…
> + kthread_load_mm = current->flags & PF_KTHREAD &&
> + current->mm == NULL;
…
Would you like to apply a more succinct code variant?
+ kthread_load_mm = current->flags & PF_KTHREAD && !current->mm;
Regards,
Markus
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2020-07-07 6:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 10:49 [RFC PATCH] vfio: type1: fix kthread use case Hillf Danton
2020-07-06 11:32 ` Markus Elfring
2020-07-06 12:42 ` Hillf Danton
2020-07-06 13:33 ` Markus Elfring
2020-07-06 14:08 ` Hillf Danton
2020-07-06 14:04 ` Markus Elfring
2020-07-07 1:14 ` Hillf Danton
2020-07-07 6:04 ` Markus Elfring [this message]
2020-07-07 0:31 ` Yan Zhao
2020-07-07 2:00 ` Hillf Danton
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=f29f7008-6489-0db3-86b3-5f83f5ed7770@web.de \
--to=markus.elfring@web.de \
--cc=alex.williamson@redhat.com \
--cc=hch@lst.de \
--cc=hdanton@sina.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yan.y.zhao@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;
as well as URLs for NNTP newsgroup(s).