[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFEAcA_=BTXVdkN0WmajxVSjbDrmxc5z65hCbxr=7TqJVsE9EA@mail.gmail.com>
Date: Mon, 6 May 2013 10:14:23 +0100
From: Peter Maydell <peter.maydell@...aro.org>
To: Rusty Russell <rusty@...tcorp.com.au>
Cc: Alexander Graf <agraf@...e.de>,
Pranavkumar Sawargaonkar <pranavkumar@...aro.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linaro-kernel@...ts.linaro.org" <linaro-kernel@...ts.linaro.org>,
"patches@...aro.org" <patches@...aro.org>,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
"kvmarm@...ts.cs.columbia.edu" <kvmarm@...ts.cs.columbia.edu>,
Amit Shah <amit.shah@...hat.com>
Subject: Re: [PATCH 0/2] Early printk support for virtio console devices.
On 6 May 2013 06:11, Rusty Russell <rusty@...tcorp.com.au> wrote:
> Peter Maydell <peter.maydell@...aro.org> writes:
>> To be actually useful we need to also specify something in
>> the device tree to say "here is where you will find your
>> emergency output and what it is".
>
> Hmm, I'm not sure that's true. It looks like it needs:
>
> 1) An enhancment to the vdev->set_config callback to pass through (at
> least) an offset, probably offset and length.
>
> 2) An emerg_write() function ptr which can be called at any time, set by
> virtio_console.c's class_init:
That all looks like sensible QEMU implementation possibilities
but it seems to be a bit of a non-sequitur from "how do we
tell the kernel to actually use this?"
-- PMM
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists