From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Julien Grall <julien.grall@arm.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Dave P Martin <dave.martin@arm.com>
Subject: Re: [Xen-devel] xen/evtchn and forced threaded irq
Date: Mon, 25 Feb 2019 15:24:24 +0200 [thread overview]
Message-ID: <13a9616c-2d9a-f90b-3358-f2dcadbbb64d@gmail.com> (raw)
In-Reply-To: <fe44917f-bbe9-3e0e-fdda-2eb4db9f25c2@arm.com>
On 2/22/19 3:33 PM, Julien Grall wrote:
> 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.
Sorry, I was probably not precise enough. I mean that an event might have
associated payload in the ring buffer, for example [1]. So, counting events
may help somehow, but the ring's data may still be lost
>
> Cheers,
>
[1]
https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=xen/include/public/io/displif.h;h=cc5de9cb1f35dedc99c866d73d086b19e496852a;hb=HEAD#l756
next prev parent reply other threads:[~2019-02-25 13:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 17:31 Julien Grall
2019-02-20 0:02 ` Boris Ostrovsky
2019-02-20 14:15 ` Julien Grall
2019-02-20 17:07 ` Boris Ostrovsky
2019-02-20 18:05 ` Julien Grall
2019-02-20 20:04 ` Boris Ostrovsky
2019-02-20 20:46 ` Julien Grall
2019-02-20 21:46 ` Boris Ostrovsky
2019-02-20 22:03 ` Julien Grall
2019-02-21 8:07 ` [Xen-devel] " Roger Pau Monné
[not found] ` <CAF3u54Ct7nBjoLw9Vzb=aZVu=N5Ccp5_k6GxLo_ZSA=YCsco6A@mail.gmail.com>
2019-02-21 8:52 ` Juergen Gross
2019-02-21 9:14 ` Roger Pau Monné
2019-02-21 20:46 ` Julien Grall
2020-04-27 23:20 ` Stefano Stabellini
2019-02-22 11:44 ` Jan Beulich
2019-02-22 12:38 ` [Xen-devel] " Oleksandr Andrushchenko
2019-02-22 13:33 ` Julien Grall
2019-02-25 13:24 ` Oleksandr Andrushchenko [this message]
2019-02-25 13:55 ` Julien Grall
2019-02-25 14:08 ` Oleksandr Andrushchenko
2019-02-25 15:26 ` Julien Grall
2019-02-26 9:14 ` Roger Pau Monné
2019-02-26 9:30 ` Andrew Cooper
2019-02-26 9:44 ` Roger Pau Monné
2019-02-26 10:03 ` Julien Grall
2019-02-26 10:17 ` Roger Pau Monné
2019-02-26 10:26 ` Julien Grall
2019-02-26 11:02 ` Roger Pau Monné
2019-02-27 11:09 ` Julien Grall
2019-02-26 9:45 ` Paul Durrant
2019-02-21 8:17 ` Juergen Gross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13a9616c-2d9a-f90b-3358-f2dcadbbb64d@gmail.com \
--to=andr2000@gmail.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dave.martin@arm.com \
--cc=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®