From: Ryan Harper <ryanh@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] 2nd try: 2/2 VCPU creation and allocation
Date: Wed, 12 Oct 2005 11:15:31 -0500 [thread overview]
Message-ID: <20051012161531.GV17358@us.ibm.com> (raw)
In-Reply-To: <8a1ee1a6fae5f2217438c742318c4d1a@cl.cam.ac.uk>
* Keir Fraser <Keir.Fraser@cl.cam.ac.uk> [2005-10-12 11:05]:
>
> On 11 Oct 2005, at 16:16, Ryan Harper wrote:
>
> >Allocation map.
>
> What does this patch buy us, given that we already support per-vcpu
> maps? If I understand correctly, this adds a per-domain map, which
> seems redundant to me.
I guess not as much as it did before we had build-time vcpu creation. I
can easily translate the allocation map in the configuration file into a
set of pincpu ops before allocating domain memory and achieve the same
effect as the patch does without the changes to the domain structure and
pincpu dom0_op.
I'll resend without the changes to xen.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
prev parent reply other threads:[~2005-10-12 16:15 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 ` [PATCH] 2nd try: " Ryan Harper
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 [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=20051012161531.GV17358@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.