 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] [PATCH] xen: increase static dmesg buffer to 64K
| To: | Keir Fraser <keir.xen@xxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] [PATCH] xen: increase static dmesg buffer to 64K |
| From: | Olaf Hering <olaf@xxxxxxxxx> |
| Date: | Mon, 18 Jul 2011 10:45:12 +0200 |
| Cc: | xen-devel@xxxxxxxxxxxxxxxxxxx, Jan Beulich <JBeulich@xxxxxxxxxx> |
| Delivery-date: | Mon, 18 Jul 2011 01:45:55 -0700 |
| Dkim-signature: | v=1; a=rsa-sha1; c=relaxed/relaxed; t=1310978718; l=940; s=domk; d=aepfle.de; h=In-Reply-To:Content-Type:MIME-Version:References:Subject:Cc:To:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=jeetR+5vrL2knhgqkkDrLYLBC+Y=; b=Eyvw0jdsCJLIoG70u3Kd/hS2+E8TAK6L3BOMG6b4iE1PAggdHKCBbFoQcucjs62bfBq hl4XfxP3HM0tfyUpOGc6mgUB8ddGthGIpnF7HHGa6kO8BKrm6P/NZXkTT8epI0+0w9BdM KzZAGJHgeeWwLOQ7+vg1PQN92RwI6a7TXwo= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <CA49AE62.1E119%keir.xen@xxxxxxxxx> |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| References: | <20110718081628.GA22448@xxxxxxxxx> <CA49AE62.1E119%keir.xen@xxxxxxxxx> |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
| User-agent: | Mutt/1.5.21.rev5535 (2011-07-01) |
On Mon, Jul 18, Keir Fraser wrote: > On 18/07/2011 09:16, "Olaf Hering" <olaf@xxxxxxxxx> wrote: > > I think conring_size= should be evaluated very early. Is there a way to > > allocate a range of mfns very early which can then be used for the dmesg > > buffer? > > Are you actually losing messages because you can't allocate the larger > console ring early enough? It seems a bit unlikely, but possible I suppose. Yes, I was booting with conring_size=, but the bulk of messages were already printed at that point. My 80 cpu testbox had 24K in dmesg buffer with my patch. > Anyhow, the normal memory allocator is available plenty early enough. You'd > just need to do the allocation earlier than console_init_postirq(). Sometime > soon after the call to end_boot_allocator() would work nicely. I will put that on my TODO list, and look at your and Jans suggestion to move the dmesg buffer allocation earlier. Olaf _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] [PATCH] xen: increase static dmesg buffer to 64K, Keir Fraser |
|---|---|
| Next by Date: | Re: [Xen-devel] [PATCH] xen: update machine_to_phys_order on resume, Jan Beulich |
| Previous by Thread: | Re: [Xen-devel] [PATCH] xen: increase static dmesg buffer to 64K, Keir Fraser |
| Next by Thread: | [Xen-devel] Failure to create HVM DomU at Xen 4.1 ( kernel 3.0.0-5-generic) Ubuntu 11.10 (alpha 2), Boris Derzhavets |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
