From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Jan Beulich <jbeulich@novell.com>,
Jinsong Liu <jinsong.liu@intel.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 2] Add user PM control interface
Date: Wed, 10 Dec 2008 10:32:32 +0000 [thread overview]
Message-ID: <C5654B40.20057%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C5654492.2004B%keir.fraser@eu.citrix.com>
On 10/12/2008 10:04, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:
> The only reason for dom0 kernel not to use domctl/sysctl is that the
> structures may be subject to change. So if you do, then the dom0 kernel in
> that case becomes part of the 'matched set' with Xen itself and the tools.
> As a distributor of 'whole system' software, you may not actually care about
> this limitation (since you can track dependencies and easily cause all
> packages to be upgraded)?
>
> Adding some domctl/sysctl usage in the Linux kernel would actually be fine
> by me, except that I do think it should be conditional on a Kconfig option
> that makes the above additional constraint very clear to the user.
>
> And actually, I don't think we've broken sysctl/domctl compatibility, or
> changed their ABI version numbers, at all recently.
Thinking some more, this doesn't work well unless we start guaranteeing
source compatibility at least... Perhaps it's time now to make stronger
guarantees about the domctl and sysctl interfaces.
Really in this case it depends: is support for Linux pm tools going to be
practically useful, especially in the general cases such as #dom0-cpus !=
#physical-cpus? It does seem a bit dubious to me.
-- Keir
next prev parent reply other threads:[~2008-12-10 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 8:46 [PATCH 2] Add user PM control interface Liu, Jinsong
2008-12-10 9:08 ` Jan Beulich
2008-12-10 10:04 ` Keir Fraser
2008-12-10 10:06 ` Keir Fraser
2008-12-10 10:32 ` Keir Fraser [this message]
2008-12-10 10:41 ` Jan Beulich
2008-12-10 13:08 ` Tian, Kevin
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=C5654B40.20057%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=jbeulich@novell.com \
--cc=jinsong.liu@intel.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.