From: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Avi Kivity <avi@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>, "hpa@zytor.com" <hpa@zytor.com>
Subject: Re: 2.6.35 hangs on early boot in KVM
Date: Tue, 3 Aug 2010 17:01:05 +0100 [thread overview]
Message-ID: <201008031701.06278.tvrtko.ursulin@sophos.com> (raw)
In-Reply-To: <20100803154901.GF28136@aftab>
On Tuesday 03 Aug 2010 16:49:01 Borislav Petkov wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>
> Date: Tue, Aug 03, 2010 at 11:31:02AM -0400
>
> > > One interesting waning spotted:
> > >
> > > include/config/auto.conf:555:warning: symbol value '-fcall-saved-ecx
> > > -fcall- saved-edx' invalid for ARCH_HWEIGHT_CFLAGS
> >
> > Copying Peter and Borislav, guys please look at the above warning. I am
> > bisecting a non-bootable 2.6.35 under KVM and while I am not there yet,
> > it is close to the hweight commit
> > (cb41838bbc4403f7270a94b93a9a0d9fc9c2e7ea) and I spotted this warning.
>
> That's because you're at a bisection point before the hweight patch but
> your .config already contains the ARCH_HWEIGHT_CFLAGS variable because
> of the previous bisection point which contained the hweight patch.
>
> I think this can be safely ignored.
Yep, bisect pointed to another commit so I continued another part of this
thread. Thanks for the explanation!
Tvrtko
Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United Kingdom.
Company Reg No 2096520. VAT Reg No GB 348 3873 20.
next prev parent reply other threads:[~2010-08-03 16:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 9:28 Tvrtko Ursulin
2010-08-03 9:45 ` Tvrtko Ursulin
2010-08-03 13:53 ` Tvrtko Ursulin
2010-08-03 14:51 ` Avi Kivity
2010-08-03 14:57 ` Tvrtko Ursulin
2010-08-03 15:17 ` Tvrtko Ursulin
2010-08-03 15:31 ` Tvrtko Ursulin
2010-08-03 15:49 ` Borislav Petkov
2010-08-03 16:01 ` Tvrtko Ursulin [this message]
2010-08-03 15:59 ` Tvrtko Ursulin
2010-08-03 20:37 ` Eric W. Biederman
2010-08-04 8:09 ` Tvrtko Ursulin
2010-08-03 20:57 ` Yinghai Lu
2010-08-04 8:18 ` Tvrtko Ursulin
2010-08-04 9:05 ` Yinghai Lu
2010-08-04 9:16 ` Tvrtko Ursulin
2010-08-04 9:19 ` Tvrtko Ursulin
2010-08-04 9:34 ` Yinghai Lu
2010-08-04 9:44 ` Tvrtko Ursulin
2010-08-04 9:36 ` Gleb Natapov
2010-08-04 10:37 ` Eric W. Biederman
2010-08-04 10:46 ` Tvrtko Ursulin
2010-08-04 20:30 ` [PATCH] x86/apic: Map the local apic when parsing the MP table Eric W. Biederman
2010-08-04 21:49 ` Yinghai Lu
2010-08-04 21:58 ` [PATCH 1/2] x86, acpi: merge two register_lapic_address() Yinghai Lu
2010-08-04 22:00 ` [PATCH 2/2] x86: remove early_init_lapic_mapping Yinghai Lu
2010-08-06 0:15 ` [tip:x86/urgent] x86, apic: Map the local apic when parsing the MP table tip-bot for Eric W. Biederman
2010-08-07 0:08 ` Yinghai Lu
2010-08-07 0:15 ` H. Peter Anvin
2010-08-07 0:51 ` Yinghai Lu
2010-08-07 1:08 ` Eric W. Biederman
2010-08-07 1:21 ` H. Peter Anvin
2010-08-07 1:30 ` Yinghai Lu
2010-08-07 2:49 ` Eric W. Biederman
2010-08-03 22:28 2.6.35 hangs on early boot in KVM Donald Parsons
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=201008031701.06278.tvrtko.ursulin@sophos.com \
--to=tvrtko.ursulin@sophos.com \
--cc=avi@redhat.com \
--cc=bp@amd64.org \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®