From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andres Lagar-Cavilla <andres.lagarcavilla@gmail.com>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Andres Lagar-Cavilla <andreslc@gridcentric.ca>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Andres Lagar-Cavilla <andres@lagarcavilla.org>,
Attilio Rao <attilio.rao@citrix.com>
Subject: Re: [PATCH] Synchronize privcmd header constants
Date: Fri, 19 Oct 2012 17:49:57 +0200 [thread overview]
Message-ID: <508176A5.10401@citrix.com> (raw)
In-Reply-To: <94CA9621-D7BF-45CB-A6A2-7F68E14D3C23@gmail.com>
On 19/10/12 17:46, Andres Lagar-Cavilla wrote:
>
> On Oct 19, 2012, at 4:37 AM, Roger Pau Monné <roger.pau@citrix.com> wrote:
>
>> On 19/10/12 04:20, Andres Lagar-Cavilla wrote:
>>> I've had a look. The xen.org tree knows about three other OSes: minios, solaris and netbsd. None knows about paged out frames. None uses the XEN_DOMCTL_PFINFO_PAGEDTAB constant in domctl.h
>>>
>>> 1. The domctl.h constant can still go away without hurting other OSes.
>>
>> I've checked and NetBSD doesn't use XEN_DOMCTL_PFINFO_PAGEDTAB, so as
>> Andres says I guess it's safe to remove it.
>>
>>> 2. It is trivial to add the PRIVCMD_MMAPBATCH_* constants to the privcmd.h of other OSes. It can't hurt. I can do it here. Each OS Xen maintainer would have to take care of syncing that up in the respective upstream. However ...
>>> 3. Not that trivial to teach all these OSes about paged out frames. Does anyone care?
>>
>> Well, I'm sure the NetBSD community would be interested in this, but
>> finding someone to actually work on it is a whole different story…
>
> Thanks Roger. Ian should I expect a response from Solaris?
Solaris (Illumos) is currently pretty broken, and has gone the KVM side
as far as I know, so I wouldn't expect any response.
next prev parent reply other threads:[~2012-10-19 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 15:30 [PATCH] Synchronize privcmd header constants Andres Lagar-Cavilla
2012-10-18 8:08 ` Ian Campbell
2012-10-19 2:20 ` Andres Lagar-Cavilla
2012-10-19 8:37 ` Roger Pau Monné
2012-10-19 15:46 ` Andres Lagar-Cavilla
2012-10-19 15:49 ` Roger Pau Monné [this message]
2012-10-19 17:41 ` Pasi Kärkkäinen
2012-11-12 17:04 ` Ian Campbell
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=508176A5.10401@citrix.com \
--to=roger.pau@citrix.com \
--cc=Christoph.Egger@amd.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=andres.lagarcavilla@gmail.com \
--cc=andres@lagarcavilla.org \
--cc=andreslc@gridcentric.ca \
--cc=attilio.rao@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.