From: Florian Manschwetus <florianmanschwetus@gmx.de>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Mark Johnson <johnson.nh@gmail.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0 of 12] backport critical fixes from qemu upstream
Date: Sun, 11 Oct 2009 11:04:24 +0200 [thread overview]
Message-ID: <4AD19F98.6000003@gmx.de> (raw)
In-Reply-To: <19151.16802.657454.713076@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 916 bytes --]
Am 09.10.2009 15:58, schrieb Ian Jackson:
> Mark Johnson writes ("Re: [Xen-devel] [PATCH 0 of 12] backport critical fixes from qemu upstream"):
>> On Mon, Oct 5, 2009 at 9:40 AM, Stefano Stabellini
>> <stefano.stabellini@eu.citrix.com> wrote:
>>> The same should be done to qemu-xen-3.4-testing as well.
>>> Cheers,
>>
>> Are you planning to push these to qemu-xen-3.4-testing soon too?
>
> Yes, but I'm giving it a few days to settle down in qemu-xen-unstable
> first, as that seemed sensible ...
>
> Ian.
Ok, but how much are a few days?
This,
2106 xvm 3 59 0 5700M 3743M sleep 758:48 0.28% qemu-dm
is quite a real showstopper and a big pain in my...
So, sorry but this fix is really a critical one.
Florian
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3686 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-10-11 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 13:40 [PATCH 0 of 12] backport critical fixes from qemu upstream Stefano Stabellini
2009-10-09 12:04 ` Mark Johnson
2009-10-09 13:58 ` Ian Jackson
2009-10-11 9:04 ` Florian Manschwetus [this message]
2009-10-14 19:49 ` Mark Johnson
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=4AD19F98.6000003@gmx.de \
--to=florianmanschwetus@gmx.de \
--cc=Ian.Jackson@eu.citrix.com \
--cc=johnson.nh@gmail.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.