From: Avi Kivity <avi@redhat.com>
To: "Daniel Godás" <dgodas@gmail.com>
Cc: KVM List <kvm@vger.kernel.org>
Subject: Re: Fix to issues with kvm.h and g++
Date: Thu, 06 Nov 2008 17:57:54 +0200 [thread overview]
Message-ID: <49131402.3000003@redhat.com> (raw)
In-Reply-To: <e4de053b0811021439p2fba39acge7237ce8779de813@mail.gmail.com>
Daniel Godás wrote:
> Hello,
>
> I am writing a kvm-based emulation framework in c++. When I included
> <linux/kvm.h> I got the following errors:
>
> /usr/include/linux/kvm.h:89: error: 'struct kvm_run::<anonymous
> union>::kvm_io' invalid; an anonymous union can only have non-static
> data members
> /usr/include/linux/kvm.h:230: error: declaration of '__u64
> kvm_dirty_log::<anonymous union>::padding'
> /usr/include/linux/kvm.h:227: error: conflicts with previous
> declaration '__u32 kvm_dirty_log::padding'
> /usr/include/linux/kvm.h:89: error: 'struct kvm_run::<anonymous
> union>::kvm_io' invalid; an anonymous union can only have non-static
> data members
> /usr/include/linux/kvm.h:230: error: declaration of '__u64
> kvm_dirty_log::<anonymous union>::padding'
> /usr/include/linux/kvm.h:227: error: conflicts with previous
> declaration '__u32 kvm_dirty_log::padding'
>
> It looks like nobody uses struct kvm_io nor in kernel or user space.
>
Please move it outside the outer structure, just in case.
> The same happens with the two padding fields. The following patch
> fixes the errors:
>
>
And resend with a signoff and changelog entry.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-11-06 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 22:39 Fix to issues with kvm.h and g++ Daniel Godás
2008-11-06 15:57 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-18 4:23 nathan binkert
2009-03-18 8:49 ` Avi Kivity
2009-03-18 20:19 ` nathan binkert
2009-03-19 9:48 ` 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=49131402.3000003@redhat.com \
--to=avi@redhat.com \
--cc=dgodas@gmail.com \
--cc=kvm@vger.kernel.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.