From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2168011 ] kvm_host.h:128: error: field 'mmu_notifier' has incomplete
Date: Mon, 15 Dec 2008 18:00:17 +0000 [thread overview]
Message-ID: <E1LCHjt-0000FS-84@b55xhf1.ch3.sourceforge.com> (raw)
Bugs item #2168011, was opened at 2008-10-15 11:53
Message generated for change (Comment added) made by wg1
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2168011&group_id=180599
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Stephane Bakhos (nuitari3)
Assigned to: Nobody/Anonymous (nobody)
Summary: kvm_host.h:128: error: field 'mmu_notifier' has incomplete
Initial Comment:
When compiling kvm-77/76 on a 2.6.27 kernel with AMD IOMMU activated I get:
kvm_host.h:128: error: field 'mmu_notifier' has incomplete type
----------------------------------------------------------------------
Comment By: Wolfram Gloger (wg1)
Date: 2008-12-15 19:00
Message:
I'm seeing this too, with kvm-79 and now kvm-81 on Linux-2.6.27.7 and
Linux-2.6.27.9.
I'm surprised that such a FTBS is not more prevalent..
For now, I have helped myself with the attached patch.
----------------------------------------------------------------------
Comment By: Stephane Bakhos (nuitari3)
Date: 2008-10-15 16:18
Message:
It looks like I was wrong in saying that AMD IOMMU was the cause. When I
complied again I used make -j5 and it looks like it just skipped the kernel
modules.
----------------------------------------------------------------------
Comment By: Stephane Bakhos (nuitari3)
Date: 2008-10-15 12:11
Message:
It looks like I was wrong in saying that AMD IOMMU was the cause. When I
complied again I used make -j5 and it looks like it just skipped the kernel
modules.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2168011&group_id=180599
next reply other threads:[~2008-12-15 18:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 18:00 SourceForge.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-02 2:34 [ kvm-Bugs-2168011 ] kvm_host.h:128: error: field 'mmu_notifier' has incomplete SourceForge.net
2008-12-25 10:21 SourceForge.net
2008-12-24 16:27 SourceForge.net
2008-12-24 15:53 SourceForge.net
2008-12-24 13:49 SourceForge.net
2008-12-15 18:11 SourceForge.net
2008-10-15 14:18 SourceForge.net
2008-10-15 10:11 SourceForge.net
2008-10-15 9:53 SourceForge.net
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=E1LCHjt-0000FS-84@b55xhf1.ch3.sourceforge.com \
--to=noreply@sourceforge.net \
/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