All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Wray <mike.wray@hp.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Ryan Harper <ryanh@us.ibm.com>,
	xen-devel@lists.xensource.com, Christian.Limpach@cl.cam.ac.uk
Subject: Re: [RESUBMIT] [PATCH] xen,	tools: pincpu use vcpu and cpumap_t
Date: Fri, 13 May 2005 16:20:46 +0100	[thread overview]
Message-ID: <4284C5CE.5020505@hp.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3F93@liverpoolst.ad.cl.cam.ac.uk>

Ian Pratt wrote:
>  > > >>I'll update it against current unstable and resubmit.  Thanks.
> 
>>>>
>>>>Updated against 2005-05-10 nightly unstable snapshot.
>>>>
>>>
>>>Thanks, I'll apply it.
>>
>>I've applied this already -- but it needs some more changes 
>>like moving the vcpu_to_cpu and cpumap arrays out of 
>>getdomaininfo into the new getvcpucontext, allowing this to 
>>scale beyond MAX_VIRT_CPUS. 
>>Also, I think sparse vcpu allocations aren't handled right 
>>for these two arrays, which moving them to getvcpucontext 
>>will also fix. 
>>Patches for this would be highly appreciated!
> 
> 
> As I recall, I think Mike's tree has some improvements for this patch
> too, in particular moving the conversion from the processor list into a
> bitmap from xm into  xend. Steve's been working to get Mike's stuff
> fully tested and integrated. Hopefully we can get this all merged
> tomorrow.

Yes, I had some fixes, but unstable won't boot for me at the moment
so I'm unable to test them.

Mike

  parent reply	other threads:[~2005-05-13 15:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-11 21:09 [RESUBMIT] [PATCH] xen, tools: pincpu use vcpu and cpumap_t Ian Pratt
2005-05-11 21:17 ` Kip Macy
2005-05-13 15:20 ` Mike Wray [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-26 22:31 [PATCH] xen,tools: " Ryan Harper
2005-05-03 16:51 ` Mike Wray
2005-05-03 23:58   ` [RESUBMIT] [PATCH] xen, tools: " Ryan Harper
2005-05-05 15:49     ` Mike Wray
2005-05-10 13:59     ` Mike Wray
2005-05-10 14:59       ` Ryan Harper
2005-05-10 15:55         ` Ryan Harper
2005-05-11 15:16           ` Mike Wray
2005-05-11 20:30             ` Christian Limpach
2005-05-11 20:41               ` Kip Macy
2005-05-11 21:17                 ` Christian Limpach
2005-05-11 21:18                   ` Kip Macy
2005-05-12 15:16           ` Mike Wray
2005-05-12 16:06             ` Mike Wray
2005-05-12 16:17               ` 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=4284C5CE.5020505@hp.com \
    --to=mike.wray@hp.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=ryanh@us.ibm.com \
    --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.