From: Mike Wray <mike.wray@hp.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: [RESUBMIT] [PATCH] xen, tools: pincpu use vcpu and cpumap_t
Date: Thu, 05 May 2005 16:49:50 +0100 [thread overview]
Message-ID: <427A409E.2010306@hp.com> (raw)
In-Reply-To: <20050503235807.GB11696@us.ibm.com>
Ryan Harper wrote:
> * Mike Wray <mike.wray@hp.com> [2005-05-03 12:01]:
>
>>Ryan Harper wrote:
>>
>>>Here is an update to the previous pincpu patches. This patch updates
>>>the pincpu dom0op to use a cpumap_t pointer, rather than specifying a
>>>size in the interface. cpumap_t is current typedef'ed to an unsigned
>>>long. xm list -v now truncates the cpumap field to only show the bits
>>>of the map that are relevant. That is, if you have four VCPUS, you will
>>>only see the first four bits of the cpumap.
>>>
>>>This patch compiles against current unstable tree, but I could not test
>>>it as the current unstable tree crashes dom0 when booting domU. I back
>>>ported the patch to 20050420 snapshot and it worked there.
>>>
>>
>>This patch causes the dom0 crash I reported on the current unstable
>>(attached) so it needs fixing before applying.
>
>
> I was not able to recreate dom0 crash with the previous patch against
> current nightly snapshot (20050503). None-the-less addressing some of
> your feedback.
>
> Attached is an updated patch.
> o bumped cpumap_t up to u64, per Ian and Keir
> o Fixed deref of user-space pointer without copy_from_user(), Mike Wray
> o Added put_domain() in ed > MAX_VIRT_CPUS error path, Mike Wray
OK, I'll give it another whirl.
Mike
next prev parent reply other threads:[~2005-05-05 15:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 22:31 [PATCH] xen,tools: pincpu use vcpu and cpumap_t Ryan Harper
2005-04-26 23:14 ` Lars Rasmusson
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-05-11 21:09 Ian Pratt
2005-05-11 21:17 ` Kip Macy
2005-05-13 15:20 ` Mike Wray
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=427A409E.2010306@hp.com \
--to=mike.wray@hp.com \
--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.