Kvm-ia64 Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [patch] allow dynamic sizing the kvm vmm area on ia64
Date: Wed, 04 Feb 2009 10:11:49 +0000	[thread overview]
Message-ID: <498969E5.8070406@sgi.com> (raw)
In-Reply-To: <497F08D5.5050902@sgi.com>

Zhang, Xiantao wrote:
> Hi, Jes
>      I am in holidays these days, sorry for late response.  I think
 > you are saying vm area not vmm area.  In addition,  do you have plan
 > to add the part to dynamicly set the value of kvm_vm_data_shift ?
 > You know, it has no difference with before until this part is ready.
> Maybe we can dynamicly cacluate the value in upspace according to the
> amount of vcups, and transfer it to kernel at the stage of vm
> creation.  Another thing we need to consider is its value should
> follow tlb's page size, otherwise, it may result in other issues. 
> Thanks for your effort! 

Hi Xiantao,

Thanks for taking a look at this. Yes I do plan to add some logic for
setting this from QEMU. Basically what I talked to Hollis about was to
create some KVM_CONTEXT_CREATE or similar ioctl, where one requests a
maximum size of the KVM instance, like maximum possible number of vcpus,
memory etc.

Cheers,
Jes


> Xiantao
> 
> Jes Sorensen wrote:
>> Hi,
>>
>> This patch allows dynamically sizing the vmm area on ia64. I have left
>> it with the same size as we used to have with the constants, but it
>> seems to work going higher. I put in an artificial limit of 64 vcpus
>> for now anyway as scaling wise it doesn't work well going higher
>> anyway..... we'll get there :-)
>>
>> Cheers,
>> Jes


      parent reply	other threads:[~2009-02-04 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 13:15 [patch] allow dynamic sizing the kvm vmm area on ia64 Jes Sorensen
2009-02-04  2:02 ` Zhang, Xiantao
2009-02-04 10:11 ` Jes Sorensen [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=498969E5.8070406@sgi.com \
    --to=jes@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox