From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Re: Features and bug fixes for Linux kernel 3.3
Date: Mon, 9 Jan 2012 16:32:30 -0500 [thread overview]
Message-ID: <20120109213230.GD4773@phenom.dumpdata.com> (raw)
In-Reply-To: <20120109183304.GA1287@phenom.dumpdata.com>
On Mon, Jan 09, 2012 at 01:33:04PM -0500, Konrad Rzeszutek Wilk wrote:
> 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.
And in the Jens Axboe (block maintainer) we have patches to support the 'secure' DISCARD
operation for blkfront/blkback. It is TRIM/UNMAP with the option of securely erasing the media.
prev parent reply other threads:[~2012-01-09 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 18:33 Features and bug fixes for Linux kernel 3.3 Konrad Rzeszutek Wilk
2012-01-09 18:59 ` Stefan Kuhne
2012-01-09 21:13 ` Konrad Rzeszutek Wilk
2012-01-09 21:32 ` Konrad Rzeszutek Wilk [this message]
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=20120109213230.GD4773@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).