All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: ncmike@us.ibm.com
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [Xen-staging] [xen-unstable] xsm: Consolidate xsm processing within domain control hypercall.
Date: Tue, 04 Dec 2007 13:06:22 -0700	[thread overview]
Message-ID: <1196798782.19310.36.camel@lappy> (raw)
In-Reply-To: <200712041026.lB4AQPM6004133@latara.uk.xensource.com>


  Does this work right across a PV domain save/restore on x86?  On ia64
I end up with "Domain-Unnamed" after I save a PV domain and another
after I restore it, then do a shutdown.  Reverting this patch restores
correct behavior.  Thanks,

	Alex

On Tue, 2007-12-04 at 10:26 +0000, Xen staging patchbot-unstable wrote:
> # HG changeset patch
> # User Keir Fraser
> # Date 1196763935 0
> # Node ID d2bef6551c1263e457aef75ce403ba53652a803f
> # Parent  190c2592247d3258d6b2c60939d27928c70ac5ca
> xsm: Consolidate xsm processing within domain control hypercall.
> 
> Consolidate all the 15 xsm calls from within do_domctl a single
> routine that is only called in one place, xsm_domctl:
> 
> int xsm_domctl (struct xen_domctl *domctl);
> 
> The parameter to domctl is a pointer to the xen_domctl structure that
> contains a union of all sub operational parameters.
> 
> The benefits of this patch include:
> 
> (1) Easier to maintain because there is one place in the entire
> hypercall to check with the xsm, instead of 15 or more.
> 
> (2) New sub-operations don't also need to add a corresponding xsm
>     function.
> 
> (3) Removes 178 lines of code.
> 
> (4) Enhanced security because of 1-4.
> 

-- 
Alex Williamson                             HP Open Source & Linux Org.

       reply	other threads:[~2007-12-04 20:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200712041026.lB4AQPM6004133@latara.uk.xensource.com>
2007-12-04 20:06 ` Alex Williamson [this message]
2007-12-04 20:44   ` [Xen-staging] [xen-unstable] xsm: Consolidate xsm processing within domain control hypercall Alex Williamson
2007-12-04 21:20     ` George S. Coker, II
2007-12-04 21:46       ` Mike D. Day
2007-12-04 21:54         ` George S. Coker, II
2007-12-04 21:59           ` Mike D. Day
2007-12-04 23:26             ` George S. Coker, II
2007-12-04 23:22         ` George S. Coker, II
2007-12-04 21:36     ` Mike D. Day
2007-12-04 21:52       ` Alex Williamson
2007-12-04 21:58         ` George S. Coker, II
2007-12-04 22:26           ` Mike D. Day
2007-12-04 21:49   ` Mike D. Day
2007-12-04 22:05     ` Alex Williamson
2007-12-04 22:23       ` George S. Coker, II
2007-12-05  0:19       ` Alex Williamson
2007-12-04 22:44   ` Mike D. Day
2007-12-04 23:27     ` George S. Coker, II

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=1196798782.19310.36.camel@lappy \
    --to=alex.williamson@hp.com \
    --cc=ncmike@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.