All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andres Lagar-Cavilla <andres@lagarcavilla.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Vincent Hanquez <Vincent.Hanquez@eu.citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: libxenlight or libxenheavy?
Date: Tue, 01 Dec 2009 09:27:57 -0500	[thread overview]
Message-ID: <4B1527ED.2000903@lagarcavilla.com> (raw)
In-Reply-To: <C73AD222.338A%keir.fraser@eu.citrix.com>

I think 3/14 (8mb slack) is a non-issue because no real memory is 
allocated. Perhaps a confussion due to the patch description.
I'll see what I can do about 7/14 (no dm for pv). Later today. As well 
as Stefano's comments on 1/14 which should allow 2/14 as well
Andres
Keir Fraser wrote:
> Too late. Issues will have to be fixed up in followup patches.
>
>  -- Keir
>
> On 01/12/2009 14:00, "Stefano Stabellini" <Stefano.Stabellini@eu.citrix.com>
> wrote:
>
>   
>> I would not apply also 3/14 and 7/14 because of Vincent's comments.
>>
>> On Tue, 1 Dec 2009, Keir Fraser wrote:
>>     
>>> Applied all but patch 2/14, of the below list. It depended on patch 1/14
>>> which was nacked. All others I list below are applied as of c/s 20538.
>>>
>>>  -- Keir
>>>
>>>       
>
>
>   

  reply	other threads:[~2009-12-01 14:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 19:08 libxenlight or libxenheavy? Andres Lagar-Cavilla
2009-12-01  6:12 ` Vincent Hanquez
2009-12-01  6:35 ` Vincent Hanquez
2009-12-01 11:41   ` Stefano Stabellini
2009-12-01 12:14     ` Keir Fraser
2009-12-01 13:51       ` Keir Fraser
2009-12-01 14:00         ` Stefano Stabellini
2009-12-01 14:01           ` Keir Fraser
2009-12-01 14:27             ` Andres Lagar-Cavilla [this message]
2009-12-01 11:23 ` Stefano Stabellini
2009-12-01 11:24 ` Jean Guyader

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=4B1527ED.2000903@lagarcavilla.com \
    --to=andres@lagarcavilla.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=Vincent.Hanquez@eu.citrix.com \
    --cc=keir.fraser@eu.citrix.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.