[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <67b7a01c-9de5-d520-d465-e4e3954302e2@oracle.com>
Date: Tue, 23 Feb 2021 10:44:58 -0500
From: Boris Ostrovsky <boris.ostrovsky@...cle.com>
To: Juergen Gross <jgross@...e.com>, xen-devel@...ts.xenproject.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-block@...r.kernel.org, linux-scsi@...r.kernel.org
Cc: Stefano Stabellini <sstabellini@...nel.org>,
stable@...r.kernel.org, Wei Liu <wei.liu@...nel.org>,
Paul Durrant <paul@....org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Roger Pau Monné <roger.pau@...rix.com>,
Jens Axboe <axboe@...nel.dk>
Subject: Re: [PATCH v3 0/8] xen/events: bug fixes and some diagnostic aids
On 2/19/21 10:40 AM, Juergen Gross wrote:
> The first four patches are fixes for XSA-332. The avoid WARN splats
> and a performance issue with interdomain events.
>
> Patches 5 and 6 are some additions to event handling in order to add
> some per pv-device statistics to sysfs and the ability to have a per
> backend device spurious event delay control.
>
> Patches 7 and 8 are minor fixes I had lying around.
>
> Juergen Gross (8):
> xen/events: reset affinity of 2-level event when tearing it down
> xen/events: don't unmask an event channel when an eoi is pending
> xen/events: avoid handling the same event on two cpus at the same time
> xen/netback: fix spurious event detection for common event case
> xen/events: link interdomain events to associated xenbus device
> xen/events: add per-xenbus device event statistics and settings
> xen/evtchn: use smp barriers for user event ring
> xen/evtchn: use READ/WRITE_ONCE() for accessing ring indices
>
I am going to pick up the last 3 patches since Ross appears to be having some issues with #2 (and 4 and 5 went in via netdev tree)
-boris
Powered by blists - more mailing lists