From: "Andres Lagar-Cavilla" <andres@lagarcavilla.org>
To: Konrad Rzeszutek Wilk <konrad@darnok.org>
Cc: xen-devel@lists.xensource.com, ian.campbell@citrix.com,
adin@gridcentric.ca
Subject: Re: Xen 4.2 TODO List
Date: Mon, 23 Jan 2012 20:52:20 -0800 [thread overview]
Message-ID: <f890bfdfa94240a5e92cd7b8bbd5ce4f.squirrel@webmail.lagarcavilla.org> (raw)
In-Reply-To: <20120124014144.GA23702@andromeda.dapyr.net>
> On Mon, Jan 23, 2012 at 07:03:09AM -0800, Andres Lagar-Cavilla wrote:
>> > Date: Mon, 23 Jan 2012 13:19:05 +0000
>> > From: Ian Campbell <Ian.Campbell@citrix.com>
>> > To: xen-devel <xen-devel@lists.xensource.com>
>> > Subject: [Xen-devel] Xen 4.2 TODO List Update
>> > Message-ID: <1327324745.24561.124.camel@zakaz.uk.xensource.com>
>> > Content-Type: text/plain; charset="UTF-8"
>> >
>> > Newly updated list follows. Please send me corrections (especially
>> > "done"). I've stopped CCing everyone, since I guess it is mostly spam
>> to
>> > the majority.
>> >
>> > hypervisor, blockers:
>> >
>> > * round-up of the closing of the security hole in MSI-X
>> > passthrough (uniformly - i.e. even for Dom0 - disallowing
>> write
>> > access to MSI-X table pages). (Jan Beulich -- more fixes
>> > required than first thought, patches posted)
>> > * domctls / sysctls set up to modify scheduler parameters, like
>> > the credit1 timeslice and schedule rate. (George Dunlap)
>> > * get the interface changes for sharing/paging/mem-events done
>> and
>> > dusted so that 4.2 is a stable API that we hold to. (Tim
>> Deegan,
>> > Andres Lagar-Cavilla et al)
>> > * mem event ring management posted, seems close to going
>> > in.
>> Mem event ring management has gone in, so you can chalk it off the list.
>
> Any progress on the pvops side of this? This is the -EBUSY patches
> right?
Actually, this is something quite different -- making sure that when the
hypervisor needs to kick the pager into action no events get lost.
On the pvops kernel we need to make sure backends wait for that pager to
get things right. And we halted that for a little while, after your
exchanges with Adin by the end of the year. But we'll be back with the
scheduled programming after the short break ;)
Cheers,
Andres
>
prev parent reply other threads:[~2012-01-24 4:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1214.1327325228.1471.xen-devel@lists.xensource.com>
2012-01-23 15:03 ` Xen 4.2 TODO List Andres Lagar-Cavilla
2012-01-24 1:41 ` Konrad Rzeszutek Wilk
2012-01-24 4:52 ` Andres Lagar-Cavilla [this message]
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=f890bfdfa94240a5e92cd7b8bbd5ce4f.squirrel@webmail.lagarcavilla.org \
--to=andres@lagarcavilla.org \
--cc=adin@gridcentric.ca \
--cc=ian.campbell@citrix.com \
--cc=konrad@darnok.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 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).