From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: Mykyta Poturai <Mykyta_Poturai@epam.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Michal Orzel <michal.orzel@amd.com>
Subject: Re: [PATCH v6 1/5] arm/irq: Keep track of irq affinities
Date: Thu, 19 Mar 2026 01:39:36 +0000 [thread overview]
Message-ID: <871phgk36w.fsf@epam.com> (raw)
In-Reply-To: <877br8k3fy.fsf@epam.com> (Volodymyr Babchuk's message of "Thu, 19 Mar 2026 03:34:09 +0200")
Volodymyr Babchuk <volodymyr_babchuk@epam.com> writes:
> Hi Mykyta,
>
> Mykyta Poturai <Mykyta_Poturai@epam.com> writes:
>
>> Currently on Arm the desc->affinity mask of an irq is never updated,
>> which makes it hard to know the actual affinity of an interrupt.
>
> With this change you'll track affinity of hardware interrupts, but pure
> virtual interrupts still will not be tracked. Is it intended behaviour?
> I believe it should be mentioned in the commit message.
Well, that was blunder :( please disregard this.
--
WBR, Volodymyr
next prev parent reply other threads:[~2026-03-19 1:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 9:39 [PATCH v6 0/5] Implement CPU hotplug on Arm Mykyta Poturai
2026-03-12 9:39 ` [PATCH v6 1/5] arm/irq: Keep track of irq affinities Mykyta Poturai
2026-03-18 8:05 ` Bertrand Marquis
2026-03-19 1:34 ` Volodymyr Babchuk
2026-03-19 1:39 ` Volodymyr Babchuk [this message]
2026-03-12 9:39 ` [PATCH v6 2/5] arm/irq: Migrate IRQs during CPU up/down operations Mykyta Poturai
2026-03-18 8:12 ` Bertrand Marquis
2026-03-12 9:39 ` [PATCH v6 3/5] arm/sysctl: Implement cpu hotplug ops Mykyta Poturai
2026-03-18 8:23 ` Bertrand Marquis
2026-03-23 11:09 ` Jan Beulich
2026-03-27 10:39 ` Mykyta Poturai
2026-03-27 11:40 ` Jan Beulich
2026-03-12 9:39 ` [PATCH v6 4/5] tools: Allow building xen-hptool without CONFIG_MIGRATE Mykyta Poturai
2026-03-12 9:39 ` [PATCH v6 5/5] docs: Document CPU hotplug Mykyta Poturai
2026-03-18 8:28 ` Bertrand Marquis
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=871phgk36w.fsf@epam.com \
--to=volodymyr_babchuk@epam.com \
--cc=Mykyta_Poturai@epam.com \
--cc=bertrand.marquis@arm.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.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 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.