Received: by 2002:ac0:a679:0:0:0:0:0 with SMTP id p54csp1532308imp; Fri, 22 Feb 2019 05:34:43 -0800 (PST) X-Google-Smtp-Source: AHgI3IaClztYVQ+l8g4HQbt2SZFDItvfzj5TjbJfvQ6Rw2c7h4d8O+H1mW6YX+TutWEBkHfRqFJ2 X-Received: by 2002:a63:43:: with SMTP id 64mr4036906pga.64.1550842483369; Fri, 22 Feb 2019 05:34:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550842483; cv=none; d=google.com; s=arc-20160816; b=IYLhmtssDlDfCfnKOfpuVG+hAgsue0ttryZeY+cj59KL0oVnMJIUBqhwWnhnNCmxjf zi7tVT0deYManp4wMBEw9TOh7NeQJke33hEg9/6DC9ikseXBETx8VRXgjbBU+BsL+yQD lz9mVeZcAI8BTkfcdEDIwZOXRJjBFPeGN+Z217OdrKzYzSaOJ7TQtWGLZhUbC1EU5C3J 8+QX8RrPC6Cabfgn4oKv4fAItC7W55Ml/n2FpiLUuakkgONKkxKtKYteIk9MfQ7YywtX wRVJLHCDfTB2tMBGgvYl2XSwryITjOITU+Ln0N8ugU1gTsdwALqKzEPQn8JJXkh5gsGo zBxw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=7C0kXZTGn80C6p98VWNJ568KY1VXndzJaYMa7j5LLcc=; b=Buutq2jKIGIMYyyn85rQkX0cFFckE9aKBioWgZwrlmbpOuPcVQdhRBS8vQrhjD7Cvz r7DG3weNG+anIxJ6DJS3+bJAnILLXXirQSbtCwoELZOwY15flnXAm9KDeJi2MWuhrc1o wDbNgpyHQRD7ijoQh7RcOFdnse/Io2GGQqEbLKhbLlAe3rmpujmHRXtl1A3+0fq2QOIP ZJ/GhNmy9Z84nH41S3kfiFS1MCRgCnPOZRX/AMwZVnyjVrth8R6P010txapjVw7Jj750 GOg+IwPe/aEnpW6Pkn59f8lgMWdZiCFYESbySsjazvSH8fw9W/HVpsRTHS72xJK+V/yB PW7Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f193si1400528pgc.510.2019.02.22.05.34.23; Fri, 22 Feb 2019 05:34:43 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726380AbfBVNd7 (ORCPT + 99 others); Fri, 22 Feb 2019 08:33:59 -0500 Received: from foss.arm.com ([217.140.101.70]:60924 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726087AbfBVNd7 (ORCPT ); Fri, 22 Feb 2019 08:33:59 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 04380A78; Fri, 22 Feb 2019 05:33:59 -0800 (PST) Received: from [10.1.196.50] (e108454-lin.cambridge.arm.com [10.1.196.50]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 779AC3F690; Fri, 22 Feb 2019 05:33:57 -0800 (PST) Subject: Re: [Xen-devel] xen/evtchn and forced threaded irq To: Oleksandr Andrushchenko , Boris Ostrovsky Cc: Juergen Gross , Stefano Stabellini , Andrew Cooper , "linux-kernel@vger.kernel.org" , Jan Beulich , xen-devel , Dave P Martin References: <5e256d9a-572c-e01e-7706-407f99245b00@arm.com> <20190220000209.GA4091@localhost.localdomain> <21214d47-9c68-e6bf-007a-4047cc2b02f9@oracle.com> <8f7445d7-fa50-f3e9-44f5-cc2aebd020f4@arm.com> <15bc52cb-82d8-4d2c-e5a8-c6ae8de90276@oracle.com> <5df8888a-4a29-fccd-bac2-a9c170244029@arm.com> From: Julien Grall Message-ID: Date: Fri, 22 Feb 2019 13:33:55 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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