mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Cc: "xen-devel" <xen-devel@lists.xen.org>, <gavin.bowe@oracle.com>,
	<kurt.hackel@oracle.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] What went in Linux 3.6, 3.7 and 3.8 from Xen standpoint.
Date: Fri, 15 Feb 2013 16:47:47 +0000	[thread overview]
Message-ID: <511E74C302000078000BEDB1@nat28.tlf.novell.com> (raw)
In-Reply-To: <20130215162651.GB13775@phenom.dumpdata.com>

>>> On 15.02.13 at 17:26, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> 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,

Where?

> 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.

Jan


  reply	other threads:[~2013-02-15 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-15 16:26 Konrad Rzeszutek Wilk
2013-02-15 16:47 ` Jan Beulich [this message]
2013-02-15 17:30   ` [Xen-devel] " 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=511E74C302000078000BEDB1@nat28.tlf.novell.com \
    --to=jbeulich@suse.com \
    --cc=gavin.bowe@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=kurt.hackel@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xen.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®