From: Ryan Harper <ryanh@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: [Xen-changelog] Create new vcpu_op() hypercall. Replaces old boot_vcpu()
Date: Tue, 4 Oct 2005 11:05:44 -0500 [thread overview]
Message-ID: <20051004160544.GG17358@us.ibm.com> (raw)
In-Reply-To: <20051004153828.GF17358@us.ibm.com>
* Ryan Harper <ryanh@us.ibm.com> [2005-10-04 10:40]:
> * Ryan Harper <ryanh@us.ibm.com> [2005-10-03 13:42]:
> > * Xen patchbot -unstable <patchbot-unstable@lists.xensource.com> [2005-10-03 13:16]:
> > > # HG changeset patch
> > > # User kaf24@firebug.cl.cam.ac.uk
> > > # Node ID 85f92475b9437fcd10bf1ae105f53b0abe963050
> > > # Parent dd87869f877ca9c68c97f36b3870908fb279edb9
> > > Create new vcpu_op() hypercall. Replaces old boot_vcpu()
> > > hypercall and vcpu-related schedop commands.
> > >
> > > Signed-off-by: Keir Fraser <keir@xensource.com>
>
> btw, this patch also regressed vcpu-{enable/disable} for dom0 and domU.
Actually this was just the first changeset where I noticed. The break
is further back. I'll reply in a bit with the changeset where this was
broken.
--
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-04 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1EMUrD-0002RM-Cz@xenbits.xensource.com>
2005-10-03 18:42 ` [Xen-changelog] Create new vcpu_op() hypercall. Replaces old boot_vcpu() Ryan Harper
2005-10-03 20:48 ` Keir Fraser
2005-10-03 21:07 ` Ryan Harper
2005-10-03 21:53 ` Keir Fraser
2005-10-04 15:38 ` Ryan Harper
2005-10-04 16:05 ` Ryan Harper [this message]
2005-10-04 16:36 ` Keir Fraser
2005-10-04 20:39 ` Ryan Harper
2005-10-04 21:10 ` Ewan Mellor
2005-10-04 21:17 ` Ryan Harper
2005-10-05 9:28 ` Ewan Mellor
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=20051004160544.GG17358@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.