From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Cc: gavin.bowe@oracle.com, kurt.hackel@oracle.com
Subject: What went in Linux 3.6, 3.7 and 3.8 from Xen standpoint.
Date: Fri, 15 Feb 2013 11:26:51 -0500 [thread overview]
Message-ID: <20130215162651.GB13775@phenom.dumpdata.com> (raw)
Hey,
I realized I hadn't done my usual 'here is what goes in' for about half-a-year.
So catching up and doing it all at once.
v3.6:
- Fix a lot of bugs: Systems with MP BIOS failing, Systems with ACPI NUMA failing,
FLR in xen-pciback leaving the devices unusable, 32-bit PCI sounds cards in dom0
not working, fix crashes when using acpidump, fix crashes with CONFIG_MAX_DOMAIN_PAGES=512
- Make the P2M interaction on MMIO ranges use less memory during booting
(aka, Reuse existing P2M leafs).
- Simplification and cleanups in the code base. Coverity fixes
- Performance optimizations by caching TLS and GDT descriptors
- Performance optimizations in PTE page manipulations
- Xen MCE driver added (to see MCE events that Xen hypervisor gets)
- Xen PCPU driver added (to online/offline physical CPUs via dom0)
v3.7:
- Initial support for ARM working under Xen as both guest and initial domain.
- Security fixes.
- Fix RCU warning, add fallback code for old hypervisors, fix memory leaks in
gntdev driver, fix some pvops calls failing, Fixes in
xen-[kbd|fb|blk|net|hvc]-backend to deal with CLOSED transition
- Allow xen/privcmd to use v2 of MMAPBATCH command (and fixes for it)
- Support Xen backends to work with paged out grants (meaning work with HVM
guests that have its memory paged out)
- Performance optimization in xen/privcmd for migrating guests.
- Performance improvements when doing kdump for PVonHVM guests.
- Xen DBGP driver added (USB EHCI debug driver)
- FLR support in xen-pciback.
- Support wildcards in xen-pciback.hide=(*) argument parsing.
- Xen EFI support, and keyboard shift status flag.
- Late usage of Xen-SWIOTLB allowing PV PCI passthrough guest to boot without
'iommu=soft' as an argument and late initialization of SWIOTLB.
- Support more than 128GB in a PV guest.
- Cleanups in the initial pagetable creation.
v3.8:
- Persistent feature grant in xen-block system allowing greater performance.
- More fixes in the Xen-pciback for wildcard parsing
- Xen Processor Aggregator Device (PAD) added.
- Optimizations for xen/privcmd for ARM and PVH via new hypercall (add_to_physmap_range)
- Xen ARM can use the balloon driver
- Fixes for vcpu onlining/offlining, grant table initialization, parsing of cpu
onlining/offlining values, checks in xen-pciback, locking fixes in gtndev,
fix stack corruptions, fix xen_iret checks. xen-pciback DoSing dom0 with
messages, fix mmap batch ioctl error path.
- Further enh to allow PVHVM backend drivers (so moving dom0 functionality in guests)
next reply other threads:[~2013-02-15 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 16:26 Konrad Rzeszutek Wilk [this message]
2013-02-15 16:47 ` What went in Linux 3.6, 3.7 and 3.8 from Xen standpoint Jan Beulich
2013-02-15 16:47 ` [Xen-devel] " Jan Beulich
2013-02-15 17:30 ` Konrad Rzeszutek Wilk
2013-02-15 17:30 ` 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=20130215162651.GB13775@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=gavin.bowe@oracle.com \
--cc=kurt.hackel@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@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.