From: Juergen Gross <jgross@suse.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
boris.ostrovsky@oracle.com
Subject: [GIT PULL] xen: branch for v5.12-rc3
Date: Fri, 12 Mar 2021 09:34:00 +0100 [thread overview]
Message-ID: <20210312083400.2594-1-jgross@suse.com> (raw)
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-5.12b-rc3-tag
xen: branch for v5.12-rc3
It contains two patch series and a single patch:
- a small cleanup patch to remove unneeded symbol exports
- a series to cleanup Xen grant handling (avoiding allocations in some
cases, and using common defines for "invalid" values)
- a series to address a race issue in Xen event channel handling
Thanks.
Juergen
arch/arm/xen/p2m.c | 5 +-
arch/x86/xen/p2m.c | 6 +-
drivers/pci/xen-pcifront.c | 4 +-
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 ++--
drivers/xen/gntdev.c | 54 +++++++++------
include/xen/grant_table.h | 7 ++
include/xen/xenbus.h | 1 -
10 files changed, 169 insertions(+), 81 deletions(-)
Jan Beulich (4):
Xen: drop exports of {set,clear}_foreign_p2m_mapping()
Xen/gntdev: don't needlessly allocate k{,un}map_ops[]
Xen/gnttab: introduce common INVALID_GRANT_{HANDLE,REF}
Xen/gntdev: don't needlessly use kvcalloc()
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
next reply other threads:[~2021-03-12 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 8:34 Juergen Gross [this message]
2021-03-12 20:03 ` pr-tracker-bot
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=20210312083400.2594-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®