From: Ryan Harper <ryanh@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: [PATCH] 2nd try: 0/2 VCPU creation and allocation
Date: Tue, 11 Oct 2005 10:13:42 -0500 [thread overview]
Message-ID: <20051011151342.GR17358@us.ibm.com> (raw)
In-Reply-To: <e03426a13ac8e7d1aa04b6d34258d661@cl.cam.ac.uk>
* Keir Fraser <Keir.Fraser@cl.cam.ac.uk> [2005-10-10 11:34]:
>
> On 10 Oct 2005, at 17:23, Ryan Harper wrote:
>
> >OK, that makes sense. I'll turn VCPUOP_create into set_max_vcpus(max)
> >which will create vcpus 1-(max-1). Any preference on the hypercall
> >name? Does set_max_vcpus() still make sense if it is also creating
> >vcpus?
> >
> >How about DOM0_CREATEVCPUS and
> > do_createvcpus(struct domain* d, unsigned int max_vcpus).
>
> I'm not fussed. I guess I have a slight preference for the latter
> (createvcpus).
The first patch creates a new dom0_op, DOM0_VCPUSINCREASE, which will
create VCPU 1 to (limit-1) in the target domain. The max_vcpus value is
gone as is the VCPUOP_create.
The second patch is the same as before.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
next prev parent reply other threads:[~2005-10-11 15:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 15:16 [PATCH] 0/2 VCPU creation and allocation Ryan Harper
2005-10-10 15:29 ` Keir Fraser
2005-10-10 15:28 ` Ryan Harper
2005-10-10 16:01 ` Keir Fraser
2005-10-10 16:05 ` Ryan Harper
2005-10-10 16:17 ` Keir Fraser
2005-10-10 16:23 ` Ryan Harper
2005-10-10 16:39 ` Keir Fraser
2005-10-11 15:13 ` Ryan Harper [this message]
2005-10-11 15:15 ` [PATCH] 2nd try: 1/2 " Ryan Harper
2005-10-11 15:16 ` [PATCH] 2nd try: 2/2 " Ryan Harper
2005-10-12 16:10 ` Keir Fraser
2005-10-12 16:15 ` 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=20051011151342.GR17358@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=Keir.Fraser@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.