From: Cornelia Huck <cohuck@redhat.com>
To: Jason Wang <jasowang@redhat.com>,
mst@redhat.com, jasowang@redhat.com,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Cc: lulu@redhat.com, paulmck@kernel.org, linux-s390@vger.kernel.org,
peterz@infradead.org, maz@kernel.org,
Peter Oberparleiter <oberpar@linux.ibm.com>,
pasic@linux.ibm.com, eperezma@redhat.com,
Vineeth Vijayan <vneethv@linux.ibm.com>,
tglx@linutronix.de
Subject: Re: [PATCH V5 6/9] virtio-ccw: implement synchronize_cbs()
Date: Wed, 18 May 2022 11:32:33 +0200 [thread overview]
Message-ID: <87tu9nfaoe.fsf@redhat.com> (raw)
In-Reply-To: <20220518035951.94220-7-jasowang@redhat.com>
On Wed, May 18 2022, Jason Wang <jasowang@redhat.com> wrote:
> This patch tries to implement the synchronize_cbs() for ccw. For the
> vring_interrupt() that is called via virtio_airq_handler(), the
> synchronization is simply done via the airq_info's lock. For the
> vring_interrupt() that is called via virtio_ccw_int_handler(), a per
> device rwlock is introduced ans used in the synchronization method.
s/ans/and/
>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: "Paul E. McKenney" <paulmck@kernel.org>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Halil Pasic <pasic@linux.ibm.com>
> Cc: Cornelia Huck <cohuck@redhat.com>
> Cc: Vineeth Vijayan <vneethv@linux.ibm.com>
> Cc: Peter Oberparleiter <oberpar@linux.ibm.com>
> Cc: linux-s390@vger.kernel.org
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
> drivers/s390/virtio/virtio_ccw.c | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/drivers/s390/virtio/virtio_ccw.c b/drivers/s390/virtio/virtio_ccw.c
> index d35e7a3f7067..22d36594bcdd 100644
> --- a/drivers/s390/virtio/virtio_ccw.c
> +++ b/drivers/s390/virtio/virtio_ccw.c
> @@ -62,6 +62,7 @@ struct virtio_ccw_device {
> unsigned int revision; /* Transport revision */
> wait_queue_head_t wait_q;
> spinlock_t lock;
> + rwlock_t irq_lock;
> struct mutex io_lock; /* Serializes I/O requests */
> struct list_head virtqueues;
> bool is_thinint;
> @@ -984,6 +985,27 @@ static const char *virtio_ccw_bus_name(struct virtio_device *vdev)
> return dev_name(&vcdev->cdev->dev);
> }
>
> +static void virtio_ccw_synchronize_cbs(struct virtio_device *vdev)
> +{
> + struct virtio_ccw_device *vcdev = to_vc_device(vdev);
> + struct airq_info *info = vcdev->airq_info;
> +
> + if (info) {
> + /*
> + * Synchronize with the vring_interrupt() with airq indicator
Maybe
/*
* This device uses adapter interrupts: synchronize with
* vring_interrupt() called by virtio_airq_handler() via the indicator
* area lock.
*/
> + */
> + write_lock_irq(&info->lock);
> + write_unlock_irq(&info->lock);
> + } else {
> + /*
> + * Synchronize with the vring_interrupt() called by
> + * virtio_ccw_int_handler().
/*
* This device uses classic interrupts: synchronize with
* vring_interrupt() called by virtio_ccw_int_handler() via the
* per-device irq_lock.
*/
> + */
> + write_lock_irq(&vcdev->irq_lock);
> + write_unlock_irq(&vcdev->irq_lock);
> + }
> +}
> +
> static const struct virtio_config_ops virtio_ccw_config_ops = {
> .get_features = virtio_ccw_get_features,
> .finalize_features = virtio_ccw_finalize_features,
> @@ -995,6 +1017,7 @@ static const struct virtio_config_ops virtio_ccw_config_ops = {
> .find_vqs = virtio_ccw_find_vqs,
> .del_vqs = virtio_ccw_del_vqs,
> .bus_name = virtio_ccw_bus_name,
> + .synchronize_cbs = virtio_ccw_synchronize_cbs,
> };
>
>
> @@ -1106,6 +1129,8 @@ static void virtio_ccw_int_handler(struct ccw_device *cdev,
> vcdev->err = -EIO;
> }
> virtio_ccw_check_activity(vcdev, activity);
> + /* Local interrupt should be disabled at this time */
/* Interrupts are disabled here. */
?
Interrupts enabled here would surely be a bug.
> + read_lock(&vcdev->irq_lock);
> for_each_set_bit(i, indicators(vcdev),
> sizeof(*indicators(vcdev)) * BITS_PER_BYTE) {
> /* The bit clear must happen before the vring kick. */
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-05-18 9:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 3:59 [PATCH V5 0/9] rework on the IRQ hardening of virtio Jason Wang
2022-05-18 3:59 ` [PATCH V5 1/9] virtio: use virtio_device_ready() in virtio_device_restore() Jason Wang
2022-05-18 3:59 ` [PATCH V5 2/9] virtio: use virtio_reset_device() when possible Jason Wang
2022-05-19 8:32 ` Stefano Garzarella
2022-05-18 3:59 ` [PATCH V5 3/9] virtio: introduce config op to synchronize vring callbacks Jason Wang
2022-05-19 8:34 ` Stefano Garzarella
2022-05-18 3:59 ` [PATCH V5 4/9] virtio-pci: implement synchronize_cbs() Jason Wang
2022-05-18 3:59 ` [PATCH V5 5/9] virtio-mmio: " Jason Wang
2022-05-18 3:59 ` [PATCH V5 6/9] virtio-ccw: " Jason Wang
2022-05-18 9:32 ` Cornelia Huck [this message]
2022-05-19 8:02 ` Jason Wang
2022-05-24 16:29 ` Halil Pasic
2022-05-18 3:59 ` [PATCH V5 7/9] virtio: allow to unbreak virtqueue Jason Wang
2022-05-18 10:03 ` Cornelia Huck
2022-05-19 8:08 ` Jason Wang
2022-05-18 3:59 ` [PATCH V5 8/9] virtio: harden vring IRQ Jason Wang
2022-05-18 3:59 ` [PATCH V5 9/9] virtio: use WARN_ON() to warn illegal status value Jason Wang
2022-05-19 8:34 ` Stefano Garzarella
2022-05-23 8:53 ` [PATCH V5 0/9] rework on the IRQ hardening of virtio Halil Pasic
2022-05-24 16:27 ` Halil Pasic
2022-05-25 2:33 ` Jason Wang
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=87tu9nfaoe.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=maz@kernel.org \
--cc=mst@redhat.com \
--cc=oberpar@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=vneethv@linux.ibm.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).