From: Jan Beulich <jbeulich@suse.com>
To: Igor Druzhinin <igor.druzhinin@citrix.com>
Cc: andrew.cooper3@citrix.com, roger.pau@citrix.com, wl@xen.org,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] x86/IRQ: bump max number of guests for a shared IRQ to 31
Date: Wed, 2 Dec 2020 10:25:09 +0100 [thread overview]
Message-ID: <b98d3517-6c9d-6f40-6e28-cde142978143@suse.com> (raw)
In-Reply-To: <1606780777-30718-1-git-send-email-igor.druzhinin@citrix.com>
On 01.12.2020 00:59, Igor Druzhinin wrote:
> 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.
Not sure about this. What is the biggest number you've found on any
system? (I assume the chosen value of 31 has some headroom.)
Instead I'm wondering whether this wouldn't better be a Kconfig
setting (or even command line controllable). There don't look to be
any restrictions on the precise value chosen (i.e. 2**n-1 like is
the case for old and new values here, for whatever reason), so a
simple permitted range of like 4...64 would seem fine to specify.
Whether the default then would want to be 8 (close to the current
7) or higher (around the actually observed maximum) is a different
question.
Jan
next prev parent reply other threads:[~2020-12-02 9:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 23:59 [PATCH] x86/IRQ: bump max number of guests for a shared IRQ to 31 Igor Druzhinin
2020-12-02 9:25 ` Jan Beulich [this message]
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=b98d3517-6c9d-6f40-6e28-cde142978143@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=igor.druzhinin@citrix.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 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).