From: Neil Horman <nhorman@redhat.com>
To: David Kershner <david.kershner@unisys.com>
Cc: corbet@lwn.net, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, gregkh@linuxfoundation.org,
erik.arfvidson@unisys.com, timothy.sell@unisys.com,
hofrat@osadl.org, dzickus@redhat.com, jes.sorensen@redhat.com,
alexander.curtin@unisys.com, janani.rvchndrn@gmail.com,
sudipm.mukherjee@gmail.com, prarit@redhat.com,
david.binder@unisys.com, dan.j.williams@intel.com,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
sparmaintainer@unisys.com
Subject: Re: [PATCH v2 10/27] staging: unisys: visorinput: remove unnecessary locking
Date: Wed, 1 Jun 2016 10:17:48 -0400 [thread overview]
Message-ID: <20160601141748.GD4578@hmsreliant.think-freely.org> (raw)
In-Reply-To: <1464748013-31309-11-git-send-email-david.kershner@unisys.com>
On Tue, May 31, 2016 at 10:26:36PM -0400, David Kershner wrote:
> From: Tim Sell <Timothy.Sell@unisys.com>
>
> Locking in the _interrupt() function is NOT necessary so long as we ensure
> that interrupts have been stopped whenever we need to pause or resume the
> device, which we now do.
>
> While a device is paused, we ensure that interrupts stay disabled, i.e.
> that the _interrupt() function will NOT be called, yet remember the desired
> state in devdata->interrupts_enabled if open() or close() are called are
> called while the device is paused. Then when the device is resumed, we
> restore the actual state of interrupts (i.e., whether _interrupt() is going
> to be called or not) to the desired state in devdata->interrupts_enabled.
>
> Signed-off-by: Tim Sell <Timothy.Sell@unisys.com>
> Signed-off-by: David Kershner <david.kershner@unisys.com>
> ---
> drivers/staging/unisys/visorinput/visorinput.c | 57 +++++++++++++++++++++-----
> 1 file changed, 47 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/staging/unisys/visorinput/visorinput.c b/drivers/staging/unisys/visorinput/visorinput.c
> index 12a3570..9c00710 100644
> --- a/drivers/staging/unisys/visorinput/visorinput.c
> +++ b/drivers/staging/unisys/visorinput/visorinput.c
> @@ -66,6 +66,7 @@ struct visorinput_devdata {
> struct rw_semaphore lock_visor_dev; /* lock for dev */
> struct input_dev *visorinput_dev;
> bool paused;
> + bool interrupts_enabled;
> unsigned int keycode_table_bytes; /* size of following array */
> /* for keyboard devices: visorkbd_keycode[] + visorkbd_ext_keycode[] */
> unsigned char keycode_table[0];
> @@ -228,7 +229,21 @@ static int visorinput_open(struct input_dev *visorinput_dev)
> return -EINVAL;
> }
> dev_dbg(&visorinput_dev->dev, "%s opened\n", __func__);
> +
> + /*
> + * If we're not paused, really enable interrupts.
> + * Regardless of whether we are paused, set a flag indicating
> + * interrupts should be enabled so when we resume, interrupts
> + * will really be enabled.
> + */
> + down_write(&devdata->lock_visor_dev);
> + devdata->interrupts_enabled = true;
> + if (devdata->paused)
> + goto out_unlock;
Don't you want to wait until you actually enable interrupts here to set
interrupts_enabled to true? Otherwise, if devdata->paused is true, you will be
out of sync.
> visorbus_enable_channel_interrupts(devdata->dev);
> +
> +out_unlock:
> + up_write(&devdata->lock_visor_dev);
> return 0;
> }
>
> @@ -243,7 +258,22 @@ static void visorinput_close(struct input_dev *visorinput_dev)
> return;
> }
> dev_dbg(&visorinput_dev->dev, "%s closed\n", __func__);
> +
> + /*
> + * If we're not paused, really disable interrupts.
> + * Regardless of whether we are paused, set a flag indicating
> + * interrupts should be disabled so when we resume we will
> + * not re-enable them.
> + */
> +
> + down_write(&devdata->lock_visor_dev);
> + devdata->interrupts_enabled = false;
> + if (devdata->paused)
> + goto out_unlock;
Ditto to my above comment
> visorbus_disable_channel_interrupts(devdata->dev);
> +
> +out_unlock:
> + up_write(&devdata->lock_visor_dev);
> }
>
> /*
> @@ -438,10 +468,8 @@ visorinput_remove(struct visor_device *dev)
> * in visorinput_channel_interrupt()
> */
>
> - down_write(&devdata->lock_visor_dev);
> dev_set_drvdata(&dev->device, NULL);
> unregister_client_input(devdata->visorinput_dev);
> - up_write(&devdata->lock_visor_dev);
> kfree(devdata);
> }
>
> @@ -529,13 +557,7 @@ visorinput_channel_interrupt(struct visor_device *dev)
> if (!devdata)
> return;
>
> - down_write(&devdata->lock_visor_dev);
> - if (devdata->paused) /* don't touch device/channel when paused */
> - goto out_locked;
> -
> visorinput_dev = devdata->visorinput_dev;
> - if (!visorinput_dev)
> - goto out_locked;
>
> while (visorchannel_signalremove(dev->visorchannel, 0, &r)) {
> scancode = r.activity.arg1;
> @@ -611,8 +633,6 @@ visorinput_channel_interrupt(struct visor_device *dev)
> break;
> }
> }
> -out_locked:
> - up_write(&devdata->lock_visor_dev);
> }
>
> static int
> @@ -632,6 +652,14 @@ visorinput_pause(struct visor_device *dev,
> rc = -EBUSY;
> goto out_locked;
> }
> + if (devdata->interrupts_enabled)
> + visorbus_disable_channel_interrupts(dev);
> +
> + /*
> + * due to above, at this time no thread of execution will be
> + * in visorinput_channel_interrupt()
> + */
> +
> devdata->paused = true;
> complete_func(dev, 0);
> rc = 0;
> @@ -659,6 +687,15 @@ visorinput_resume(struct visor_device *dev,
> }
> devdata->paused = false;
> complete_func(dev, 0);
> +
> + /*
> + * Re-establish calls to visorinput_channel_interrupt() if that is
> + * the desired state that we've kept track of in interrupts_enabled
> + * while the device was paused.
> + */
> + if (devdata->interrupts_enabled)
> + visorbus_enable_channel_interrupts(dev);
> +
Unless I'm mistaken, it seems that visorinput_pause and visorinput_open or close
can be called in parallel on different cpus. As such the state of
interrupts_enabled may change during the execution of this function, which would
lead to interrupts not getting properly enabled.
> rc = 0;
> out_locked:
> up_write(&devdata->lock_visor_dev);
> --
> 1.9.1
>
next prev parent reply other threads:[~2016-06-01 14:17 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 2:26 [PATCH v2 00/27] Fixed issues raised by tglx, then move visorbus to drivers/virt David Kershner
2016-06-01 2:26 ` [PATCH v2 01/27] staging: unisys: visorbus change -1 return values David Kershner
2016-06-01 13:27 ` Neil Horman
2016-06-01 2:26 ` [PATCH v2 02/27] staging: unisys: visorchipset change -1 return value David Kershner
2016-06-01 13:11 ` Neil Horman
2016-06-01 2:26 ` [PATCH v2 03/27] staging: unisys: iovmcall_gnuc.h change -1 return values David Kershner
2016-06-01 13:36 ` Neil Horman
2016-06-01 2:26 ` [PATCH v2 04/27] staging: unisys: visorbus: remove unused module parameters David Kershner
2016-06-01 2:26 ` [PATCH v2 05/27] staging: unisys: visorbus: remove unused struct David Kershner
2016-06-01 2:26 ` [PATCH v2 06/27] staging: unisys: visorbus: modify format string to match argument David Kershner
2016-06-01 2:26 ` [PATCH v2 07/27] staging: unisys: visornic: Correct comment spelling mistake David Kershner
2016-06-01 2:26 ` [PATCH v2 08/27] staging: unisys: include: Remove thread-related enum members David Kershner
2016-06-01 2:26 ` [PATCH v2 09/27] staging: unisys: visorbus: removed unused periodic_test_workqueue David Kershner
2016-06-01 2:26 ` [PATCH v2 10/27] staging: unisys: visorinput: remove unnecessary locking David Kershner
2016-06-01 6:40 ` Thomas Gleixner
2016-06-03 4:34 ` Sell, Timothy C
2016-06-01 14:17 ` Neil Horman [this message]
2016-06-01 15:09 ` Sell, Timothy C
2016-06-01 18:42 ` Neil Horman
2016-06-02 5:02 ` Sell, Timothy C
2016-06-02 12:46 ` Neil Horman
2016-06-01 2:26 ` [PATCH v2 11/27] staging: unisys: visorbus: use kernel timer instead of workqueue David Kershner
2016-06-01 2:26 ` [PATCH v2 12/27] staging: unisys: visorbus: remove periodic_work.h/.c David Kershner
2016-06-01 2:26 ` [PATCH v2 13/27] staging: unisys: visorbus: Make visordriver_callback_lock a mutex David Kershner
2016-06-01 6:45 ` Thomas Gleixner
2016-06-01 2:26 ` [PATCH v2 14/27] staging: unisys: visorbus: Remove unnecessary EXPORT_SYMBOL statements David Kershner
2016-06-01 2:26 ` [PATCH v2 15/27] staging: unisys: visorbus: Remove unused functions David Kershner
2016-06-01 2:26 ` [PATCH v2 16/27] staging: unisys: Remove reference to unused STANDALONE_CLIENT David Kershner
2016-06-01 2:26 ` [PATCH v2 17/27] staging: unisys: visorbus: vbusdeviceinfo function descriptions more kerneldoc-like David Kershner
2016-06-01 2:26 ` [PATCH v2 18/27] staging: unisys: visorbus: make " David Kershner
2016-06-01 2:26 ` [PATCH v2 19/27] staging: unisys: visorbus: make visorbus_private.h " David Kershner
2016-06-01 2:26 ` [PATCH v2 20/27] staging: unisys: visorbus: make visorchannel " David Kershner
2016-06-01 6:43 ` Thomas Gleixner
2016-06-01 2:26 ` [PATCH v2 21/27] staging: unisys: visorbus: make visorchipset " David Kershner
2016-06-01 2:26 ` [PATCH v2 22/27] staging: unisys: visorbus: Move visorbus-unique functions to private header David Kershner
2016-06-01 2:26 ` [PATCH v2 23/27] staging: unisys: visorbus: Add kerneldoc-style comments for visorbus API David Kershner
2016-06-01 2:26 ` [PATCH v2 24/27] staging: unisys: Move vbushelper.h to visorbus directory David Kershner
2016-06-01 2:26 ` [PATCH v2 25/27] include: linux: visorbus: Add visorbus to include/linux directory David Kershner
2016-06-01 2:26 ` [PATCH v2 26/27] Documentation: Move visorbus documentation from staging to Documentation/ David Kershner
2016-06-01 2:26 ` [PATCH v2 27/27] drivers: Add visorbus to the drivers directory David Kershner
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=20160601141748.GD4578@hmsreliant.think-freely.org \
--to=nhorman@redhat.com \
--cc=alexander.curtin@unisys.com \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=david.binder@unisys.com \
--cc=david.kershner@unisys.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=dzickus@redhat.com \
--cc=erik.arfvidson@unisys.com \
--cc=gregkh@linuxfoundation.org \
--cc=hofrat@osadl.org \
--cc=hpa@zytor.com \
--cc=janani.rvchndrn@gmail.com \
--cc=jes.sorensen@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=sparmaintainer@unisys.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=tglx@linutronix.de \
--cc=timothy.sell@unisys.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®