From: John Garry <john.garry@huawei.com>
To: Marc Zyngier <maz@kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 0/3] MSI: Track device proxying when allocating MSIs
Date: Mon, 30 Nov 2020 13:14:26 +0000 [thread overview]
Message-ID: <6dec3d43-70bb-6c66-fca6-77e1c2b0cc4f@huawei.com> (raw)
In-Reply-To: <20201129135208.680293-1-maz@kernel.org>
On 29/11/2020 13:52, Marc Zyngier wrote:
> This series aims to plug a gap found with John's "managed interrupts
> for platform devices" series.
>
> We have a couple of cases where we allocate MSIs for a device, but the
> endpoint generating the actual interrupts (let's call it the "logical
> device") isn't the one being seen generating the MSIs (the "effective
> device"):
>
> - PCI devices behind a non transparent bridge
> - Devices attached to a wire-to-MSI bridge
>
> For interrupt infrastructures such as the ITS (where the effective
> device ID is part of the translation), it is important decouple the
> lifetime of the effective device mapping from the interrupt allocation
> on behalf of the logical device. Yes, I have a headache too.
>
> To achieve this split, let's tag the such allocations with a new flag
> that convey the fact that the effective device isn't the logical
> one. This mostly affects the platform-MSI subsystem.
>
> Subsequent patches add handling of this new flag in the GICv3 ITS
> (though there may be scope for something more generic in the case of
> the last patch).
Hi Marc,
Tested-by: John Garry <john.garry@huawei.com>
Thanks!
>
> Marc Zyngier (3):
> platform-msi: Track shared domain allocation
> irqchip/gic-v3-its: Tag ITS device as shared if allocating for a proxy
> device
> irqchip/gic-v3-its: Flag device allocation as proxied if behind a PCI
> bridge
>
> drivers/base/platform-msi.c | 7 +++++++
> drivers/irqchip/irq-gic-v3-its-pci-msi.c | 11 ++++++++---
> drivers/irqchip/irq-gic-v3-its.c | 3 +++
> include/asm-generic/msi.h | 4 ++++
> 4 files changed, 22 insertions(+), 3 deletions(-)
>
prev parent reply other threads:[~2020-11-30 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 13:52 Marc Zyngier
2020-11-29 13:52 ` [PATCH 1/3] platform-msi: Track shared domain allocation Marc Zyngier
2020-12-11 14:58 ` [irqchip: irq/irqchip-next] " irqchip-bot for Marc Zyngier
2020-11-29 13:52 ` [PATCH 2/3] irqchip/gic-v3-its: Tag ITS device as shared if allocating for a proxy device Marc Zyngier
2020-12-11 14:58 ` [irqchip: irq/irqchip-next] " irqchip-bot for Marc Zyngier
2020-11-29 13:52 ` [PATCH 3/3] irqchip/gic-v3-its: Flag device allocation as proxied if behind a PCI bridge Marc Zyngier
2020-12-11 14:58 ` [irqchip: irq/irqchip-next] " irqchip-bot for Marc Zyngier
2020-11-30 13:14 ` John Garry [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=6dec3d43-70bb-6c66-fca6-77e1c2b0cc4f@huawei.com \
--to=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
/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®