From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] x86: don't change affinity with interrupt unmasked
Date: Wed, 25 Mar 2015 18:12:17 +0000 [thread overview]
Message-ID: <5512FA81.4000708@citrix.com> (raw)
In-Reply-To: <550C4D62020000780006C258@mail.emea.novell.com>
On 20/03/15 16:40, Jan Beulich wrote:
> With ->startup unmasking the IRQ, setting the affinity afterwards
> without masking the IRQ again is invalid namely for MSI (which can't
> have their affinity updated atomically).
>
> Signed-off-by: Jan Beulich<jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
> ---
> Changing the affinity of non-maskable MSI IRQs seems bogus too
Agreed. Their affinity can clearly only be changed safely by a device
driver which can guarantee that an interrupt will not be generated
during the vulnerable period.
This further implies that Xen can't even safely set an affinity to start
with...
> , but I
> can't immediately see what we can do about this (better than disabling
> affinity changes for them).
If we used interrupt remapping properly (which we don't), we could
update the effective affinity without changing any device configuration,
but this still doesn't provide a solution for the many systems out there
without (functional) interrupt remapping.
~Andrew
next prev parent reply other threads:[~2015-03-25 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 15:40 [PATCH] x86: don't change affinity with interrupt unmasked Jan Beulich
2015-03-23 18:46 ` Konrad Rzeszutek Wilk
2015-03-24 7:46 ` Jan Beulich
2015-03-25 18:12 ` Andrew Cooper [this message]
2015-03-26 8:04 ` Jan Beulich
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=5512FA81.4000708@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.