From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, xen-users@lists.xensource.com
Subject: Features for Linux kernel 3.3.
Date: Thu, 13 Oct 2011 15:32:15 -0400 [thread overview]
Message-ID: <20111013193214.GC16336@phenom.oracle.com> (raw)
This is what is being currently developed and reviewed. Some of it
might be done before 3.2 merge windows opens so it could become part
of 3.2:
- PV spinlocks. Jeremy has been tirelessly working on this and every time
it looks like it is ready somebody comes out and points out a bug
in generic code that impacts his work. So this has mushroomed to now
include jump_label support (for tracing), compare and exchange atomic
operations (for everything), and then the PV spinlocks patches.
- ACPI S3 support. The code is going through a review and we need
some eyes from the ACPI folks to make sure nothing is wrong.
- Graphic support for radeon/nouveau for 32-bit cards (enterprise type).
Also known as "TTM DMA pool" code.
- Blkback/blkfront features. Expanding the blkback to do amazing things.
Like make the code easier to read, expanding the discard support to support
REQ_DISCARD_SECURE and also do multipage rings (to allow more I/Os).
- microcode update. Well, this one is complex. The x86 maintainers
want to re-write how it is done, so the Xen microcode is shelved for
right now until that is complete.
- cleancache. This is the last piece of tmem - it allows the swap disk
to use the temporary memory pool that tmem provides to make the guest
run even faster.
- Xen ACPI cpufreq patches. They are not yet ready to be posted, but they
are slowly taking shape.
If I missed somebody's current work, please point me out to it.
next reply other threads:[~2011-10-13 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 19:32 Konrad Rzeszutek Wilk [this message]
2011-10-13 20:04 ` Features for Linux kernel 3.3 Dan Magenheimer
2011-10-13 20:07 ` Andy Burns
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=20111013193214.GC16336@phenom.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.