From: Avi Kivity <avi@redhat.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
kvm@vger.kernel.org, linux-next@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: linux-next: Tree for July 16 (kvm)
Date: Mon, 18 Jul 2011 11:20:58 +0300 [thread overview]
Message-ID: <4E23ECEA.90803@redhat.com> (raw)
In-Reply-To: <20110716115719.feedaeb2.rdunlap@xenotime.net>
On 07/16/2011 09:57 PM, Randy Dunlap wrote:
> On Sun, 17 Jul 2011 00:08:15 +1000 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > Changes since 20110707:
>
>
> kvmclock.c:(.text+0x2778e): undefined reference to `kvm_disable_steal_time'
>
> Full kernel config file is attached.
>
CONFIG_KVM_CLOCK && !CONFIG_KVM_GUEST.
What to do? Stick a wrmsr_safe() in kvmclock.c? Move kvm_disable
steal_time() inline? what about has_steal_clock?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-07-18 8:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 14:08 linux-next: Tree for July 16 Stephen Rothwell
2011-07-16 14:28 ` Stephen Rothwell
2011-07-16 18:57 ` linux-next: Tree for July 16 (kvm) Randy Dunlap
2011-07-18 8:20 ` Avi Kivity [this message]
2011-07-16 19:03 ` linux-next: Tree for July 16 (acpi/apei) Randy Dunlap
2011-07-16 22:16 ` [PATCH] ACPI: APEI build fix Len Brown
2011-07-16 23:45 ` Randy Dunlap
2011-07-16 19:10 ` linux-next: Tree for July 16 (bcma) Randy Dunlap
2011-07-16 19:14 ` linux-next: Tree for July 16 Arnd Bergmann
2011-07-16 19:14 ` linux-next: Tree for July 16 (net/bnx2x) Randy Dunlap
2011-07-16 20:24 ` Dmitry Kravkov
2011-07-16 20:26 ` David Miller
2011-07-16 20:30 ` Dmitry Kravkov
2011-07-16 20:36 ` David Miller
2011-07-16 21:01 ` Randy Dunlap
2011-07-16 19:17 ` linux-next: Tree for July 16 (tpm) Randy Dunlap
2011-07-16 19:25 ` [PATCH -next] watchdog: hpwdt depends on PCI Randy Dunlap
2011-07-18 16:40 ` Mingarelli, Thomas
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=4E23ECEA.90803@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).