public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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 14:38:47 +0300	[thread overview]
Message-ID: <4A48A7C7.4060700@redhat.com> (raw)
In-Reply-To: <1246272959.7775.41.camel@johannes.local>

On 06/29/2009 01:55 PM, Johannes Berg wrote:
> I had MAXSMP configured, which makes it 4096, but if I turn off MAXSMP
> and make NR_CPUS 8, then I get
>     text	   data	    bss	   	 dec		    hex	filename
> 5594521	2562924	12726272	20883717	13ea905	vmlinux
>    

12MB bss is still pretty bloated, but I guess that's beyond the scope of 
this thread.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-06-29 11:37 UTC|newest]

Thread overview: 20+ 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
2009-06-29 10:55                         ` Johannes Berg
2009-06-29 11:38                           ` Avi Kivity [this message]
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

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=4A48A7C7.4060700@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox