All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [patch] cap code_gen_buffer_size on ia64
Date: Wed, 24 Sep 2008 10:58:17 +0000	[thread overview]
Message-ID: <48DA1D49.80108@redhat.com> (raw)
In-Reply-To: <48DA061A.20705@sgi.com>

Jes Sorensen wrote:
> Hi,
>
> This one limits the code_gen_buffer_size on ia64, phys_mem_size/4
> really gets out of hand when you boot say a 64GB guest.
>

ia64 doesn't codegen; why not set it to zero?

(and the phys_ram_size / 4 heuristic is ridiculous; code size doesn't 
scale with guest size)

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


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Jes Sorensen <jes@sgi.com>
Cc: kvm@vger.kernel.org, kvm-ia64@vger.kernel.org
Subject: Re: [patch] cap code_gen_buffer_size on ia64
Date: Wed, 24 Sep 2008 13:58:17 +0300	[thread overview]
Message-ID: <48DA1D49.80108@redhat.com> (raw)
In-Reply-To: <48DA061A.20705@sgi.com>

Jes Sorensen wrote:
> Hi,
>
> This one limits the code_gen_buffer_size on ia64, phys_mem_size/4
> really gets out of hand when you boot say a 64GB guest.
>

ia64 doesn't codegen; why not set it to zero?

(and the phys_ram_size / 4 heuristic is ridiculous; code size doesn't 
scale with guest size)

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


  reply	other threads:[~2008-09-24 10:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24  9:19 [patch] cap code_gen_buffer_size on ia64 Jes Sorensen
2008-09-24  9:19 ` Jes Sorensen
2008-09-24 10:58 ` Avi Kivity [this message]
2008-09-24 10:58   ` Avi Kivity
2008-09-24 11:00 ` Jes Sorensen
2008-09-24 11:00   ` Jes Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2008-09-24 11:28 [patch] do not allocate code_gen buffer " Jes Sorensen
2008-09-24 11:28 ` Jes Sorensen
2008-09-24 11:39 ` Avi Kivity
2008-09-24 11:39   ` Avi Kivity
2008-09-24 11:42 ` Jes Sorensen
2008-09-24 11:42   ` Jes Sorensen
2008-09-24 12:09 ` Avi Kivity
2008-09-24 12:09   ` Avi Kivity
2008-09-24 12:52 ` Jes Sorensen
2008-09-24 12:52   ` Jes Sorensen
2008-09-24 13:09 ` Avi Kivity
2008-09-24 13:09   ` Avi Kivity
2008-09-24 15:33 ` Anthony Liguori
2008-09-24 15:33   ` Anthony Liguori
2008-09-24 15:40 ` Avi Kivity
2008-09-24 15:40   ` Avi Kivity

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=48DA1D49.80108@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm-ia64@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.