From: Lin Ming <mlin@ss.pku.edu.cn>
To: linux-kernel@vger.kernel.org
Cc: xen-devel@lists.xensource.com, x86@kernel.org,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Ingo Molnar <mingo@redhat.com>,
Xiantao Zhang <xiantao.zhang@intel.com>
Subject: Re: [RFC PATCH] xen: get correct nr_irqs_gsi value from hypervisor
Date: Tue, 10 Apr 2012 23:16:35 +0800 [thread overview]
Message-ID: <1334070995.5865.135.camel@hp6530s> (raw)
In-Reply-To: <1334069838.5865.130.camel@hp6530s>
On Tue, 2012-04-10 at 22:57 +0800, Lin Ming wrote:
> nr_irqs_gsi is set in probe_nr_irqs_gsi()
> nr_irqs_gsi = gsi_top + NR_IRQS_LEGACY;
>
> gsi_top is set in mp_register_ioapic()
> gsi_top = gsi_cfg->gsi_end + 1;
>
> mp_register_ioapic() calls io_apic_read, which don't have a Xen specific
> version. Actually, io_apic_read() always return -1 on Xen Dom0 kernel.
>
> So currently, nr_irqs_gsi is always wrong on Xen Dom0 kernel.
>
> This patch gets the correct nr_irqs_gsi value from Xen hypervisor with a
> hypercall.
>
> Signed-off-by: Lin Ming <mlin@ss.pku.edu.cn>
> --
> arch/x86/include/asm/io_apic.h | 2 ++
> arch/x86/kernel/apic/io_apic.c | 2 +-
> arch/x86/xen/setup.c | 9 +++++++++
> include/xen/interface/physdev.h | 6 ++++++
> 4 files changed, 18 insertions(+), 1 deletions(-)
>
> (I will send xen hypervisor patch in another mail)\
Here is xen hypervisor side patch:
[RFC PATCH] x86: Add a new physdev_op PHYSDEVOP_nr_irqs_gsi
http://marc.info/?l=xen-devel&m=133407101003891&w=2
Regards,
Lin Ming
next prev parent reply other threads:[~2012-04-10 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 14:57 [RFC PATCH] xen: get correct nr_irqs_gsi value from hypervisor Lin Ming
2012-04-10 15:16 ` Lin Ming [this message]
2012-04-11 13:53 ` [Xen-devel] " Konrad Rzeszutek Wilk
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=1334070995.5865.135.camel@hp6530s \
--to=mlin@ss.pku.edu.cn \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
--cc=xiantao.zhang@intel.com \
/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).