From: Avi Kivity <avi@qumranet.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: kvm-devel@lists.sourceforge.net, Tony Luck <tony.luck@intel.com>,
kvm-ia64-devel@lists.sourceforge.net
Subject: Re: [PATCH] Build fix for kvm/ia64 userspace.
Date: Wed, 07 May 2008 11:00:02 +0300 [thread overview]
Message-ID: <48216182.8040303@qumranet.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC012295A4@pdsmsx415.ccr.corp.intel.com>
Zhang, Xiantao wrote:
>>> #include <asm/types.h>
>>> +
>>> +#ifdef __KERNEL__
>>> #include <asm/fpu.h>
>>> +#else
>>> +#include <signal.h>
>>> +#endif
>>>
>>>
>> Fishy. A kernel header including a userspace header?
>>
>> Maybe you need to include <linux/signal.h> unconditionally?
>>
> Hi, Avi
> You know, kvm.h is shared by userspace and kernel. But
> unfortunately, the usersapce header files have redefinition for one
> strucutre (structure ia64_fpreg) {One in asm/fpu.h and the other one in
> bits/sigcontext}, maybe a bug here.
> Therefore, if userspace code includes fpu.h and sigcontext.h in
> one source file, it will complain the redefinition. Do you have good
> idea to cope with this issue ?
One way would be to define a new kvm_ia64_fpreg and use that. Seems
that the standard ia64_fpreg is unusable in userspace due to the issue
you mentioned.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-05-07 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 5:12 [PATCH] Build fix for kvm/ia64 userspace Zhang, Xiantao
2008-05-06 14:41 ` Avi Kivity
2008-05-07 6:23 ` Zhang, Xiantao
2008-05-07 8:00 ` Avi Kivity [this message]
2008-05-07 10:30 ` Zhang, Xiantao
2008-05-07 11:07 ` Avi Kivity
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=48216182.8040303@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=kvm-ia64-devel@lists.sourceforge.net \
--cc=tony.luck@intel.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 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.