From: Ross Lagerwall <ross.lagerwall@citrix.com>
To: Juergen Gross <jgross@suse.com>, <xen-devel@lists.xenproject.org>,
<linux-kernel@vger.kernel.org>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Stefano Stabellini <sstabellini@kernel.org>,
<stable@vger.kernel.org>, Julien Grall <julien@xen.org>
Subject: Re: [PATCH 2/7] xen/events: don't unmask an event channel when an eoi is pending
Date: Mon, 8 Feb 2021 10:15:31 +0000 [thread overview]
Message-ID: <bdf20a87-5b4d-529e-7028-cea3eeef769b@citrix.com> (raw)
In-Reply-To: <20210206104932.29064-3-jgross@suse.com>
On 2021-02-06 10:49, Juergen Gross wrote:
> An event channel should be kept masked when an eoi is pending for it.
> When being migrated to another cpu it might be unmasked, though.
>
> In order to avoid this keep two different flags for each event channel
> to be able to distinguish "normal" masking/unmasking from eoi related
> masking/unmasking. The event channel should only be able to generate
> an interrupt if both flags are cleared.
>
> Cc: stable@vger.kernel.org
> Fixes: 54c9de89895e0a36047 ("xen/events: add a new late EOI evtchn framework")
> Reported-by: Julien Grall <julien@xen.org>
> Signed-off-by: Juergen Gross <jgross@suse.com>
...> +static void lateeoi_ack_dynirq(struct irq_data *data)
> +{
> + struct irq_info *info = info_for_irq(data->irq);
> + evtchn_port_t evtchn = info ? info->evtchn : 0;
> +
> + if (VALID_EVTCHN(evtchn)) {
> + info->eoi_pending = true;
> + mask_evtchn(evtchn);
> + }
> +}
Doesn't this (and the one below) need a call to clear_evtchn() to
actually ack the pending event? Otherwise I can't see what clears
the pending bit.
I tested out this patch but processes using the userspace evtchn device did
not work very well without the clear_evtchn() call.
Ross
> +
> +static void lateeoi_mask_ack_dynirq(struct irq_data *data)
> +{
> + struct irq_info *info = info_for_irq(data->irq);
> + evtchn_port_t evtchn = info ? info->evtchn : 0;
> +
> + if (VALID_EVTCHN(evtchn)) {
> + info->masked = true;
> + info->eoi_pending = true;
> + mask_evtchn(evtchn);
> + }
> +}
> +
next prev parent reply other threads:[~2021-02-08 10:34 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 10:49 [PATCH 0/7] xen/events: bug fixes and some diagnostic aids Juergen Gross
2021-02-06 10:49 ` [PATCH 1/7] xen/events: reset affinity of 2-level event initially Juergen Gross
2021-02-06 11:20 ` Julien Grall
2021-02-06 12:09 ` Jürgen Groß
2021-02-06 12:19 ` Julien Grall
2021-02-06 10:49 ` [PATCH 2/7] xen/events: don't unmask an event channel when an eoi is pending Juergen Gross
2021-02-08 10:06 ` Jan Beulich
2021-02-08 10:21 ` Jürgen Groß
2021-02-08 10:15 ` Ross Lagerwall [this message]
2021-02-06 10:49 ` [PATCH 3/7] xen/events: fix lateeoi irq acknowledgment Juergen Gross
2021-02-06 10:49 ` [PATCH 4/7] xen/events: link interdomain events to associated xenbus device Juergen Gross
2021-02-08 23:26 ` Boris Ostrovsky
2021-02-09 13:55 ` Wei Liu
2021-02-06 10:49 ` [PATCH 5/7] xen/events: add per-xenbus device event statistics and settings Juergen Gross
2021-02-08 23:35 ` Boris Ostrovsky
2021-02-06 10:49 ` [PATCH 6/7] xen/evtch: use smp barriers for user event ring Juergen Gross
2021-02-08 9:38 ` Jan Beulich
2021-02-08 9:41 ` Jürgen Groß
2021-02-08 9:44 ` Andrew Cooper
2021-02-08 9:50 ` Jan Beulich
2021-02-08 10:23 ` Andrew Cooper
2021-02-08 10:25 ` Jürgen Groß
2021-02-08 10:31 ` Andrew Cooper
2021-02-08 10:36 ` Jan Beulich
2021-02-08 10:45 ` Andrew Cooper
2021-02-06 10:49 ` [PATCH 7/7] xen/evtchn: read producer index only once Juergen Gross
2021-02-08 9:48 ` Jan Beulich
2021-02-08 10:41 ` Jürgen Groß
2021-02-08 10:51 ` Jan Beulich
2021-02-08 10:59 ` Jürgen Groß
2021-02-08 11:50 ` Julien Grall
2021-02-08 11:54 ` Jan Beulich
2021-02-08 12:15 ` Jürgen Groß
2021-02-08 12:23 ` Jan Beulich
2021-02-08 12:26 ` Jürgen Groß
2021-02-08 11:40 ` Julien Grall
2021-02-08 11:48 ` Jürgen Groß
2021-02-08 12:03 ` Julien Grall
2021-02-06 18:46 ` [PATCH 0/7] xen/events: bug fixes and some diagnostic aids Julien Grall
2021-02-07 12:58 ` Jürgen Groß
2021-02-08 9:11 ` Julien Grall
2021-02-08 9:41 ` Jürgen Groß
2021-02-08 9:54 ` Julien Grall
2021-02-08 10:22 ` Jürgen Groß
2021-02-08 10:40 ` Julien Grall
2021-02-08 12:14 ` Jürgen Groß
2021-02-08 12:16 ` Julien Grall
2021-02-08 12:31 ` Jürgen Groß
2021-02-08 13:09 ` Julien Grall
2021-02-08 13:58 ` Jürgen Groß
2021-02-08 14:20 ` Julien Grall
2021-02-08 14:35 ` Julien Grall
2021-02-08 14:50 ` Jürgen Groß
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=bdf20a87-5b4d-529e-7028-cea3eeef769b@citrix.com \
--to=ross.lagerwall@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=julien@xen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=stable@vger.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