From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ND1We-0002oR-9R for qemu-devel@nongnu.org; Tue, 24 Nov 2009 14:58:12 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ND1WY-0002gV-AF for qemu-devel@nongnu.org; Tue, 24 Nov 2009 14:58:11 -0500 Received: from [199.232.76.173] (port=42012 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ND1WX-0002g9-SE for qemu-devel@nongnu.org; Tue, 24 Nov 2009 14:58:05 -0500 Received: from cantor.suse.de ([195.135.220.2]:33092 helo=mx1.suse.de) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1ND1WX-0000wX-Bw for qemu-devel@nongnu.org; Tue, 24 Nov 2009 14:58:05 -0500 Subject: Re: [Qemu-devel] [PATCH 10/13] Implement early printk in virtio-console Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Alexander Graf In-Reply-To: <4B0C3870.3010203@codemonkey.ws> Date: Tue, 24 Nov 2009 20:58:01 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <4A9A6DF4-5790-4135-88EB-D73F4C57D6EF@suse.de> References: <1259083781-14642-1-git-send-email-agraf@suse.de> <1259083781-14642-11-git-send-email-agraf@suse.de> <4B0C2C24.9060107@codemonkey.ws> <486F7673-73A4-4983-9ACC-3C45BB73BF59@suse.de> <4B0C332E.7020408@codemonkey.ws> <158A814D-A4BB-4F3C-BFC6-8470FB559A1F@suse.de> <4B0C3440.7080406@codemonkey.ws> <06578E67-B7AD-4217-B9F0-FDA753E35412@suse.de> <4B0C3870.3010203@codemonkey.ws> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Carsten Otte , qemu-devel@nongnu.org, Aurelien Jarno On 24.11.2009, at 20:48, Anthony Liguori wrote: > Alexander Graf wrote: >>> Oh, that's bad :-) >>>=20 >>> That should really be it's own character device. We don't really = have a way to connect two character devices like that. Maybe muxing? >>> =20 >>=20 >> So you want me to implement char muxing and a bootloader within a = week? :) >> =20 >=20 > Char muxing is already there. Ah :-). I guess I could also just create a separate console. It's only = for early printk anyways. > Don't know what to do about the bootloader bit. At this point, I'm = curious about whether kboot would be a viable solution. My opinion would be to leave it as is for now and switch to a real = bootloader that runs inside the guest later. Alex=