From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Features and bug fixes for Linux kernel 3.3
Date: Mon, 9 Jan 2012 13:33:04 -0500 [thread overview]
Message-ID: <20120109183304.GA1287@phenom.dumpdata.com> (raw)
Hey,
Linux 3.3 merge window opened last week and today I've asked Linus
to pulled some of the patches. This is what is going in through
the Xen tree:
- SysFS documentation updates. We are slowly updating them to make sure that the SysFS
entires are properly documented.
- Making the grant system able to use more fancier types of grants to speed-up
guest to guest exchange of data (sub-page and transitive grants).
- Updates in the backends to be able to export the Xen backends in an
Hardware Virtualized Management (HVM) guest. We usually export those backends in
the initial domain (dom0), but are moving slowly to make it possible to do it any guest
(PV or HVM). NOTE: Only the netback version is in. The blkback needs an
Ack from Jens Axboe and while I am sure he will provide it it might be past the
merge window time-frame.
- Better driver to deal with memory type ioctls calls. In the past we were doing
ioctls on /proc/xen/priv_cmd (yuck) and with this are moving to doing it in
/dev/xen/priv_cmd.
- Fix a security issues were the guest could try to send a nasty (out of band)
message and potentially cause mishap.
- Remove duplicate initialization fields in the backend drivers.
- Jeremy is now working for a fancy new startup so changing the MAINTAINERS file to
reflect that his contribution are done during his private time.
- Sensible config options. We had some that weren't all that good so adjusting
them properly.
- Bug-fixes, fixing a bug in xen-pciback with the "Ownership but beware" bug.
In the Dave Airlie tree (DRM, graphics) the TTM DMA backend is going in. It allows the TTM
to pre-allocate (and setup DMA for them) the pages for graphics (similar to how network
layers do it) before using them. This means that both radeon and nouveau 32-bit cards
can now work properly with Xen, so that ATI ES1000 found in most server boxes will now
run X. 64-bit cards work just fine.
Full credit is as follow:
Annie Li (7):
xen/granttable: Introducing grant table V2 stucture
xen/granttable: Refactor some code
xen/granttable: Grant tables V2 implementation
xen/granttable: Keep code format clean
xen/granttable: Improve comments for function pointers
xen/granttable: Support sub-page grants
xen/granttable: Support transitive grants
Bastian Blank (5):
xen: Add privcmd device driver
xen: Add xenbus device driver
xen: Add xenbus_backend device
xen/privcmd: Remove unused support for arch specific privcmp mmap
xen/xenbus-frontend: Make error message more clear
Daniel De Graaf (10):
xen/gntalloc: Change gref_lock to a mutex
xen/gnt{dev,alloc}: reserve event channels for notify
xen/event: Add reference counting to event channels
xen/events: prevent calling evtchn_get on invalid channels
xen/gntalloc: release grant references on page free
xen/gntalloc: fix reference counts on multi-page mappings
xenbus: Support HVM backends
xenbus: Use grant-table wrapper functions
xen/grant-table: Support mappings required by blkback
xen/netback: Enable netback on HVM guests
David Vrabel (2):
xen: document balloon driver sysfs files
xen: document backend sysfs files
Ian Campbell (3):
xen/xenbus: Reject replies with payload > XENSTORE_PAYLOAD_MAX.
xenbus: maximum buffer size is XENSTORE_PAYLOAD_MAX
xen/xenbus: don't reimplement kvasprintf via a fixed size buffer
Jan Beulich (1):
Xen: consolidate and simplify struct xenbus_driver instantiation
Jeremy Fitzhardinge (1):
Xen: update MAINTAINER info
Julia Lawall (1):
xen-gntalloc: introduce missing kfree
Konrad Rzeszutek Wilk (7):
Merge branch 'stable/docs-for-3.3' into stable/for-linus-3.3
xen/xenbus-frontend: Fix compile error with randconfig
Merge commit 'v3.2-rc3' into stable/for-linus-3.3
xen/xenbus: Fix compile error - missing header for xen_initial_domain()
xen/pciback: Move the PCI_DEV_FLAGS_ASSIGNED ops to the "[un|]bind"
xen/pciback: Fix "device has been assigned to X domain!" warning
xen/pciback: Expand the warning message to include domain id.
Maxim Uvarov (1):
xen: Make XEN_MAX_DOMAIN_MEMORY have more sensible defaults
Tony Luck (1):
xen/ia64: fix build breakage because of conflicting u64 guest handles
next reply other threads:[~2012-01-09 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 18:33 Konrad Rzeszutek Wilk [this message]
2012-01-09 18:59 ` Features and bug fixes for Linux kernel 3.3 Stefan Kuhne
2012-01-09 21:13 ` Konrad Rzeszutek Wilk
2012-01-09 21:32 ` Konrad Rzeszutek Wilk
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=20120109183304.GA1287@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/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).