From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Cc: Juergen Gross <jgross@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Stefano Stabellini <sstabellini@kernel.org>,
stable@vger.kernel.org
Subject: [PATCH v4 0/3] xen/events: bug fixes and some diagnostic aids
Date: Sat, 6 Mar 2021 17:18:30 +0100 [thread overview]
Message-ID: <20210306161833.4552-1-jgross@suse.com> (raw)
Those are fixes for XSA-332.
The rest of the V3 patches have been applied already. There is one
additional fix in patch 2 which addresses network outages when a guest
is doing reboot loops.
Juergen Gross (3):
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
drivers/xen/events/events_2l.c | 22 +++--
drivers/xen/events/events_base.c | 130 ++++++++++++++++++++-------
drivers/xen/events/events_fifo.c | 7 --
drivers/xen/events/events_internal.h | 14 +--
4 files changed, 123 insertions(+), 50 deletions(-)
--
2.26.2
next reply other threads:[~2021-03-06 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 16:18 Juergen Gross [this message]
2021-03-06 16:18 ` [PATCH v4 1/3] xen/events: reset affinity of 2-level event when tearing it down Juergen Gross
2021-03-06 16:18 ` [PATCH v4 2/3] xen/events: don't unmask an event channel when an eoi is pending Juergen Gross
2021-03-08 20:33 ` Boris Ostrovsky
2021-03-09 5:14 ` Jürgen Groß
2021-03-09 8:57 ` Ross Lagerwall
2021-03-10 9:08 ` Ross Lagerwall
2021-03-06 16:18 ` [PATCH v4 3/3] xen/events: avoid handling the same event on two cpus at the same time Juergen Gross
2021-03-11 14:36 ` [PATCH v4 0/3] xen/events: bug fixes and some diagnostic aids Boris Ostrovsky
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=20210306161833.4552-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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).