From: Avi Kivity <avi@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: kvm@vger.kernel.org
Subject: Re: BUG: using smp_processor_id() in preemptible
Date: Mon, 29 Jun 2009 13:39:03 +0300 [thread overview]
Message-ID: <4A4899C7.7000604@redhat.com> (raw)
In-Reply-To: <1246271545.7775.40.camel@johannes.local>
On 06/29/2009 01:32 PM, Johannes Berg wrote:
>
>> Do you really have a 100MB kernel?
>>
>
> Hmm. Maybe?
>
> text data bss dec hex filename
> 5635486 5482828 84287488 95405802 5afc6ea vmlinux
> -rwxr-xr-x 1 johannes johannes 86242879 2009-06-29 11:31 vmlinux
> -rwxr-xr-x 1 johannes johannes 83M 2009-06-29 11:31 vmlinux
>
> But that's with complete debug info.
>
debug info is not loaded IIUC. But you have 84MB of BSS, that looks
very broken. Maybe you have a zillion cpus configured, though that
should be dynamic now.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-29 10:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 14:15 BUG: using smp_processor_id() in preemptible Johannes Berg
2009-06-28 14:11 ` Avi Kivity
2009-06-29 8:32 ` Johannes Berg
2009-06-29 9:08 ` Avi Kivity
2009-06-29 9:54 ` Johannes Berg
2009-06-29 9:57 ` Johannes Berg
2009-06-29 10:00 ` Avi Kivity
2009-06-29 10:06 ` Johannes Berg
2009-06-29 10:16 ` Avi Kivity
2009-06-29 10:18 ` Johannes Berg
2009-06-29 10:25 ` Avi Kivity
2009-06-29 10:32 ` Johannes Berg
2009-06-29 10:39 ` Avi Kivity [this message]
2009-06-29 10:55 ` Johannes Berg
2009-06-29 11:38 ` Avi Kivity
2009-06-29 12:03 ` Johannes Berg
2009-06-29 9:59 ` Avi Kivity
2009-06-29 10:00 ` Johannes Berg
2009-06-29 10:04 ` Avi Kivity
2009-06-29 10:04 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2018-01-11 12:31 Ricardo Nabinger Sanchez
2018-01-11 17:14 ` Eric Dumazet
2012-10-24 8:24 Paul Thompson
2012-10-24 22:39 ` Borislav Petkov
2010-05-25 5:57 Artem Bityutskiy
2010-05-25 5:57 ` Artem Bityutskiy
2008-12-08 12:13 Tim Blechmann
2009-01-13 9:44 ` Tim Blechmann
2009-02-20 20:42 ` Paul Gortmaker
2008-08-20 5:34 Aneesh Kumar K.V
2008-08-21 4:17 ` Eric Sandeen
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=4A4899C7.7000604@redhat.com \
--to=avi@redhat.com \
--cc=johannes@sipsolutions.net \
--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.