xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com
Subject: Linux 3.4 patches..
Date: Wed, 14 Mar 2012 15:35:22 -0400	[thread overview]
Message-ID: <20120314193522.GG16960@phenom.dumpdata.com> (raw)

Hey,

So these are the patches I am aware of that are going in 3.4:
If there are some I've missed please respond to this email with your
patch.

Akinobu Mita (1):
      xen-blkfront: use bitmap_set() and bitmap_clear()

Alex Shi (1):
      xen: use this_cpu_xxx replace percpu_xxx funcs

Andrew Jones (1):
      xen/blkfront: don't put bdev right after getting it

Bastian Blank (4):
      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 (2):
      xen/blkback: use grant-table.c hypercall wrappers
      xen/blkback: Enable blkback on HVM guests

Ian Campbell (1):
      xen: only limit memory map to maximum reservation for domain 0.

Jan Beulich (3):
      xenbus: address compiler warnings
      xenbus: don't free other end details too early
      xen: constify all instances of "struct attribute_group"

Konrad Rzeszutek Wilk (13):
      xen: Add privcmd device driver
      xen/xenbus-frontend: Fix compile error with randconfig
      xen/xenbus: Fix compile error - missing header for xen_initial_domain()
      xen/mmu: Fix compile errors introduced by x86/memblock mismerge.
      pci: Introduce __pci_reset_function_locked to be used when holding device_lock.
      xen/pciback: Support pci_reset_function, aka FLR or D3 support.
      xen/cpu: Make VCPU hotplug code online CPUs properly.
      xen/setup/pm/acpi: Remove the call to boot_option_idle_override.
      xen/enlighten: Expose MWAIT and MWAIT_LEAF if hypervisor OKs it.
      xen/acpi-processor: C and P-state driver that uploads said data to hypervisor.
      xen/cpufreq: Disable the cpu frequency scaling drivers from loading.
      xen/acpi-processor: Do not depend on CPU frequency scaling drivers.
      [CPUFREQ]: provide disable_cpufreq() function to disable the API.

Stefano Stabellini (4):
      hvc_xen: support PV on HVM consoles
      hvc_xen: implement multiconsole support
      hvc_xen: introduce HVC_XEN_FRONTEND
      xen/xenbus: ignore console/0

Steven Noonan (1):
      xen-blkfront: make blkif_io_lock spinlock per-device

Tang Liang (1):
      xen: Utilize the restore_msi_irqs hook.


And these two are going through review:
      xen/blkback: Squash the discard support for 'file' and 'phy' type.
      xen/blkback: Make optional features be really optional.

             reply	other threads:[~2012-03-14 19:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 19:35 Konrad Rzeszutek Wilk [this message]
2012-03-14 20:09 ` Linux 3.4 patches Stefan Kuhne
2012-03-14 20:39   ` Konrad Rzeszutek Wilk
2012-03-15  9:14 ` Jan Beulich
2012-03-15 16:23   ` Konrad Rzeszutek Wilk
2012-03-15 18:42     ` Sander Eikelenboom
2012-03-15  9:42 ` Jan Beulich
2012-03-21  6:54 ` Ren, Yongjie
2012-03-21 16:07   ` 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=20120314193522.GG16960@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --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 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).