From: Lin Ming <mlin@ss.pku.edu.cn>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen/apic: implement io apic read with hypercall
Date: Fri, 20 Apr 2012 19:13:16 +0800 [thread overview]
Message-ID: <1334920396.2863.16.camel@hp6530s> (raw)
In-Reply-To: <4F913340.4000202@citrix.com>
On Fri, 2012-04-20 at 10:58 +0100, Andrew Cooper wrote:
> On 20/04/12 10:25, Lin Ming wrote:
> > Implements xen_io_apic_read with hypercall, so it returns proper IO-APIC
> > information instead of fabricated one.
> >
> > Signed-off-by: Lin Ming <mlin@ss.pku.edu.cn>
> > ---
> > arch/x86/xen/apic.c | 16 +++++++++++-----
> > 1 files changed, 11 insertions(+), 5 deletions(-)
> >
> > diff --git a/arch/x86/xen/apic.c b/arch/x86/xen/apic.c
> > index aee16ab..f1f392d 100644
> > --- a/arch/x86/xen/apic.c
> > +++ b/arch/x86/xen/apic.c
> > @@ -1,14 +1,20 @@
> > #include <linux/init.h>
> > #include <asm/x86_init.h>
> > +#include <asm/apic.h>
> > +#include <xen/interface/physdev.h>
> > +#include <asm/xen/hypercall.h>
> >
> > unsigned int xen_io_apic_read(unsigned apic, unsigned reg)
> > {
> > - if (reg == 0x1)
> > - return 0x00170020;
> > - else if (reg == 0x0)
> > - return apic << 24;
> > + struct physdev_apic apic_op;
> > + int ret;
> >
> > - return 0xff;
> > + apic_op.apic_physbase = mpc_ioapic_addr(apic);
> > + apic_op.reg = reg;
> > + ret = HYPERVISOR_physdev_op(PHYSDEVOP_apic_read, &apic_op);
> > + if (ret)
> > + return ret;
> > + return apic_op.value;
>
> Hypercall ret errors are negative, yet this function is unsigned. Given
> that the previous function had no possible way to fail, perhaps on error
> you should fake up the values as before.
How about return -1 on error?
The calling function can check -1 for error.
unsigned int ret = apic_read(...);
if (ret == -1)
//handle error.
Thanks,
Lin Ming
next prev parent reply other threads:[~2012-04-20 11:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 9:25 [PATCH] xen/apic: implement io apic read with hypercall Lin Ming
2012-04-20 9:58 ` [Xen-devel] " Andrew Cooper
2012-04-20 11:13 ` Lin Ming [this message]
2012-04-20 12:38 ` Ian Campbell
2012-04-20 12:52 ` Jan Beulich
2012-04-20 12:53 ` Andrew Cooper
2012-04-20 13:12 ` Ian Campbell
2012-04-20 13:20 ` Andrew Cooper
2012-04-20 14:50 ` Lin Ming
2012-04-20 14:59 ` Jan Beulich
2012-04-20 15:06 ` Ian Campbell
2012-04-20 15:39 ` Lin Ming
2012-04-20 16:43 ` Konrad Rzeszutek Wilk
2012-04-20 16:41 ` Konrad Rzeszutek Wilk
2012-04-23 8:42 ` Lin Ming
2012-04-23 15:11 ` Konrad Rzeszutek Wilk
2012-04-24 14:43 ` Lin Ming
2012-04-24 16:23 ` Konrad Rzeszutek Wilk
2012-04-25 10:06 ` Lin Ming
2012-04-26 15:33 ` 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=1334920396.2863.16.camel@hp6530s \
--to=mlin@ss.pku.edu.cn \
--cc=andrew.cooper3@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.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