From: Thomas Fjellstrom <tfjellstrom@shaw.ca>
To: kvm@vger.kernel.org
Subject: Re: Status of pci passthrough work?
Date: Sat, 27 Sep 2008 12:01:28 -0600 [thread overview]
Message-ID: <200809271201.28705.tfjellstrom@shaw.ca> (raw)
In-Reply-To: <200809271007.54111.tfjellstrom@shaw.ca>
On Saturday 27 September 2008, Thomas Fjellstrom wrote:
> On Saturday 27 September 2008, Jan C. Bernauer wrote:
> > Thomas Fjellstrom wrote:
> > > How did you manage to pull together those patches? They all seem so
> >
> > old, and
> >
> > > won't likely apply cleanly to git head :(
> >
> > Which patches do you mean? The patches for kvm?
> > There is a nice repository managed by Amit Shah:
> > Linux source:
> > http://git.kernel.org/?p=linux/kernel/git/amit/kvm.git;a=summary
> >
> > kvm-userspace:
> > http://git.kernel.org/?p=linux/kernel/git/amit/kvm-userspace.git;a=summar
> >y
> >
> > I think this compiled without too much problems.
>
> Ah, the pci branches in the main kvm.git tree seemed to be months old, and
> I assumed thats where the code was kept.
>
> > Best regards,
> > Jan
So I've checked out both of those trees and used head, and kvm-userspace is
erroring out:
gcc -I. -I.. -I/root/kvm-amit-userspace/qemu/target-i386 -I/root/kvm-amit-
userspace/qemu -MMD -MT qemu-kvm-x86.o -MP -DNEED_CPU_H -D_GNU_SOURCE -
D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D__user= -I/root/kvm-amit-
userspace/qemu/tcg -I/root/kvm-amit-userspace/qemu/tcg/x86_64 -I/root/kvm-
amit-userspace/qemu/fpu -DHAS_AUDIO -DHAS_AUDIO_CHOICE -I/root/kvm-amit-
userspace/qemu/slirp -I /root/kvm-amit-userspace/qemu/../libkvm -DCONFIG_X86
-Wall -O2 -g -fno-strict-aliasing -m64 -I /root/kvm-amit-
userspace/kernel/include -c -o qemu-kvm-x86.o /root/kvm-amit-
userspace/qemu/qemu-kvm-x86.c
/root/kvm-amit-userspace/qemu/qemu-kvm-x86.c:522: error:
âKVM_FEATURE_CLOCKSOURCEâ undeclared here (not in a function)
/root/kvm-amit-userspace/qemu/qemu-kvm-x86.c:525: error:
âKVM_FEATURE_NOP_IO_DELAYâ undeclared here (not in a function)
/root/kvm-amit-userspace/qemu/qemu-kvm-x86.c:528: error: âKVM_FEATURE_MMU_OPâ
undeclared here (not in a function)
So I'm a little stuck now.
--
Thomas Fjellstrom
tfjellstrom@shaw.ca
next prev parent reply other threads:[~2008-09-27 18:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 2:20 Status of pci passthrough work? Thomas Fjellstrom
2008-09-27 6:43 ` Han, Weidong
2008-09-27 7:12 ` Thomas Fjellstrom
2008-09-27 7:44 ` Han, Weidong
2008-09-27 7:57 ` Thomas Fjellstrom
2008-09-28 7:10 ` Amit Shah
2008-09-29 1:09 ` Thomas Fjellstrom
2008-10-03 6:30 ` Amit Shah
2008-12-15 14:40 ` xming
2008-09-27 12:46 ` Jan C. Bernauer
2008-09-27 15:40 ` Thomas Fjellstrom
2008-09-27 15:55 ` Jan C. Bernauer
2008-09-27 16:07 ` Thomas Fjellstrom
2008-09-27 18:01 ` Thomas Fjellstrom [this message]
2008-09-27 18:26 ` Jan C. Bernauer
2008-09-27 18:33 ` Thomas Fjellstrom
2008-09-27 18:40 ` Jan C. Bernauer
2008-09-27 18:44 ` Thomas Fjellstrom
2008-09-28 4:39 ` Avi Kivity
2008-09-28 7:11 ` Amit Shah
[not found] <194255114.431631229436171339.JavaMail.root@zmail02.collab.prod.int.phx2.redhat.com>
2008-12-16 14:07 ` Amit Shah
2008-12-16 14:38 ` xming
2008-12-16 14:40 ` Amit Shah
2009-05-14 17:08 ` Passera, Pablo R
2009-05-15 11:00 ` Amit Shah
2009-05-15 13:14 ` Passera, Pablo R
2009-05-15 13:38 ` Amit Shah
2009-05-29 17:41 ` Passera, Pablo R
2009-05-30 8:36 ` Amit Shah
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=200809271201.28705.tfjellstrom@shaw.ca \
--to=tfjellstrom@shaw.ca \
--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.