[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fe44917f-bbe9-3e0e-fdda-2eb4db9f25c2@arm.com>
Date: Fri, 22 Feb 2019 13:33:55 +0000
From: Julien Grall <julien.grall@....com>
To: Oleksandr Andrushchenko <andr2000@...il.com>,
Boris Ostrovsky <boris.ostrovsky@...cle.com>
Cc: Juergen Gross <jgross@...e.com>,
Stefano Stabellini <sstabellini@...nel.org>,
Andrew Cooper <Andrew.Cooper3@...rix.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jan Beulich <JBeulich@...e.com>,
xen-devel <xen-devel@...ts.xenproject.org>,
Dave P Martin <dave.martin@....com>
Subject: Re: [Xen-devel] xen/evtchn and forced threaded irq
Hi,
On 22/02/2019 12:38, Oleksandr Andrushchenko wrote:
> On 2/20/19 10:46 PM, Julien Grall wrote:
>> Discussing with my team, a solution that came up would be to introduce one
>> atomic field per event to record the number of event received. I will explore
>> that solution tomorrow.
> How will this help if events have some payload?
What payload? The event channel does not carry any payload. It only notify you
that something happen. Then this is up to the user to decide what to you with it.
Cheers,
--
Julien Grall
Powered by blists - more mailing lists