Re: [Xen-devel] [PATCH 03/11] xen/arm: vpl011: Refactor evtchn_send in Xen to allow sending events from a xen bound channel

Hi, Now I am using notify_via_xen_event_channel() to send the vpl011 events to dom0. So no changes are required in evtchn_send() and this patch can be dropped. Regards, Bhupinder On 6 March 2017 at 16:42, Bhupinder Thakur wrote: > Hi, > > On 6 March 2017 at 16:24,

Re: [Xen-devel] [PATCH 03/11] xen/arm: vpl011: Refactor evtchn_send in Xen to allow sending events from a xen bound channel

Hi, On 6 March 2017 at 16:24, Jan Beulich wrote: On 06.03.17 at 11:44, wrote: >> On 6 March 2017 at 13:45, Jan Beulich wrote: >> On 05.03.17 at 13:39, wrote: On 02/21/2017 11:26 AM,

Re: [Xen-devel] [PATCH 03/11] xen/arm: vpl011: Refactor evtchn_send in Xen to allow sending events from a xen bound channel

>>> On 06.03.17 at 11:44, wrote: > On 6 March 2017 at 13:45, Jan Beulich wrote: > On 05.03.17 at 13:39, wrote: >>> On 02/21/2017 11:26 AM, Bhupinder Thakur wrote: Breakup evtchn_send() to allow sending events for a

Re: [Xen-devel] [PATCH 03/11] xen/arm: vpl011: Refactor evtchn_send in Xen to allow sending events from a xen bound channel

Hi Jan, On 6 March 2017 at 13:45, Jan Beulich wrote: On 05.03.17 at 13:39, wrote: >> My knowledge is limited for this code. So I've just CCed "The REST" >> maintainers. Please do CC them in the future. > > Indeed. > I will take care of this in the

Re: [Xen-devel] [PATCH 03/11] xen/arm: vpl011: Refactor evtchn_send in Xen to allow sending events from a xen bound channel

>>> On 06.03.17 at 11:16, wrote: > On 4 March 2017 at 02:43, Konrad Rzeszutek Wilk > wrote: >> On Tue, Feb 21, 2017 at 04:56:00PM +0530, Bhupinder Thakur wrote: >>> Breakup evtchn_send() to allow sending events for a Xen bound channel. >>>

Re: [Xen-devel] [PATCH 03/11] xen/arm: vpl011: Refactor evtchn_send in Xen to allow sending events from a xen bound channel

Hi Konrad, On 4 March 2017 at 02:43, Konrad Rzeszutek Wilk wrote: > On Tue, Feb 21, 2017 at 04:56:00PM +0530, Bhupinder Thakur wrote: >> Breakup evtchn_send() to allow sending events for a Xen bound channel. >> Currently, >> there is a check in evtchn_send() i.e.

Re: [Xen-devel] [PATCH 03/11] xen/arm: vpl011: Refactor evtchn_send in Xen to allow sending events from a xen bound channel

>>> On 05.03.17 at 13:39, wrote: > My knowledge is limited for this code. So I've just CCed "The REST" > maintainers. Please do CC them in the future. Indeed. > On 02/21/2017 11:26 AM, Bhupinder Thakur wrote: >> Breakup evtchn_send() to allow sending events for a Xen

Re: [Xen-devel] [PATCH 03/11] xen/arm: vpl011: Refactor evtchn_send in Xen to allow sending events from a xen bound channel

Hi Bhupinder, My knowledge is limited for this code. So I've just CCed "The REST" maintainers. Please do CC them in the future. On 02/21/2017 11:26 AM, Bhupinder Thakur wrote: Breakup evtchn_send() to allow sending events for a Xen bound channel. Currently, there is a check in evtchn_send()

Re: [Xen-devel] [PATCH 03/11] xen/arm: vpl011: Refactor evtchn_send in Xen to allow sending events from a xen bound channel

On Tue, Feb 21, 2017 at 04:56:00PM +0530, Bhupinder Thakur wrote: > Breakup evtchn_send() to allow sending events for a Xen bound channel. > Currently, > there is a check in evtchn_send() i.e. is_consumer_xen() that if the event > channel > is bound to a xen consumer then event generation is not

[Xen-devel] [PATCH 03/11] xen/arm: vpl011: Refactor evtchn_send in Xen to allow sending events from a xen bound channel

Breakup evtchn_send() to allow sending events for a Xen bound channel. Currently, there is a check in evtchn_send() i.e. is_consumer_xen() that if the event channel is bound to a xen consumer then event generation is not allowed for that channel. This check is to disallow a guest from raising