xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <raistlin@linux.it>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Xen 4.2 Release Plan / TODO
Date: Thu, 12 Apr 2012 12:24:16 +0200	[thread overview]
Message-ID: <1334226256.22289.0.camel@Abyss> (raw)
In-Reply-To: <1334053490.12209.176.camel@dagon.hellion.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 2166 bytes --]

On Tue, 2012-04-10 at 10:24 +0000, Ian Campbell wrote: 
> Lots more DONE this week, still a few big ticket items or items with no
> progress (that I've noticed) please let me know if the status of
> anything has changed.
>
Here I am. :-)

> tools, blockers:
>       * libxl stable API -- we would like 4.2 to define a stable API
>         which downstream's can start to rely on not changing. Aspects of
>         this are:
>               * Safe fork vs. fd handling hooks. Involves API changes
>                 (Ian J, patches posted)
>               * locking/serialization, e.g., for domain creation. As of
>                 now,  nothing is provided for this purpose, and
>                 downstream toolstacks have to put their own mechanisms
>                 in place. E.g., xl uses a fcntl() lock around the whole
>                 process of domain creation. It should OTOH be libxl job
>                 to offer a proper set of hooks --placed at the proper
>                 spots during the domain creation process-- for the
>                 downstreams to fill with the proper callbacks. (Dario
>                 Faggioli)
>                       * Thinking to defer this until 4.3?
>
Here's the point. This was raised for the following main reasons:
1. xl holds a lock during domain creation for way too long
2. checking for free memory in xl when it is Xen that will actually 
    allocate it after a while is prone to races (the classical TOCTTOU 
    condition)

We thought both these things to be addressable by messing around with
locks, but a more careful analysis revealed we can't solve 2. in a sane
enough way by just doing that (i.e., messing with lock, moving it
around, etc.).

That being the case, yes, I think we can move this forward toward 4.3
without much problems, and I propose doing so. Thoughts?

Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)




[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2012-04-12 10:24 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 10:24 Xen 4.2 Release Plan / TODO Ian Campbell
2012-04-12  9:56 ` George Dunlap
2012-04-12 10:24 ` Dario Faggioli [this message]
2012-04-12 11:00   ` Ian Campbell
  -- strict thread matches above, loose matches on Subject: below --
2012-07-02 11:02 Ian Campbell
2012-07-03  7:52 ` Jan Beulich
2012-07-03 10:45   ` Anthony PERARD
2012-07-04 16:42 ` Dario Faggioli
2012-07-04 17:08 ` Roger Pau Monne
2012-07-13  9:55   ` Roger Pau Monne
2012-06-26  8:39 Ian Campbell
2012-06-26 20:31 ` Matt Wilson
2012-06-26 21:09   ` Konrad Rzeszutek Wilk
2012-06-26 22:57     ` Matt Wilson
2012-06-27  8:41       ` Ian Campbell
2012-06-28  8:56       ` Ren, Yongjie
2012-06-27 13:12 ` Jan Beulich
2012-06-27 14:52   ` Ian Campbell
2012-06-27 14:57     ` Jan Beulich
2012-06-27 15:01       ` Ian Campbell
2012-06-27 15:36         ` Jan Beulich
2012-06-28 15:18 ` Tim Deegan
2012-06-20 11:29 Ian Campbell
2012-06-20 11:43 ` Andrew Cooper
2012-06-20 13:07   ` Jan Beulich
2012-06-20 13:19     ` Andrew Cooper
2012-06-20 19:29       ` Andrew Cooper
2012-06-26  8:16         ` Ian Campbell
2012-04-02 10:26 Ian Campbell
2012-04-02 10:39 ` David Vrabel
2012-04-02 10:43   ` Ian Campbell
2012-04-02 11:17 ` George Dunlap
2012-04-02 14:41 ` Stefano Stabellini
2012-04-11 16:11 ` Ian Jackson
2012-04-11 16:13   ` Ian Jackson
2012-04-12  7:42     ` Ian Campbell
2012-04-12  7:35   ` Ian Campbell
2012-04-12  7:59     ` Ian Campbell
2012-04-12 16:37       ` Dan Magenheimer
2012-04-12 16:45         ` Ian Campbell
2012-04-13 15:28           ` Dan Magenheimer
2012-04-13 10:45         ` Ian Jackson
2012-04-13 19:45           ` Dan Magenheimer
2012-04-16 10:16             ` Ian Jackson
2012-04-12  8:16     ` Ian Campbell
2012-04-24 17:52       ` Ian Jackson
2012-03-27  9:34 Ian Campbell
2012-03-27 18:30 ` Shriram Rajagopalan
2012-03-19 10:57 Ian Campbell
2012-03-19 11:25 ` Jan Beulich
2012-03-19 11:33   ` Ian Campbell
2012-03-19 12:02     ` Jan Beulich
2012-03-19 12:13   ` Stefano Stabellini
2012-03-19 12:13 ` George Dunlap
2012-03-19 12:28   ` Ian Campbell
2012-03-20  5:19 ` Matt Wilson
2012-03-20  8:42   ` Ian Campbell
2012-03-22  9:21 ` Ian Campbell
2012-03-22  9:22 ` Ian Campbell
2012-03-22 10:22   ` Stefano Stabellini
2012-03-22  9:35 ` George Dunlap
2012-03-22  9:53   ` Ian Campbell
2012-03-22 10:08     ` George Dunlap
2012-03-22 10:19       ` Ian Campbell
2012-03-22 10:31         ` Keir Fraser
2012-03-22 10:34         ` George Dunlap
2012-03-22 10:38           ` Ian Campbell
2012-03-27  9:33             ` Ian Campbell
2012-03-27 10:19               ` George Dunlap

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=1334226256.22289.0.camel@Abyss \
    --to=raistlin@linux.it \
    --cc=Ian.Campbell@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 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).