All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: aq <aquynh@gmail.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] enforce dom0 cpus and balloon out memory
Date: Fri, 29 Jul 2005 10:17:20 -0500	[thread overview]
Message-ID: <20050729151720.GF8702@us.ibm.com> (raw)
In-Reply-To: <9cde8bff05072820043a496e14@mail.gmail.com>

* aq <aquynh@gmail.com> [2005-07-29 09:01]:
> This patch does 2 jobs:
> 
> - Enforce the number of CPUs dom0 will take. See the new variable
> "dom0-cpus" in xend-config.sxp (you will want to set this variable to
> 1 on SMP systems)

You could use vcpu-hotplug to drop the extra cpus from dom0 instead of
writing directly into sysfs.  The only stopper to that approach is the
fact that dom0's self.channel is not initialized when xend starts and
subsequently doesn't send the control message.  Channels are initialized
when a domain is built, but since dom0 is built by xen, the routine
which sets up channels isn't called for dom0.  Haven't found a good place
for xend to initialized the channel for dom0 yet either.

See vcpu_hotplug() in xen/xend/XendDomInfo.py

Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

  reply	other threads:[~2005-07-29 15:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29  3:04 [PATCH] enforce dom0 cpus and balloon out memory aq
2005-07-29 15:17 ` Ryan Harper [this message]
2005-07-29 15:24   ` Mark Williamson
2005-07-29 15:43     ` Ryan Harper
  -- strict thread matches above, loose matches on Subject: below --
2005-07-29 17:26 Ian Pratt
2005-07-29 17:50 ` Keir Fraser
2005-07-29 18:26   ` Ryan Harper

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=20050729151720.GF8702@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=aquynh@gmail.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    /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.