From: Juergen Gross <jgross@suse.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
sstabellini@kernel.org
Subject: [GIT PULL] xen: branch for v6.7-rc1
Date: Sat, 28 Oct 2023 17:55:24 +0200 [thread overview]
Message-ID: <20231028155524.19315-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-6.7-rc1-tag
xen: branch for v6.7-rc1
It contains the following patches:
- 2 small cleanup patches
- a fix for PCI passthrough under Xen
- a 4 patch series speeding up virtio under Xen with user space backends
Thanks.
Juergen
drivers/xen/Kconfig | 8 +-
drivers/xen/events/events_base.c | 3 +-
drivers/xen/evtchn.c | 2 +-
drivers/xen/privcmd.c | 407 +++++++++++++++++++++++-
drivers/xen/xen-pciback/conf_space.c | 19 +-
drivers/xen/xen-pciback/conf_space_capability.c | 8 +-
drivers/xen/xen-pciback/conf_space_header.c | 21 +-
drivers/xen/xenbus/xenbus_dev_frontend.c | 4 +-
drivers/xen/xenbus/xenbus_probe.c | 2 +-
include/uapi/xen/privcmd.h | 22 +-
include/xen/interface/hvm/ioreq.h | 51 +++
11 files changed, 508 insertions(+), 39 deletions(-)
Gustavo A. R. Silva (1):
xen/xenbus: Add __counted_by for struct read_buffer and use struct_size()
Juergen Gross (1):
xenbus: fix error exit in xenbus_init()
Marek Marczykowski-Górecki (1):
xen-pciback: Consider INTx disabled when MSI/MSI-X is enabled
Viresh Kumar (4):
xen: Make struct privcmd_irqfd's layout architecture independent
xen: irqfd: Use _IOW instead of the internal _IOC() macro
xen: evtchn: Allow shared registration of IRQ handers
xen: privcmd: Add support for ioeventfd
next reply other threads:[~2023-10-28 15:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-28 15:55 Juergen Gross [this message]
2023-11-01 20:50 ` 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=20231028155524.19315-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@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®