stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Juergen Gross <jgross@suse.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 12/14] xen/events: use a common cpu hotplug hook for event channels
Date: Mon, 2 Nov 2020 16:53:42 +0100	[thread overview]
Message-ID: <20201102155342.GA1492224@kroah.com> (raw)
In-Reply-To: <20201102121722.10940-13-jgross@suse.com>

On Mon, Nov 02, 2020 at 01:17:20PM +0100, Juergen Gross wrote:
> Today only fifo event channels have a cpu hotplug callback. In order
> to prepare for more percpu (de)init work move that callback into
> events_base.c and add percpu_init() and percpu_deinit() hooks to
> struct evtchn_ops.
> 
> This is part of XSA-332.
> 
> This is upstream commit 7beb290caa2adb0a399e735a1e175db9aae0523a
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Juergen Gross <jgross@suse.com>
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> Reviewed-by: Wei Liu <wl@xen.org>xen/events: use a common cpu hotplug hook for event
>  channels
> 
> Today only fifo event channels have a cpu hotplug callback. In order
> to prepare for more percpu (de)init work move that callback into
> events_base.c and add percpu_init() and percpu_deinit() hooks to
> struct evtchn_ops.
> 
> This is part of XSA-332.
> 
> This is upstream commit 7beb290caa2adb0a399e735a1e175db9aae0523a
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Juergen Gross <jgross@suse.com>
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> Reviewed-by: Wei Liu <wl@xen.org>
> ---
>  drivers/xen/events/events_base.c     | 25 +++++++++++++++++
>  drivers/xen/events/events_fifo.c     | 40 +++++++++++++---------------
>  drivers/xen/events/events_internal.h |  3 +++
>  3 files changed, 47 insertions(+), 21 deletions(-)

Duplicated changelog text?  I'll edit it...

  reply	other threads:[~2020-11-02 15:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 12:17 [PATCH 00/14] Backport of patch series for stable 4.19 branch Juergen Gross
2020-11-02 12:17 ` [PATCH 01/14] xen/events: don't use chip_data for legacy IRQs Juergen Gross
2020-11-02 12:17 ` [PATCH 02/14] xen/events: avoid removing an event channel while handling it Juergen Gross
2020-11-02 12:17 ` [PATCH 03/14] xen/events: add a proper barrier to 2-level uevent unmasking Juergen Gross
2020-11-02 12:17 ` [PATCH 04/14] xen/events: fix race in evtchn_fifo_unmask() Juergen Gross
2020-11-02 12:17 ` [PATCH 05/14] xen/events: add a new "late EOI" evtchn framework Juergen Gross
2020-11-02 12:17 ` [PATCH 06/14] xen/blkback: use lateeoi irq binding Juergen Gross
2020-11-02 12:17 ` [PATCH 07/14] xen/netback: " Juergen Gross
2020-11-02 12:17 ` [PATCH 08/14] xen/scsiback: " Juergen Gross
2020-11-02 12:17 ` [PATCH 09/14] xen/pvcallsback: " Juergen Gross
2020-11-02 12:17 ` [PATCH 10/14] xen/pciback: " Juergen Gross
2020-11-02 12:17 ` [PATCH 11/14] xen/events: switch user event channels to lateeoi model Juergen Gross
2020-11-02 12:17 ` [PATCH 12/14] xen/events: use a common cpu hotplug hook for event channels Juergen Gross
2020-11-02 15:53   ` Greg KH [this message]
2020-11-02 12:17 ` [PATCH 13/14] xen/events: defer eoi in case of excessive number of events Juergen Gross
2020-11-02 12:17 ` [PATCH 14/14] xen/events: block rogue events for some time Juergen Gross
2020-11-02 15:55 ` [PATCH 00/14] Backport of patch series for stable 4.19 branch Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2020-11-02 15:56 [PATCH 00/14] Backport of patch series for stable 4.14 branch Juergen Gross
2020-11-02 15:57 ` [PATCH 12/14] xen/events: use a common cpu hotplug hook for event channels Juergen Gross

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=20201102155342.GA1492224@kroah.com \
    --to=greg@kroah.com \
    --cc=jgross@suse.com \
    --cc=stable@vger.kernel.org \
    /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).