From: Juergen Gross <jgross@suse.com>
To: xen-devel@lists.xenproject.org
Cc: "Juergen Gross" <jgross@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"George Dunlap" <george.dunlap@citrix.com>,
"Ian Jackson" <iwj@xenproject.org>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH v3 0/2] XSA-343 followup patches
Date: Fri, 16 Oct 2020 12:58:37 +0200 [thread overview]
Message-ID: <20201016105839.14796-1-jgross@suse.com> (raw)
The patches for XSA-343 produced some fallout, especially the event
channel locking has shown to be problematic.
Patch 1 is targeting fifo event channels for avoiding any races for the
case that the fifo queue has been changed for a specific event channel.
The second patch is modifying the per event channel locking scheme in
order to avoid deadlocks and problems due to the event channel lock
having been changed to require IRQs off by the XSA-343 patches.
Changes in V3:
- addressed comments
Juergen Gross (2):
xen/events: access last_priority and last_vcpu_id together
xen/evtchn: rework per event channel lock
xen/arch/x86/irq.c | 6 +-
xen/arch/x86/pv/shim.c | 9 +--
xen/common/event_channel.c | 109 +++++++++++++++++--------------------
xen/common/event_fifo.c | 25 +++++++--
xen/include/xen/event.h | 76 ++++++++++++++++++++++----
xen/include/xen/sched.h | 5 +-
6 files changed, 145 insertions(+), 85 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-16 10:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 10:58 Juergen Gross [this message]
2020-10-16 10:58 ` [PATCH v3 1/2] xen/events: access last_priority and last_vcpu_id together Juergen Gross
2020-11-04 9:42 ` Julien Grall
2020-10-16 10:58 ` [PATCH v3 2/2] xen/evtchn: rework per event channel lock Juergen Gross
2020-10-20 9:28 ` Jan Beulich
2020-11-02 13:41 ` Jürgen Groß
2020-11-02 13:52 ` Jan Beulich
2020-11-02 13:59 ` Jürgen Groß
2020-11-02 15:18 ` Jan Beulich
2020-11-02 15:26 ` Jürgen Groß
2020-11-04 9:50 ` Julien Grall
2020-11-04 9:56 ` Jürgen Groß
2020-11-04 10:02 ` Julien Grall
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=20201016105839.14796-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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).