From: Boqun Feng <boqun.feng@gmail.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Bjorn Helgaas <bhelgaas@google.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Boqun Feng <boqun.feng@gmail.com>
Subject: [RFC 0/2] irqchip/gic-v3-its: Introduce virtual ITS
Date: Tue, 22 Jun 2021 23:53:11 +0800 [thread overview]
Message-ID: <20210622155313.3819952-1-boqun.feng@gmail.com> (raw)
Hi Marc,
Here is an RFC for supporting platforms having LPI supported but without
ITS. And this is for the virtual PCI support for ARM64 Hyper-V guests.
We currently choose this approach (LPI w/o ITS) because a) it's allowed
for GICv3 and b) ITS may not be a more efficient way to configure LPIs
compared to hypercalls, but we'd like to get feedbacks from the
community.
Besides, patch #1 fixes a bug which I found while I was at it.
Looking forwards to any comment and suggestion!
Regards,
Boqun
Boqun Feng (2):
irqchip/gic-v3-its: Free collections if its domain initialization
fails
irqchip/gic-v3-its: Introduce virtual ITS
drivers/irqchip/irq-gic-v3-its.c | 124 ++++++++++++++++++++++++++++---
1 file changed, 115 insertions(+), 9 deletions(-)
--
2.30.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-06-22 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 15:53 Boqun Feng [this message]
2021-06-22 15:53 ` [RFC 1/2] irqchip/gic-v3-its: Free collections if its domain initialization fails Boqun Feng
2021-06-22 15:53 ` [RFC 2/2] irqchip/gic-v3-its: Introduce virtual ITS Boqun Feng
2021-06-22 17:17 ` Marc Zyngier
2021-06-22 17:32 ` [RFC 0/2] " Marc Zyngier
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=20210622155313.3819952-1-boqun.feng@gmail.com \
--to=boqun.feng@gmail.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=tglx@linutronix.de \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).