From: Jason Wang <jasowang@redhat.com>
To: Hillf Danton <hdanton@sina.com>
Cc: mst <mst@redhat.com>, linux-kernel <linux-kernel@vger.kernel.org>,
Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [PATCH V3 6/9] virtio-ccw: implement synchronize_cbs()
Date: Tue, 26 Apr 2022 13:59:04 +0800 [thread overview]
Message-ID: <CACGkMEtM=Tb9LtYttj8MZ57sfThhLmU8m1-XF4iQGCcwZdPSmA@mail.gmail.com> (raw)
In-Reply-To: <20220426053856.3325-1-hdanton@sina.com>
On Tue, Apr 26, 2022 at 1:39 PM Hillf Danton <hdanton@sina.com> wrote:
>
> On Mon, 25 Apr 2022 10:44:15 +0800 Jason Wang 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 spinlock for irq is introduced ans used in the synchronization
> > method.
> >
> > 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>
> > 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..c19f07a82d62 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;
> > + spinlock_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;
> > +
> > + /*
> > + * Synchronize with the vring_interrupt() called by
> > + * virtio_ccw_int_handler().
> > + */
> > + spin_lock(&vcdev->irq_lock);
> > + spin_unlock(&vcdev->irq_lock);
>
> Given five lock acquirers, is the sync able to ensure the other four
> parties have complete their lock/unlock operations?
Just to make sure I understand the meaning of "four parties" here. It
looks to me the lock is only used in virtio_ccw_int_handler().
Thanks
>
> > +
> > + if (info) {
> > + /*
> > + * Synchronize with the vring_interrupt() with airq indicator
> > + */
> > + write_lock(&info->lock);
> > + write_unlock(&info->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,
> > };
> >
> >
> > @@ -1079,6 +1102,7 @@ static void virtio_ccw_int_handler(struct ccw_device *cdev,
> > {
> > __u32 activity = intparm & VIRTIO_CCW_INTPARM_MASK;
> > struct virtio_ccw_device *vcdev = dev_get_drvdata(&cdev->dev);
> > + unsigned long flags;
> > int i;
> > struct virtqueue *vq;
> >
> > @@ -1106,6 +1130,7 @@ static void virtio_ccw_int_handler(struct ccw_device *cdev,
> > vcdev->err = -EIO;
> > }
> > virtio_ccw_check_activity(vcdev, activity);
> > + spin_lock_irqsave(&vcdev->irq_lock, flags);
> > for_each_set_bit(i, indicators(vcdev),
> > sizeof(*indicators(vcdev)) * BITS_PER_BYTE) {
> > /* The bit clear must happen before the vring kick. */
> > @@ -1114,6 +1139,7 @@ static void virtio_ccw_int_handler(struct ccw_device *cdev,
> > vq = virtio_ccw_vq_by_ind(vcdev, i);
> > vring_interrupt(0, vq);
> > }
> > + spin_unlock_irqrestore(&vcdev->irq_lock, flags);
> > if (test_bit(0, indicators2(vcdev))) {
> > virtio_config_changed(&vcdev->vdev);
> > clear_bit(0, indicators2(vcdev));
> > @@ -1284,6 +1310,7 @@ static int virtio_ccw_online(struct ccw_device *cdev)
> > init_waitqueue_head(&vcdev->wait_q);
> > INIT_LIST_HEAD(&vcdev->virtqueues);
> > spin_lock_init(&vcdev->lock);
> > + spin_lock_init(&vcdev->irq_lock);
> > mutex_init(&vcdev->io_lock);
> >
> > spin_lock_irqsave(get_ccwdev_lock(cdev), flags);
> > --
> > 2.25.1
> >
> >
>
next prev parent reply other threads:[~2022-04-26 5:59 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 2:44 [PATCH V3 0/9] rework on the IRQ hardening of virtio Jason Wang
2022-04-25 2:44 ` [PATCH V3 1/9] virtio: use virtio_device_ready() in virtio_device_restore() Jason Wang
2022-04-28 9:07 ` Cornelia Huck
2022-04-25 2:44 ` [PATCH V3 2/9] virtio: use virtio_reset_device() when possible Jason Wang
2022-04-28 9:07 ` Cornelia Huck
2022-04-25 2:44 ` [PATCH V3 3/9] virtio: introduce config op to synchronize vring callbacks Jason Wang
2022-04-28 9:13 ` Cornelia Huck
2022-04-29 2:08 ` Jason Wang
2022-04-29 7:25 ` Cornelia Huck
2022-05-05 8:15 ` Jason Wang
2022-04-25 2:44 ` [PATCH V3 4/9] virtio-pci: implement synchronize_cbs() Jason Wang
2022-04-25 2:44 ` [PATCH V3 5/9] virtio-mmio: " Jason Wang
2022-04-25 2:44 ` [PATCH V3 6/9] virtio-ccw: " Jason Wang
2022-04-25 8:08 ` Michael S. Tsirkin
2022-04-25 8:54 ` Cornelia Huck
2022-04-25 13:59 ` Michael S. Tsirkin
2022-04-26 2:29 ` Halil Pasic
2022-04-26 3:35 ` Michael S. Tsirkin
2022-04-26 3:38 ` Michael S. Tsirkin
2022-04-26 3:42 ` Jason Wang
2022-04-26 3:53 ` Michael S. Tsirkin
2022-04-26 3:55 ` Michael S. Tsirkin
2022-04-26 4:07 ` Jason Wang
2022-04-26 6:30 ` Michael S. Tsirkin
2022-04-27 3:53 ` Jason Wang
2022-04-27 6:28 ` Michael S. Tsirkin
2022-04-27 6:30 ` Michael S. Tsirkin
2022-04-27 7:57 ` Jason Wang
2022-04-27 15:15 ` Michael S. Tsirkin
2022-04-26 15:47 ` Cornelia Huck
2022-04-26 16:43 ` Michael S. Tsirkin
2022-04-27 9:27 ` Cornelia Huck
2022-04-28 2:43 ` Halil Pasic
2022-04-28 3:04 ` Jason Wang
2022-04-28 5:24 ` Michael S. Tsirkin
2022-04-28 5:51 ` Jason Wang
2022-04-28 5:55 ` Michael S. Tsirkin
2022-04-28 6:02 ` Jason Wang
2022-04-28 6:17 ` Michael S. Tsirkin
2022-04-28 7:42 ` Cornelia Huck
2022-04-29 2:02 ` Jason Wang
2022-04-28 4:12 ` Michael S. Tsirkin
2022-04-26 2:50 ` Halil Pasic
2022-04-26 3:46 ` Jason Wang
[not found] ` <20220426053856.3325-1-hdanton@sina.com>
2022-04-26 5:59 ` Jason Wang [this message]
2022-04-25 2:44 ` [PATCH V3 7/9] virtio: allow to unbreak virtqueue Jason Wang
2022-04-25 12:44 ` Cornelia Huck
2022-04-25 14:04 ` Michael S. Tsirkin
2022-04-26 3:45 ` Jason Wang
2022-04-25 2:44 ` [PATCH V3 8/9] virtio: harden vring IRQ Jason Wang
2022-04-25 2:44 ` [PATCH V3 9/9] virtio: use WARN_ON() to warning illegal status value Jason Wang
2022-04-25 2:49 ` [PATCH V3 0/9] rework on the IRQ hardening of virtio 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='CACGkMEtM=Tb9LtYttj8MZ57sfThhLmU8m1-XF4iQGCcwZdPSmA@mail.gmail.com' \
--to=jasowang@redhat.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pasic@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).