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.11-rc4
Date: Fri, 15 Jan 2021 15:31:53 +0100 [thread overview]
Message-ID: <20210115143153.30040-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.11-rc4-tag
xen: branch for v5.11-rc4
It contains:
- A series for fixing a regression when running as a fully virtualized
guest on an old Xen hypervisor not supporting PV interrupt callbacks
for HVM guests.
- A patch for adding support to query Xen resource sizes (setting was
possible already) from user mode.
Thanks.
Juergen
Documentation/admin-guide/kernel-parameters.txt | 4 ++
arch/arm/xen/enlighten.c | 2 +-
arch/x86/xen/enlighten_hvm.c | 15 ++++-
arch/x86/xen/smp_hvm.c | 27 ++++++---
drivers/xen/events/events_base.c | 10 ---
drivers/xen/platform-pci.c | 8 ++-
drivers/xen/privcmd.c | 25 ++++++--
drivers/xen/xenbus/xenbus.h | 1 +
drivers/xen/xenbus/xenbus_comms.c | 8 ---
drivers/xen/xenbus/xenbus_probe.c | 81 ++++++++++++++++++++-----
include/xen/xenbus.h | 2 +-
11 files changed, 129 insertions(+), 54 deletions(-)
David Woodhouse (5):
xen: Fix event channel callback via INTX/GSI
xen: Set platform PCI device INTX affinity to CPU0
x86/xen: Add xen_no_vector_callback option to test PCI INTX delivery
x86/xen: Don't register Xen IPIs when they aren't going to be used
x86/xen: Fix xen_hvm_smp_init() when vector callback not available
Roger Pau Monne (1):
xen/privcmd: allow fetching resource sizes
next reply other threads:[~2021-01-15 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 14:31 Juergen Gross [this message]
2021-01-15 18:58 ` pr-tracker-bot
2021-01-15 14:31 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=20210115143153.30040-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®