On 22 April 2013 10:45, Rusty Russell wrote:
> Anup Patel writes:
>> On 22 April 2013 06:51, Rusty Russell wrote:
>>>
>>> Pranavkumar Sawargaonkar writes:
>>> > On 18 April 2013 12:21, Rusty Russell wrote:
>>> >>
>>> >> PranavkumarSawargaonkar writes:
>>> >> > From: Pranavkumar Sawargaonkar
On 22.04.2013, at 05:10, Anup Patel wrote:
> On 22 April 2013 06:51, Rusty Russell wrote:
>>
>> Pranavkumar Sawargaonkar writes:
>>> On 18 April 2013 12:21, Rusty Russell wrote:
PranavkumarSawargaonkar writes:
> From: Pranavkumar Sawargaonkar
>
> This patch implement
Anup Patel writes:
> On 22 April 2013 06:51, Rusty Russell wrote:
>>
>> Pranavkumar Sawargaonkar writes:
>> > On 18 April 2013 12:21, Rusty Russell wrote:
>> >>
>> >> PranavkumarSawargaonkar writes:
>> >> > From: Pranavkumar Sawargaonkar
>> >> >
>> >> > This patch implements early printk supp
On 22 April 2013 06:51, Rusty Russell wrote:
>
> Pranavkumar Sawargaonkar writes:
> > On 18 April 2013 12:21, Rusty Russell wrote:
> >>
> >> PranavkumarSawargaonkar writes:
> >> > From: Pranavkumar Sawargaonkar
> >> >
> >> > This patch implements early printk support for virtio-mmio console
>
Pranavkumar Sawargaonkar writes:
> On 18 April 2013 12:21, Rusty Russell wrote:
>>
>> PranavkumarSawargaonkar writes:
>> > From: Pranavkumar Sawargaonkar
>> >
>> > This patch implements early printk support for virtio-mmio console devices
>> > without using any hypercalls.
>>
>> This makes som
On 19 April 2013 18:14, Catalin Marinas wrote:
> On Fri, Apr 19, 2013 at 05:33:18PM +0100, Peter Maydell wrote:
>> The command line lives in the DTB anyway so if you can't look
>> in the DTB you can't get at earlyprintk config either way.
>
> Linux indeed looks in the DT for the command line and t
On Fri, Apr 19, 2013 at 05:33:18PM +0100, Peter Maydell wrote:
> On 19 April 2013 17:22, Catalin Marinas wrote:
> > earlyprintk is used for debugging early problems, like DT parsing. You
> > don't have to use it unless you are debugging something. Without
> > earlyprintk you just get a normal cons
On 19 April 2013 17:22, Catalin Marinas wrote:
> earlyprintk is used for debugging early problems, like DT parsing. You
> don't have to use it unless you are debugging something. Without
> earlyprintk you just get a normal console during boot, based on the DT
> description.
The command line lives
On Fri, Apr 19, 2013 at 05:14:36PM +0100, Peter Maydell wrote:
> On 19 April 2013 17:12, Catalin Marinas wrote:
> > On Fri, Apr 19, 2013 at 11:05:47AM +0100, Peter Maydell wrote:
> >> Please make the kernel pick the device out of the device tree
> >> blob. The whole point of device tree is that it
On 19 April 2013 17:12, Catalin Marinas wrote:
> On Fri, Apr 19, 2013 at 11:05:47AM +0100, Peter Maydell wrote:
>> Please make the kernel pick the device out of the device tree
>> blob. The whole point of device tree is that it's how to tell
>> the kernel where things live -- making kvmtool/QEMU a
On Fri, Apr 19, 2013 at 11:05:47AM +0100, Peter Maydell wrote:
> On 19 April 2013 10:39, Will Deacon wrote:
> > The point of mach-virt is that it is completely parameterised. So, if you're
> > not emulating an 8250, then don't tell the kernel that you have one!
> > Similarly, if you *do* emulate i
On 19 April 2013 10:39, Will Deacon wrote:
> The point of mach-virt is that it is completely parameterised. So, if you're
> not emulating an 8250, then don't tell the kernel that you have one!
> Similarly, if you *do* emulate it, then either create a device-tree node for
> it or pass the appropria
On Fri, Apr 19, 2013 at 10:34:56AM +0100, Pranavkumar Sawargaonkar wrote:
> On 19 April 2013 15:00, Peter Maydell wrote:
> > On 19 April 2013 10:27, Will Deacon wrote:
> >> On Fri, Apr 19, 2013 at 10:25:35AM +0100, Pranavkumar Sawargaonkar wrote:
> >>> I am not against using 8250 emulation (as fa
On Fri, Apr 19, 2013 at 10:30:40AM +0100, Peter Maydell wrote:
> On 19 April 2013 10:27, Will Deacon wrote:
> > On Fri, Apr 19, 2013 at 10:25:35AM +0100, Pranavkumar Sawargaonkar wrote:
> >> I am not against using 8250 emulation (as far as it solves printk
> >> issues for kernel booting logs), but
On 19 April 2013 15:00, Peter Maydell wrote:
> On 19 April 2013 10:27, Will Deacon wrote:
>> On Fri, Apr 19, 2013 at 10:25:35AM +0100, Pranavkumar Sawargaonkar wrote:
>>> I am not against using 8250 emulation (as far as it solves printk
>>> issues for kernel booting logs), but my point is why not
On 19 April 2013 10:27, Will Deacon wrote:
> On Fri, Apr 19, 2013 at 10:25:35AM +0100, Pranavkumar Sawargaonkar wrote:
>> I am not against using 8250 emulation (as far as it solves printk
>> issues for kernel booting logs), but my point is why not to add early
>> read-write support for virtio cons
On Fri, Apr 19, 2013 at 10:25:35AM +0100, Pranavkumar Sawargaonkar wrote:
> On 19 April 2013 14:35, Will Deacon wrote:
> > On Thu, Apr 18, 2013 at 09:48:49AM +0100, Pranavkumar Sawargaonkar wrote:
> >> Actually i thought adding a config register will be easier to add a
> >> code than writing entir
Hi Will,
On 19 April 2013 14:35, Will Deacon wrote:
> Hello,
>
> On Thu, Apr 18, 2013 at 09:48:49AM +0100, Pranavkumar Sawargaonkar wrote:
>> Actually i thought adding a config register will be easier to add a
>> code than writing entire emulation as 8250 emulation will require to
>> deal with dea
Hello,
On Thu, Apr 18, 2013 at 09:48:49AM +0100, Pranavkumar Sawargaonkar wrote:
> Actually i thought adding a config register will be easier to add a
> code than writing entire emulation as 8250 emulation will require to
> deal with dealing with more registers and more code.
kvmtool already has
On 18 April 2013 13:06, Marc Zyngier wrote:
> On Thu, 18 Apr 2013 12:47:18 +0530, Pranavkumar Sawargaonkar
> wrote:
>> Hi Marc,
>>
>> On 18 April 2013 12:19, Marc Zyngier wrote:
>>
>>> Hi Pranavkumar,
>>>
>>> On Thu, 18 Apr 2013 11:22:24 +0530, PranavkumarSawargaonkar
>>> wrote:
>>> > From: Pra
On 18 April 2013 21:29, Marc Zyngier wrote:
> On Thu, 18 Apr 2013 11:25:56 -0400, Christopher Covington
> wrote:
>> Hi Pranavkumar,
>>
>> On 04/18/2013 01:52 AM, PranavkumarSawargaonkar wrote:
>>> From: Pranavkumar Sawargaonkar
>>>
>>> This patch implements early printk support for virtio-mmio c
On Thu, 18 Apr 2013 11:25:56 -0400, Christopher Covington
wrote:
> Hi Pranavkumar,
>
> On 04/18/2013 01:52 AM, PranavkumarSawargaonkar wrote:
>> From: Pranavkumar Sawargaonkar
>>
>> This patch implements early printk support for virtio-mmio console
>> devices
>> without using any hypercalls.
>
Hi Pranavkumar,
On 04/18/2013 01:52 AM, PranavkumarSawargaonkar wrote:
> From: Pranavkumar Sawargaonkar
>
> This patch implements early printk support for virtio-mmio console devices
> without using any hypercalls.
Is it possible that using DCC might be an easier solution?
[...]
Regards,
Chr
On 13:02 Thu 18 Apr , Pranavkumar Sawargaonkar wrote:
> On 18 April 2013 12:21, Rusty Russell wrote:
> >
> > PranavkumarSawargaonkar writes:
> > > From: Pranavkumar Sawargaonkar
> > >
> > > This patch implements early printk support for virtio-mmio console
> > > devices without using any hy
Hi,
On 18 April 2013 14:14, Alexander Graf wrote:
>
>
> Am 18.04.2013 um 09:32 schrieb Pranavkumar Sawargaonkar
> :
>
>> On 18 April 2013 12:21, Rusty Russell wrote:
>>>
>>> PranavkumarSawargaonkar writes:
From: Pranavkumar Sawargaonkar
This patch implements early printk suppor
Am 18.04.2013 um 10:48 schrieb Pranavkumar Sawargaonkar
:
> Hi Marc,
>
> On 18 April 2013 13:06, Marc Zyngier wrote:
>> On Thu, 18 Apr 2013 12:47:18 +0530, Pranavkumar Sawargaonkar
>> wrote:
>>> Hi Marc,
>>>
>>> On 18 April 2013 12:19, Marc Zyngier wrote:
>>>
Hi Pranavkumar,
>>
On Thu, 18 Apr 2013 09:30:52 +0100, Peter Maydell
wrote:
> On 18 April 2013 07:49, Marc Zyngier wrote:
>> If you need an early console, why not simply wire the 8250 emulation in
>> kvmtool to be useable from the MMIO bus? I reckon this would solve your
>> problem in a more elegant way...
>
> The
Am 18.04.2013 um 10:30 schrieb Peter Maydell :
> On 18 April 2013 07:49, Marc Zyngier wrote:
>> If you need an early console, why not simply wire the 8250 emulation in
>> kvmtool to be useable from the MMIO bus? I reckon this would solve your
>> problem in a more elegant way...
>
> The other a
Hi Marc,
On 18 April 2013 13:06, Marc Zyngier wrote:
> On Thu, 18 Apr 2013 12:47:18 +0530, Pranavkumar Sawargaonkar
> wrote:
>> Hi Marc,
>>
>> On 18 April 2013 12:19, Marc Zyngier wrote:
>>
>>> Hi Pranavkumar,
>>>
>>> On Thu, 18 Apr 2013 11:22:24 +0530, PranavkumarSawargaonkar
>>> wrote:
>>> >
Am 18.04.2013 um 09:32 schrieb Pranavkumar Sawargaonkar
:
> On 18 April 2013 12:21, Rusty Russell wrote:
>>
>> PranavkumarSawargaonkar writes:
>>> From: Pranavkumar Sawargaonkar
>>>
>>> This patch implements early printk support for virtio-mmio console devices
>>> without using any hyperc
On 18 April 2013 07:49, Marc Zyngier wrote:
> If you need an early console, why not simply wire the 8250 emulation in
> kvmtool to be useable from the MMIO bus? I reckon this would solve your
> problem in a more elegant way...
The other approach I thought of would be something involving
defining
On Thu, 18 Apr 2013 12:47:18 +0530, Pranavkumar Sawargaonkar
wrote:
> Hi Marc,
>
> On 18 April 2013 12:19, Marc Zyngier wrote:
>
>> Hi Pranavkumar,
>>
>> On Thu, 18 Apr 2013 11:22:24 +0530, PranavkumarSawargaonkar
>> wrote:
>> > From: Pranavkumar Sawargaonkar
>> >
>> > This patch implements e
On 18 April 2013 12:21, Rusty Russell wrote:
>
> PranavkumarSawargaonkar writes:
> > From: Pranavkumar Sawargaonkar
> >
> > This patch implements early printk support for virtio-mmio console devices
> > without using any hypercalls.
>
> This makes some sense, though not sure that early console
Hi Marc,
On 18 April 2013 12:19, Marc Zyngier wrote:
> Hi Pranavkumar,
>
> On Thu, 18 Apr 2013 11:22:24 +0530, PranavkumarSawargaonkar
> wrote:
>> From: Pranavkumar Sawargaonkar
>>
>> This patch implements early printk support for virtio-mmio console
> devices
>> without using any hypercalls.
>
Hi Pranavkumar,
On Thu, 18 Apr 2013 11:22:24 +0530, PranavkumarSawargaonkar
wrote:
> From: Pranavkumar Sawargaonkar
>
> This patch implements early printk support for virtio-mmio console
devices
> without using any hypercalls.
>
> The current virtio early printk code in kernel expects that hyp
PranavkumarSawargaonkar writes:
> From: Pranavkumar Sawargaonkar
>
> This patch implements early printk support for virtio-mmio console devices
> without using any hypercalls.
This makes some sense, though not sure that early console *read* makes
much sense. I can see the PCI version of this b
From: Pranavkumar Sawargaonkar
This patch implements early printk support for virtio-mmio console devices
without using any hypercalls.
The current virtio early printk code in kernel expects that hypervisor will
provide some mechanism generally a hypercall to support early printk. This
patch
37 matches
Mail list logo
