From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com
Cc: Benjamin.Guthro@citrix.com, andrew.cooper3@citrix.com,
Daniel Kiper <daniel.kiper@oracle.com>,
stefan.bader@canonical.com, david.vrabel@citrix.com,
JBeulich@suse.com
Subject: Linux 3.11 and the future...
Date: Wed, 5 Jun 2013 16:19:09 -0400 [thread overview]
Message-ID: <20130605201909.GA17062@phenom.dumpdata.com> (raw)
There are couple of different patches that have not been reworked
or upstream properly for v3.11. The ones that I am aware of are:
a) PAT. For that to work right now properly one needs to revert
two git commits: c79c49826270b8b0061b2fca840fc3f013c8a78a
8eaffa67b43e99ae581622c5133e20b0f48bcef1 and cherrypick
x86/cpa: Use pte_attrs instead of pte_flags on CPA/set_p.._wb/wc operations.
b) microcode update. One needs to cherry-pick
xen: add CPU microcode update driver
x86/microcode: check proper return code.
microcode_xen: Add support for AMD family >= 15h
The one solution is to use the piggyback on early microcode loading
that the Linux kernel is doing. Needs implementation in the hypervisor.
c) efi. One needs to use the patches posted by Eric Shelton
which are back-ports of work done by Tang Liang
Daniel Kiper is taking a look at in the summer and try
to do it differently.
d). multi-MSI. Jan posted a patch but that needs to be reworked
in pvops kernel.
e). VCPUOP_register_vcpu_time_memory_area
There was a post in the eons ago to use this under Xen...
There are also bugs, but lets ignore those in this email.
The ones that are now off the list are:
- kexec. This can be now done via a new hypercall. Work is in progress
and should be in Xen 4.4.
- acpi s3. Patches are in v3.11 (Rafael's linux-next branch).
Ben Guthro got Ack from hpa for it.
Am I missing any?
next reply other threads:[~2013-06-05 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 20:19 Konrad Rzeszutek Wilk [this message]
2013-06-06 7:38 ` Linux 3.11 and the future Jan Beulich
2013-06-06 13:07 ` Konrad Rzeszutek Wilk
2013-06-06 13:14 ` Jan Beulich
2013-06-07 13:58 ` Konrad Rzeszutek Wilk
2013-06-07 15:43 ` Jan Beulich
2013-06-07 17:03 ` 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=20130605201909.GA17062@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Benjamin.Guthro@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=stefan.bader@canonical.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).