From: Igor Druzhinin <igor.druzhinin@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: <jbeulich@suse.com>, <andrew.cooper3@citrix.com>,
<roger.pau@citrix.com>, <wl@xen.org>,
Igor Druzhinin <igor.druzhinin@citrix.com>
Subject: [PATCH] x86/IRQ: bump max number of guests for a shared IRQ to 31
Date: Mon, 30 Nov 2020 23:59:37 +0000 [thread overview]
Message-ID: <1606780777-30718-1-git-send-email-igor.druzhinin@citrix.com> (raw)
Current limit of 7 is too restrictive for modern systems where one GSI
could be shared by potentially many PCI INTx sources where each of them
corresponds to a device passed through to its own guest. Some systems do not
apply due dilligence in swizzling INTx links in case e.g. INTA is declared as
interrupt pin for the majority of PCI devices behind a single router,
resulting in overuse of a GSI.
Signed-off-by: Igor Druzhinin <igor.druzhinin@citrix.com>
---
If people think that would make sense - I can rework the array to a list of
domain pointers to avoid the limit.
---
xen/arch/x86/irq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/x86/irq.c b/xen/arch/x86/irq.c
index 8d1f9a9..194f660 100644
--- a/xen/arch/x86/irq.c
+++ b/xen/arch/x86/irq.c
@@ -1028,7 +1028,7 @@ int __init setup_irq(unsigned int irq, unsigned int irqflags,
* HANDLING OF GUEST-BOUND PHYSICAL IRQS
*/
-#define IRQ_MAX_GUESTS 7
+#define IRQ_MAX_GUESTS 31
typedef struct {
u8 nr_guests;
u8 in_flight;
--
2.7.4
next reply other threads:[~2020-12-01 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 23:59 Igor Druzhinin [this message]
2020-12-02 9:25 ` [PATCH] x86/IRQ: bump max number of guests for a shared IRQ to 31 Jan Beulich
2020-12-02 14:53 ` Igor Druzhinin
2020-12-02 15:21 ` Jan Beulich
2020-12-02 16:34 ` Igor Druzhinin
2020-12-03 8:20 ` 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=1606780777-30718-1-git-send-email-igor.druzhinin@citrix.com \
--to=igor.druzhinin@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=wl@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.