linux-kernel - Re: [PATCH V3 6/9] virtio-ccw: implement synchronize

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20220426124243-mutt-send-email-mst@kernel.org>
Date:   Tue, 26 Apr 2022 12:43:36 -0400
From:   "Michael S. Tsirkin" <mst@...hat.com>
To:     Cornelia Huck <cohuck@...hat.com>
Cc:     Jason Wang <jasowang@...hat.com>,
        Halil Pasic <pasic@...ux.ibm.com>,
        linux-kernel@...r.kernel.org,
        virtualization@...ts.linux-foundation.org, sgarzare@...hat.com,
        eperezma@...hat.com, lulu@...hat.com, tglx@...utronix.de,
        peterz@...radead.org, paulmck@...nel.org, maz@...nel.org
Subject: Re: [PATCH V3 6/9] virtio-ccw: implement synchronize_cbs()

On Tue, Apr 26, 2022 at 05:47:17PM +0200, Cornelia Huck wrote:
> On Mon, Apr 25 2022, "Michael S. Tsirkin" <mst@...hat.com> wrote:
> 
> > On Mon, Apr 25, 2022 at 11:53:24PM -0400, Michael S. Tsirkin wrote:
> >> On Tue, Apr 26, 2022 at 11:42:45AM +0800, Jason Wang wrote:
> >> > 
> >> > 在 2022/4/26 11:38, Michael S. Tsirkin 写道:
> >> > > On Mon, Apr 25, 2022 at 11:35:41PM -0400, Michael S. Tsirkin wrote:
> >> > > > On Tue, Apr 26, 2022 at 04:29:11AM +0200, Halil Pasic wrote:
> >> > > > > On Mon, 25 Apr 2022 09:59:55 -0400
> >> > > > > "Michael S. Tsirkin" <mst@...hat.com> wrote:
> >> > > > > 
> >> > > > > > On Mon, Apr 25, 2022 at 10:54:24AM +0200, Cornelia Huck wrote:
> >> > > > > > > On Mon, Apr 25 2022, "Michael S. Tsirkin" <mst@...hat.com> wrote:
> >> > > > > > > > On Mon, Apr 25, 2022 at 10:44:15AM +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@...utronix.de>
> >> > > > > > > > > Cc: Peter Zijlstra <peterz@...radead.org>
> >> > > > > > > > > Cc: "Paul E. McKenney" <paulmck@...nel.org>
> >> > > > > > > > > Cc: Marc Zyngier <maz@...nel.org>
> >> > > > > > > > > Cc: Halil Pasic <pasic@...ux.ibm.com>
> >> > > > > > > > > Cc: Cornelia Huck <cohuck@...hat.com>
> >> > > > > > > > > Signed-off-by: Jason Wang <jasowang@...hat.com>
> >> > > > > > > > 
> >> > > > > > > > This is the only one that is giving me pause. Halil, Cornelia,
> >> > > > > > > > should we be concerned about the performance impact here?
> >> > > > > > > > Any chance it can be tested?
> >> > > > > > > We can have a bunch of devices using the same airq structure, and the
> >> > > > > > > sync cb creates a choke point, same as registering/unregistering.
> >> > > > > > BTW can callbacks for multiple VQs run on multiple CPUs at the moment?
> >> > > > > I'm not sure I understand the question.
> >> > > > > 
> >> > > > > I do think we can have multiple CPUs that are executing some portion of
> >> > > > > virtio_ccw_int_handler(). So I guess the answer is yes. Connie what do you think?
> >> > > > > 
> >> > > > > On the other hand we could also end up serializing synchronize_cbs()
> >> > > > > calls for different devices if they happen to use the same airq_info. But
> >> > > > > this probably was not your question
> >> > > > 
> >> > > > I am less concerned about  synchronize_cbs being slow and more about
> >> > > > the slowdown in interrupt processing itself.
> >> > > > 
> >> > > > > > this patch serializes them on a spinlock.
> >> > > > > > 
> >> > > > > Those could then pile up on the newly introduced spinlock.
> 
> How bad would that be in practice? IIUC, we hit on the spinlock when
> - doing synchronize_cbs (should be rare)
> - processing queue interrupts for devices using per-device indicators
>   (which is the non-preferred path, which I would basically only expect
>   when running on an ancient or non-standard hypervisor)

this one is my concern. I am worried serializing everything on a single lock
will drastically regress performance here.


> - configuration change interrupts (should be rare)
> - during setup, reset, etc. (should not be a concern)
> 
> >> > > > > 
> >> > > > > Regards,
> >> > > > > Halil
> >> > > > Hmm yea ... not good.
> >> > > Is there any other way to synchronize with all callbacks?
> >> > 
> >> > 
> >> > Maybe using rwlock as airq handler?
> >> > 
> >> > Thanks
> >> > 
> >> 
> >> rwlock is still a shared cacheline bouncing between CPUs and
> >> a bunch of ordering instructions.
> >> Maybe something per-cpu + some IPIs to run things on all CPUs instead?
> >
> > ... and I think classic and device interrupts are different enough
> > here ...
> 
> You mean classic (per-device) and adapter interrupts, right?