From: Randy Dunlap <rdunlap@xenotime.net>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Avi Kivity <avi@redhat.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
KVM <kvm@vger.kernel.org>,
x86@kernel.org
Subject: Re: linux-next: Tree for June 29 (kvm)
Date: Sun, 01 Jul 2012 09:24:09 -0700 [thread overview]
Message-ID: <4FF079A9.6090405@xenotime.net> (raw)
In-Reply-To: <20120701105643.GA4782@redhat.com>
On 07/01/2012 03:56 AM, Michael S. Tsirkin wrote:
> On Sun, Jul 01, 2012 at 12:49:53PM +0300, Avi Kivity wrote:
>> On 07/01/2012 12:44 PM, Michael S. Tsirkin wrote:
>>> On Sun, Jul 01, 2012 at 12:41:45PM +0300, Avi Kivity wrote:
>>>> On 06/29/2012 09:05 PM, Randy Dunlap wrote:
>>>>> On 06/29/2012 12:53 AM, Stephen Rothwell wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Changes since 20120628:
>>>>>
>>>>>
>>>>>
>>>>> on i386:
>>>>>
>>>>> arch/x86/built-in.o: In function `kvm_guest_apic_eoi_write':
>>>>> kvm.c:(.text+0x3561f): undefined reference to `apic'
>>>>>
>>>>>
>>>>> Full randconfig file is attached.
>>>>
>>>> Michael, please disable pveoi if built with no apic.
>>>
>>> Will do.
>>> How do I tweak config to test this? Any hints?
>>
>> See the original mail, there's a .config there.
>
> This https://lkml.org/lkml/2012/6/29/40 ?
> I don't see a .config there.
It's in https://lkml.org/lkml/2012/6/29/350
>> Basically, i386 UP with
>> IOAPIC disabled.
--
~Randy
prev parent reply other threads:[~2012-07-01 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 7:53 linux-next: Tree for June 29 Stephen Rothwell
2012-06-29 18:05 ` linux-next: Tree for June 29 (kvm) Randy Dunlap
2012-07-01 9:41 ` Avi Kivity
2012-07-01 9:44 ` Michael S. Tsirkin
2012-07-01 9:49 ` Avi Kivity
2012-07-01 10:56 ` Michael S. Tsirkin
2012-07-01 16:24 ` Randy Dunlap [this message]
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=4FF079A9.6090405@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mst@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=x86@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 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).