From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: xen-devel@lists.xensource.com
Subject: Re: [Xen-changelog] [xen-unstable] Clean up handling of IS_PRIV_FOR() and rcu_[un]lock_domain().
Date: Sat, 29 Mar 2008 11:23:16 +0000 [thread overview]
Message-ID: <20080329112316.GC4482@implementation> (raw)
In-Reply-To: <200803290750.m2T7o8pP027589@xenbits.xensource.com>
Hello,
Xen patchbot-unstable, le Sat 29 Mar 2008 00:50:07 -0700, a écrit :
> This probably breaks stub domains. Where necessary, some of these
> reversions can themselves be reverted where they are judged both
> necessary and safe.
HVMOP_get_param is needed yes (set_param doesn't seem to be).
set_foreigndom is probably needed in a lot of cases, but maybe not all,
so maybe we should have two versions of it.
DOMCTL_getdomaininfo is needed.
DOMCTL_max_mem is needed.
DOMCTL_settimeoffset is needed.
x86 DOMCTL_memory/ioport_mapping are needed for passthrough (not
implemented yet, though)
IIRC the event channel ops are not needed right now, but will probably
be in the future.
XENMEM_in/decrease_reservation and populate_physmap are needed.
XENMEM_maximum_gpfn is needed.
I don't have the time to test precisely what else would be needed, but
the cases above should be at least 90% of what is.
Samuel
next parent reply other threads:[~2008-03-29 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200803290750.m2T7o8pP027589@xenbits.xensource.com>
2008-03-29 11:23 ` Samuel Thibault [this message]
2008-03-29 11:47 ` Re: [Xen-changelog] [xen-unstable] Clean up handling of IS_PRIV_FOR() and rcu_[un]lock_domain() Keir Fraser
2008-03-29 11:58 ` Samuel Thibault
2008-04-05 14:28 ` Samuel Thibault
2008-04-05 16:31 ` Keir Fraser
2008-04-11 14:27 ` Samuel Thibault
2008-04-05 16:25 ` Samuel Thibault
2008-04-10 15:43 ` ioemu & settimeoffset [Was: Clean up handling of IS_PRIV_FOR() and rcu_[un]lock_domain()] Samuel Thibault
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=20080329112316.GC4482@implementation \
--to=samuel.thibault@eu.citrix.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.