From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>, David Vrabel <david.vrabel@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
IanJackson <Ian.Jackson@eu.citrix.com>
Subject: Re: [PATCH] have architectures specify the number of PIRQs a hardware domain gets
Date: Thu, 11 Dec 2014 12:07:10 +0000 [thread overview]
Message-ID: <1418299630.10394.28.camel@citrix.com> (raw)
In-Reply-To: <1417791061.22808.68.camel@eu.citrix.com>
On Fri, 2014-12-05 at 14:51 +0000, Ian Campbell wrote:
> On Fri, 2014-12-05 at 14:48 +0000, Jan Beulich wrote:
> > >>> On 05.12.14 at 15:27, <Ian.Campbell@eu.citrix.com> wrote:
> > > On Fri, 2014-12-05 at 13:51 +0000, Jan Beulich wrote:
> > >> #define nr_static_irqs NR_IRQS
> > >> +#define arch_hwdom_irqs(domid) NR_IRQS
> > >
> > > FWIW gic_number_lines() is the ARM equivalent of getting the number of
> > > GSIs.
> > >
> > > *BUT* we don't actually use pirqs on ARM (everything goes via the
> > > virtualised interrupt controller). So maybe we should be setting
> > > nr_pirqs to 0 on ARM. I appreciate you likely want such a patch to come
> > > from an ARM person, so I'm fine with you making this NR_IRQS in the
> > > meantime.
> >
> > Considering Julien also asking for this, I don't mind changing this to
> > zero for ARM. Just let me know which way I can get this ack-ed.
>
> If you are happy to provide a version using zero and Julien wants to
> provide a tested-by then I'm fine with going that way.
Seems like things were more complex than Julien expected here, so I
think changing to zero would be a mistake at this point.
AIUI this patch results in no functional change for ARM, in that dom0
previously saw:
d->nr_pirqs = nr_static_irqs + extra_dom0_irqs;
where nr_static_irqs == NR_IRQS on ARM where now it sees:
When extra_dom0_irqs > 0
nr_static_irqs + extra_dom0_irqs
which is the same as before. Or when extra_dom0_irqs:
arch_hwdom_irqs(domid);
== NR_IRQS
== nr_static_irqs + 0
i.e. no change.
Oh, actually extra_dom0_irqs has changed from a default of 256 to 0, I
don't think NR_IRQS(1024) + 256 made much sense on ARM (which is limited
to 1020 IRQs in h/w anyway), so I don't consider that a problem.
If that's all correct then:
Acked-by: Ian Campbell <ian.campbell@citrix.com>
Also Ack with my REST maintainer hat on for the general principal/common
code.
Ian.
next prev parent reply other threads:[~2014-12-11 12:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-05 13:51 [PATCH] have architectures specify the number of PIRQs a hardware domain gets Jan Beulich
2014-12-05 14:27 ` Ian Campbell
2014-12-05 14:36 ` Julien Grall
2014-12-05 14:42 ` Ian Campbell
2014-12-05 15:25 ` Julien Grall
2014-12-05 15:42 ` Jan Beulich
2014-12-05 16:05 ` Julien Grall
2014-12-05 16:23 ` Jan Beulich
2014-12-05 16:34 ` Stefano Stabellini
2014-12-05 14:48 ` Jan Beulich
2014-12-05 14:51 ` Ian Campbell
2014-12-11 12:07 ` Ian Campbell [this message]
2014-12-11 13:16 ` Jan Beulich
2014-12-05 14:48 ` David Vrabel
2014-12-05 14:54 ` 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=1418299630.10394.28.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@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.