From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>, Daniel Kiper <daniel.kiper@oracle.com>
Cc: Matthew Fioravante <matthew.fioravante@jhuapl.edu>,
Ian Campbell <Ian.Campbell@citrix.com>, Wei Liu <liuw@liuw.name>,
George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jim Fehlig <JFEHLIG@suse.com>,
Anthony PERARD <anthony.perard@citrix.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>,
roger.pau@citrix.com
Subject: Re: Xen 4.3 development update, and stock-taking
Date: Fri, 18 Jan 2013 10:22:16 -0500 [thread overview]
Message-ID: <20130118152216.GC9973@phenom.dumpdata.com> (raw)
In-Reply-To: <50F7CDBF02000078000B6A95@nat28.tlf.novell.com>
On Thu, Jan 17, 2013 at 09:09:03AM +0000, Jan Beulich wrote:
> >>> On 16.01.13 at 18:55, George Dunlap <George.Dunlap@eu.citrix.com> wrote:
> > * Persistent grants for blk (external)
> > owner: roger.pau@citrix
> > status: Initial implementation posted
> > prognosis: ?
>
> I think this went into 3.8-rc.
>
> > * Scalability: 16TiB of RAM
> > owner: jan@suse
> > status: Not started
>
> Patches almost ready to be posted (working fine for "normal"
> mode, but working on simulating the mode we'd be in when
> having this much of memory).
>
> Prognosis: Good.
>
> > * Remove hardcoded mobprobe's in xencommons
> > owner: ?
> > status: ?
> > prognosis: Poor.
>
> This was actually _promised_ to be a temporary hack, so I'd
> consider it a release blocker if nothing at all was done here.
>
> > * Xen EFI boot
> > - Signature checking for dom0 kernel / initrd?
> > status: No owner.
> > prognosis: Probably not for 4.4
>
> This is already in the tree (c/s 26262:b62bd62b2683). Nothing else
> should be necessary on the hypervisor side if the shim is to be used.
>
> But of course pv-ops Linux continues to lack EFI support altogether.
CC-ing Daniel here.
next prev parent reply other threads:[~2013-01-18 15:22 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 17:55 Xen 4.3 development update, and stock-taking George Dunlap
2013-01-16 18:03 ` Matthew Fioravante
2013-01-18 15:19 ` Konrad Rzeszutek Wilk
2013-01-18 21:17 ` Fioravante, Matthew E.
2013-01-16 18:15 ` Wei Liu
2013-01-17 10:50 ` George Dunlap
2013-01-17 9:09 ` Jan Beulich
2013-01-17 11:12 ` George Dunlap
2013-01-17 12:51 ` Jan Beulich
2013-01-17 13:58 ` George Dunlap
2013-01-17 14:15 ` Jan Beulich
2013-01-17 14:32 ` George Dunlap
2013-01-17 15:26 ` Jan Beulich
2013-01-17 15:30 ` Jan Beulich
2013-01-17 15:48 ` George Dunlap
2013-01-17 16:04 ` George Dunlap
2013-01-17 16:20 ` Jan Beulich
2013-01-17 17:22 ` George Dunlap
2013-01-17 16:14 ` Jan Beulich
2013-01-17 16:29 ` George Dunlap
2013-01-17 16:49 ` Jan Beulich
2013-01-17 17:11 ` George Dunlap
2013-01-18 9:35 ` Jan Beulich
2013-01-17 16:43 ` George Dunlap
2013-01-17 17:06 ` Jan Beulich
2013-01-17 16:49 ` George Dunlap
2013-01-18 9:30 ` Jan Beulich
2013-01-18 15:24 ` Konrad Rzeszutek Wilk
2013-01-18 11:20 ` Daniel Kiper
2013-01-21 14:12 ` George Dunlap
2013-01-22 13:53 ` Daniel Kiper
2013-01-22 14:10 ` Jan Beulich
2013-01-18 15:22 ` Konrad Rzeszutek Wilk [this message]
2013-01-17 10:00 ` Roger Pau Monné
2013-01-17 11:22 ` George Dunlap
2013-01-18 9:50 ` Roger Pau Monné
2013-01-18 15:21 ` Konrad Rzeszutek Wilk
2013-01-18 15:33 ` Roger Pau Monné
2013-01-21 15:06 ` George Dunlap
2013-01-17 10:20 ` Olaf Hering
2013-01-17 17:23 ` George Dunlap
2013-01-17 15:54 ` Daniel De Graaf
2013-01-17 15:49 ` George Dunlap
2013-01-18 15:41 ` Konrad Rzeszutek Wilk
2013-01-21 15:04 ` George Dunlap
2013-01-22 17:42 ` Konrad Rzeszutek Wilk
[not found] <mailman.21508.1358358967.1399.xen-devel@lists.xen.org>
2013-01-17 16:07 ` Andres Lagar-Cavilla
-- strict thread matches above, loose matches on Subject: below --
2013-01-22 14:32 Daniel Kiper
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=20130118152216.GC9973@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=JFEHLIG@suse.com \
--cc=anthony.perard@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=liuw@liuw.name \
--cc=matthew.fioravante@jhuapl.edu \
--cc=roger.pau@citrix.com \
--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 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.