On Thu, Feb 23, 2017 at 06:45:50PM +0530, Bhupinder Thakur wrote:
> Hi,
>
> Currently, xenconsoled supports only PV console. To support one
> additional pl011 console, some of the data structures in struct domain
> and certain functions such as buffer_append, ring_free_bytes, etc.
> will have to b
Hi,
Currently, xenconsoled supports only PV console. To support one
additional pl011 console, some of the data structures in struct domain
and certain functions such as buffer_append, ring_free_bytes, etc.
will have to be be scaled to support now two types of consoles.
Some changes are required i
On Wed, 15 Feb 2017, Bhupinder Thakur wrote:
> On 15 February 2017 at 13:45, Bhupinder Thakur
> wrote:
> > Hi Stefano,
> >
> > On 14 February 2017 at 03:14, Stefano Stabellini
> > wrote:
> >> On Mon, 13 Feb 2017, Bhupinder Thakur wrote:
> >>> Hi Stefano,
> >>>
> >>> On 9 February 2017 at 05:40,
Hi,
On 15 February 2017 at 13:45, Bhupinder Thakur
wrote:
> Hi Stefano,
>
> On 14 February 2017 at 03:14, Stefano Stabellini
> wrote:
>> On Mon, 13 Feb 2017, Bhupinder Thakur wrote:
>>> Hi Stefano,
>>>
>>> On 9 February 2017 at 05:40, Stefano Stabellini
>>> wrote:
>>> > On Wed, 8 Feb 2017,
Hi Stefano,
On 14 February 2017 at 03:14, Stefano Stabellini wrote:
> On Mon, 13 Feb 2017, Bhupinder Thakur wrote:
>> Hi Stefano,
>>
>> On 9 February 2017 at 05:40, Stefano Stabellini
>> wrote:
>> > On Wed, 8 Feb 2017, Bhupinder Thakur wrote:
>> >> Hi Julien,
>> >>
>> >> On 3 February 2017 at 1
On Mon, 13 Feb 2017, Bhupinder Thakur wrote:
> Hi Stefano,
>
> On 9 February 2017 at 05:40, Stefano Stabellini
> wrote:
> > On Wed, 8 Feb 2017, Bhupinder Thakur wrote:
> >> Hi Julien,
> >>
> >> On 3 February 2017 at 19:38, Julien Grall wrote:
> >> > So if I understand correctly, you don't recei
Hi Stefano,
On 9 February 2017 at 05:40, Stefano Stabellini wrote:
> On Wed, 8 Feb 2017, Bhupinder Thakur wrote:
>> Hi Julien,
>>
>> On 3 February 2017 at 19:38, Julien Grall wrote:
>> > So if I understand correctly, you don't receive anymore output. Correct?
>> > Have you tried to see whether t
On Wed, 8 Feb 2017, Bhupinder Thakur wrote:
> Hi Julien,
>
> On 3 February 2017 at 19:38, Julien Grall wrote:
> > So if I understand correctly, you don't receive anymore output. Correct?
> > Have you tried to see whether the pl011 driver is receiving interrupt or
> > even Linux calling it.
>
> T
Hi Julien,
On 3 February 2017 at 19:38, Julien Grall wrote:
> So if I understand correctly, you don't receive anymore output. Correct?
> Have you tried to see whether the pl011 driver is receiving interrupt or
> even Linux calling it.
The pl011 driver is not receiving the interrupts (I put a
HYP
On Fri, Feb 3, 2017 at 2:53 PM, Bhupinder Thakur
wrote:
> Hi,
>
>>> Hi,
>>>
>>> I have done the changes for emulating pl011 in Xen. Currently, I have
>>> verified the emulation code by manually reading/writing data to
>>> /dev/ttyAMA0 which is the device file for pl011 device. The data is
>>> flow
On 03/02/17 13:53, Bhupinder Thakur wrote:
Hi,
Hi Bhupinder,
Hi,
I have done the changes for emulating pl011 in Xen. Currently, I have
verified the emulation code by manually reading/writing data to
/dev/ttyAMA0 which is the device file for pl011 device. The data is
flowing fine between xe
Hi,
>> Hi,
>>
>> I have done the changes for emulating pl011 in Xen. Currently, I have
>> verified the emulation code by manually reading/writing data to
>> /dev/ttyAMA0 which is the device file for pl011 device. The data is
>> flowing fine between xenconsoled and the guest domain.
>>
>> As a next
On Fri, Jan 27, 2017 at 05:44:15PM +0530, Bhupinder Thakur wrote:
> Hi,
>
> I have done the changes for emulating pl011 in Xen. Currently, I have
> verified the emulation code by manually reading/writing data to
> /dev/ttyAMA0 which is the device file for pl011 device. The data is
> flowing fine b
On Fri, 27 Jan 2017, Bhupinder Thakur wrote:
> Hi,
>
> I have done the changes for emulating pl011 in Xen. Currently, I have
> verified the emulation code by manually reading/writing data to
> /dev/ttyAMA0 which is the device file for pl011 device. The data is
> flowing fine between xenconsoled an
Hi,
I have done the changes for emulating pl011 in Xen. Currently, I have
verified the emulation code by manually reading/writing data to
/dev/ttyAMA0 which is the device file for pl011 device. The data is
flowing fine between xenconsoled and the guest domain.
As a next step, I wanted to use /dev
On Tue, 17 Jan 2017, Julien Grall wrote:
> Hi,
>
> Sorry for the late answer, I am just back from holidays and still catching-up
> with my e-mails.
>
> On 03/01/17 20:08, Stefano Stabellini wrote:
> > On Thu, 29 Dec 2016, Bhupinder Thakur wrote:
> > > On 28 December 2016 at 23:19, Julien Grall w
Hi,
On 06/01/17 21:54, Stefano Stabellini wrote:
On Fri, 6 Jan 2017, Bhupinder Thakur wrote:
Hi,
I am trying to allocate a new SPI VIRQ for sending pl011 interrupt to
the guest OS. Currently Xen does not allow to allocate a SPI VIRQ for
a guest domain. I tried allocating a new SPI VIRQ by call
Hi,
Sorry for the late answer, I am just back from holidays and still
catching-up with my e-mails.
On 03/01/17 20:08, Stefano Stabellini wrote:
On Thu, 29 Dec 2016, Bhupinder Thakur wrote:
On 28 December 2016 at 23:19, Julien Grall wrote:
On 21/12/16 22:12, Stefano Stabellini wrote:
On W
On Tue, 10 Jan 2017, Bhupinder Thakur wrote:
> Hi Stefano,
>
>
>
> On 7 January 2017 at 03:24, Stefano Stabellini wrote:
> > Hello Bhupinder,
> >
> > it is good to hear that you are making progress.
> >
> >
> > On Fri, 6 Jan 2017, Bhupinder Thakur wrote:
> >> Hi,
> >>
> >> I am trying to alloca
Hi Stefano,
On 7 January 2017 at 03:24, Stefano Stabellini wrote:
> Hello Bhupinder,
>
> it is good to hear that you are making progress.
>
>
> On Fri, 6 Jan 2017, Bhupinder Thakur wrote:
>> Hi,
>>
>> I am trying to allocate a new SPI VIRQ for sending pl011 interrupt to
>> the guest OS. Current
Hello Bhupinder,
it is good to hear that you are making progress.
On Fri, 6 Jan 2017, Bhupinder Thakur wrote:
> Hi,
>
> I am trying to allocate a new SPI VIRQ for sending pl011 interrupt to
> the guest OS. Currently Xen does not allow to allocate a SPI VIRQ for
> a guest domain. I tried allocat
Hi,
I am trying to allocate a new SPI VIRQ for sending pl011 interrupt to
the guest OS. Currently Xen does not allow to allocate a SPI VIRQ for
a guest domain. I tried allocating a new SPI VIRQ by calling
vgic_allocate_spi() but it failed as the SPI VIRQ range for the guests
is limited to 0 (vgic_
On Thu, 29 Dec 2016, Bhupinder Thakur wrote:
> On 28 December 2016 at 23:19, Julien Grall wrote:
> > On 21/12/16 22:12, Stefano Stabellini wrote:
> >>
> >> On Wed, 21 Dec 2016, Julien Grall wrote:
> >>>
> >>> On 20/12/2016 20:53, Stefano Stabellini wrote:
>
> On Tue, 20 Dec 2016, Julien
On Wed, 28 Dec 2016, Julien Grall wrote:
> Hi Stefano,
>
> On 21/12/16 22:12, Stefano Stabellini wrote:
> > On Wed, 21 Dec 2016, Julien Grall wrote:
> > > On 20/12/2016 20:53, Stefano Stabellini wrote:
> > > > On Tue, 20 Dec 2016, Julien Grall wrote:
> > > > > On 19/12/2016 21:24, Stefano Stabelli
On 28 December 2016 at 23:19, Julien Grall wrote:
> On 21/12/16 22:12, Stefano Stabellini wrote:
>>
>> On Wed, 21 Dec 2016, Julien Grall wrote:
>>>
>>> On 20/12/2016 20:53, Stefano Stabellini wrote:
On Tue, 20 Dec 2016, Julien Grall wrote:
>
> On 19/12/2016 21:24, Stefano Stabell
On 28/12/16 17:49, Julien Grall wrote:
On 21/12/16 22:12, Stefano Stabellini wrote:
On Wed, 21 Dec 2016, Julien Grall wrote:
On 20/12/2016 20:53, Stefano Stabellini wrote:
On Tue, 20 Dec 2016, Julien Grall wrote:
On 19/12/2016 21:24, Stefano Stabellini wrote:
On Mon, 19 Dec 2016, Christoff
Hi Stefano,
On 21/12/16 22:12, Stefano Stabellini wrote:
On Wed, 21 Dec 2016, Julien Grall wrote:
On 20/12/2016 20:53, Stefano Stabellini wrote:
On Tue, 20 Dec 2016, Julien Grall wrote:
On 19/12/2016 21:24, Stefano Stabellini wrote:
On Mon, 19 Dec 2016, Christoffer Dall wrote:
On Fri, Dec 1
On Wed, 21 Dec 2016, Julien Grall wrote:
> Hi Stefano,
>
> On 20/12/2016 20:53, Stefano Stabellini wrote:
> > On Tue, 20 Dec 2016, Julien Grall wrote:
> > > On 19/12/2016 21:24, Stefano Stabellini wrote:
> > > > On Mon, 19 Dec 2016, Christoffer Dall wrote:
> > > > > On Fri, Dec 16, 2016 at 05:03:1
Hi Stefano,
On 20/12/2016 22:33, Stefano Stabellini wrote:
On Tue, 20 Dec 2016, Christoffer Dall wrote:
On Mon, Dec 19, 2016 at 12:24:18PM -0800, Stefano Stabellini wrote:
On Mon, 19 Dec 2016, Christoffer Dall wrote:
On Fri, Dec 16, 2016 at 05:03:13PM +, Julien Grall wrote:
hvm_param is
Hi Stefano,
On 20/12/2016 20:53, Stefano Stabellini wrote:
On Tue, 20 Dec 2016, Julien Grall wrote:
On 19/12/2016 21:24, Stefano Stabellini wrote:
On Mon, 19 Dec 2016, Christoffer Dall wrote:
On Fri, Dec 16, 2016 at 05:03:13PM +, Julien Grall wrote:
Finally, we cannot hijack one of the g
On Tue, Dec 20, 2016 at 01:33:39PM -0800, Stefano Stabellini wrote:
> On Tue, 20 Dec 2016, Christoffer Dall wrote:
> > Hi Stefano,
> >
> > On Mon, Dec 19, 2016 at 12:24:18PM -0800, Stefano Stabellini wrote:
> > > On Mon, 19 Dec 2016, Christoffer Dall wrote:
> > > > On Fri, Dec 16, 2016 at 05:03:13
On Tue, 20 Dec 2016, Bhupinder Thakur wrote:
> Hi Stefano,
>
> Thanks for a detailed explanation. I have some queries.
>
> > Let me explain how the PV console protocol and drivers work, because
> > they are a bit unusual. The first PV console is advertised via
> > hvm_params. The guest calls:
> >
On Tue, 20 Dec 2016, Christoffer Dall wrote:
> Hi Stefano,
>
> On Mon, Dec 19, 2016 at 12:24:18PM -0800, Stefano Stabellini wrote:
> > On Mon, 19 Dec 2016, Christoffer Dall wrote:
> > > On Fri, Dec 16, 2016 at 05:03:13PM +, Julien Grall wrote:
> > > > (CC rest maintainers for event channel que
On Tue, 20 Dec 2016, Stefano Stabellini wrote:
> On Tue, 20 Dec 2016, Julien Grall wrote:
> > Hi Stefano,
> >
> > On 19/12/2016 21:24, Stefano Stabellini wrote:
> > > On Mon, 19 Dec 2016, Christoffer Dall wrote:
> > > > On Fri, Dec 16, 2016 at 05:03:13PM +, Julien Grall wrote:
> > > > > (CC re
On Tue, 20 Dec 2016, Julien Grall wrote:
> Hi Stefano,
>
> On 19/12/2016 21:24, Stefano Stabellini wrote:
> > On Mon, 19 Dec 2016, Christoffer Dall wrote:
> > > On Fri, Dec 16, 2016 at 05:03:13PM +, Julien Grall wrote:
> > > > (CC rest maintainers for event channel questions)
> > > >
> > > >
Hi Stefano,
On Mon, Dec 19, 2016 at 12:24:18PM -0800, Stefano Stabellini wrote:
> On Mon, 19 Dec 2016, Christoffer Dall wrote:
> > On Fri, Dec 16, 2016 at 05:03:13PM +, Julien Grall wrote:
> > > (CC rest maintainers for event channel questions)
> > >
> > > On 16/12/16 10:06, Bhupinder Thakur
Hi Stefano,
On 19/12/2016 21:24, Stefano Stabellini wrote:
On Mon, 19 Dec 2016, Christoffer Dall wrote:
On Fri, Dec 16, 2016 at 05:03:13PM +, Julien Grall wrote:
(CC rest maintainers for event channel questions)
On 16/12/16 10:06, Bhupinder Thakur wrote:
Hi,
Hi Bhupinder,
The idea is
Hi Stefano,
Thanks for a detailed explanation. I have some queries.
>
> Let me explain how the PV console protocol and drivers work, because
> they are a bit unusual. The first PV console is advertised via
> hvm_params. The guest calls:
>
> hvm_get_parameter(HVM_PARAM_CONSOLE_EVTCHN, &v);
> h
On Mon, 19 Dec 2016, Christoffer Dall wrote:
> On Fri, Dec 16, 2016 at 05:03:13PM +, Julien Grall wrote:
> > (CC rest maintainers for event channel questions)
> >
> > On 16/12/16 10:06, Bhupinder Thakur wrote:
> > >Hi,
> >
> > Hi Bhupinder,
> >
> > >The idea is for Xen to act as an intermedi
On Fri, Dec 16, 2016 at 05:03:13PM +, Julien Grall wrote:
> (CC rest maintainers for event channel questions)
>
> On 16/12/16 10:06, Bhupinder Thakur wrote:
> >Hi,
>
> Hi Bhupinder,
>
> >The idea is for Xen to act as an intermediary as shown below:
> >
> > ring buffers
> >
(CC rest maintainers for event channel questions)
On 16/12/16 10:06, Bhupinder Thakur wrote:
Hi,
Hi Bhupinder,
The idea is for Xen to act as an intermediary as shown below:
ring buffers
rx/tx fifo
dom0 <---> Xen HYP (running pl011 em
Hi,
The idea is for Xen to act as an intermediary as shown below:
ring buffers
rx/tx fifo
dom0 <---> Xen HYP (running pl011 emulation)
<---> domU
event
interrupts
Xen will dir
On Thu, 1 Dec 2016, Christoffer Dall wrote:
> On Wed, Nov 30, 2016 at 02:26:50PM -0800, Stefano Stabellini wrote:
> > On Wed, 30 Nov 2016, Julien Grall wrote:
> > > Hi all,
> > >
> > > Few months ago, Linaro has published the version 2 of the VM specification
> > > [1].
> > >
> > > For those who
Hi Christoffer,
On 30/11/16 16:24, Christoffer Dall wrote:
On Wed, Nov 30, 2016 at 03:29:32PM +, Julien Grall wrote:
Hi all,
Few months ago, Linaro has published the version 2 of the VM
specification [1].
For those who don't know, the specification provides guidelines to
guarantee a compl
On Wed, Nov 30, 2016 at 02:26:50PM -0800, Stefano Stabellini wrote:
> On Wed, 30 Nov 2016, Julien Grall wrote:
> > Hi all,
> >
> > Few months ago, Linaro has published the version 2 of the VM specification
> > [1].
> >
> > For those who don't know, the specification provides guidelines to
> > gu
On Wed, 30 Nov 2016, Julien Grall wrote:
> Hi all,
>
> Few months ago, Linaro has published the version 2 of the VM specification
> [1].
>
> For those who don't know, the specification provides guidelines to guarantee a
> compliant OS images could run on various hypervisor (e.g Xen, KVM).
>
> Lo
Hello Julien,
On 30 November 2016 at 17:29, Julien Grall wrote:
[...]
> I think we can distinct two places where the PL011 could be emulated:
> in the hypervisor, or outside the hypervisor.
>
> Emulating the UART in the hypervisor means that we take the risk to increase
> to the attack surface
On Wed, Nov 30, 2016 at 03:29:32PM +, Julien Grall wrote:
> Hi all,
>
> Few months ago, Linaro has published the version 2 of the VM
> specification [1].
>
> For those who don't know, the specification provides guidelines to
> guarantee a compliant OS images could run on various hypervisor (e
Hi all,
Few months ago, Linaro has published the version 2 of the VM
specification [1].
For those who don't know, the specification provides guidelines to
guarantee a compliant OS images could run on various hypervisor (e.g
Xen, KVM).
Looking at the specification, it will require Xen to ex
49 matches
Mail list logo