From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Graham, Simon" <Simon.Graham@stratus.com>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir@xensource.com>
Subject: Re: DomU crash during migration when suspending source domain
Date: Thu, 15 Feb 2007 11:52:54 -0800 [thread overview]
Message-ID: <45D4BA16.5010702@goop.org> (raw)
In-Reply-To: <342BAC0A5467384983B586A6B0B3767104A6AA62@EXNA.corp.stratus.com>
Graham, Simon wrote:
> You have a better idea of that than I do - however, it seemed to me that
> a complete fix for the cases where allocation failed would be more
> likely to be accepted than something that only fixes one place.
>
> Another thing to consider -- hitting allocation failures is MUCH more
> likely in the Xen environment when live migration is in use; how often
> is a processor taken down and then restarted outside of live migration?
> However, since live migration can occur when the domain has been up for
> a long time, it's much more likely for the allocation to fail (although
> presumably still somewhat low)...
>
> Excuse my ignorance but what's the process for pushing something like
> this upstream?
In addition to all the things Keir mentioned, the other important thing
is to make sure that your comments at the top of the patch explain 1)
what the problem you're trying to solve is, and 2) how this patch solves
those problems. And a good concise patch subject line helps as well.
See http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt for all the
details.
It seems to me that this patch should be pretty easy to get accepted,
since it is local, a pretty obvious bug, and not Xen-specific. But it
may need some stylistic attention: for one, the kernel style tries to
avoid nesting things in deep if() statements, and an early return or
goto to a comment exit point might be more appropriate.
Andi Kleen <ak@muc.de> is probably the best person to send it to (as
well as cc:ing it linux-kernel).
J
next prev parent reply other threads:[~2007-02-15 19:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 12:45 DomU crash during migration when suspending source domain Graham, Simon
2007-02-15 13:22 ` Keir Fraser
2007-02-15 19:52 ` Jeremy Fitzhardinge [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-15 2:47 Graham, Simon
2007-02-15 8:12 ` Keir Fraser
2007-02-14 13:02 Graham, Simon
2007-02-14 3:42 Graham, Simon
2007-02-14 10:13 ` Keir Fraser
2007-02-14 10:36 ` Keir Fraser
2007-02-14 10:48 ` Keir Fraser
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=45D4BA16.5010702@goop.org \
--to=jeremy@goop.org \
--cc=Simon.Graham@stratus.com \
--cc=keir@xensource.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 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.