mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Ross Lagerwall <ross.lagerwall@citrix.com>,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Julien Grall <julien@xen.org>
Subject: Re: [PATCH] xen/events: reset active flag for lateeoi events later
Date: Mon, 5 Jul 2021 11:16:43 +0200	[thread overview]
Message-ID: <f8f83223-061c-84cf-41c6-cc64e8aedfcc@suse.com> (raw)
In-Reply-To: <41f6aeaa-583f-9b00-7789-d8a6f751b49d@citrix.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 806 bytes --]

On 05.07.21 11:00, Ross Lagerwall wrote:
> On 2021-06-23 14:09, Juergen Gross wrote:
>> In order to avoid a race condition for user events when changing
>> cpu affinity reset the active flag only when EOI-ing the event.
>>
>> This is working fine as all user events are lateeoi events. Note that
>> lateeoi_ack_mask_dynirq() is not modified as there is no explicit call
>> to xen_irq_lateeoi() expected later.
>>
>> Reported-by: Julien Grall <julien@xen.org>
>> Fixes: b6622798bc50b62 ("xen/events: avoid handling the same event on two cpus at the same time")
>> Tested-by: Julien Grall <julien@xen.org>
>> Signed-off-by: Juergen Gross <jgross@suse.com>
>> ---
> 
> Hi Juergen,
> 
> Are you planning on backporting this fix to releases <= 5.10?

It is on my todo list. :-)


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3135 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

      reply	other threads:[~2021-07-05  9:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23 13:09 Juergen Gross
2021-06-23 23:18 ` Boris Ostrovsky
2021-07-05  9:00 ` Ross Lagerwall
2021-07-05  9:16   ` Juergen Gross [this message]

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=f8f83223-061c-84cf-41c6-cc64e8aedfcc@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=julien@xen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ross.lagerwall@citrix.com \
    --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®