From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH, RFC] i386: highmem access assistancehypercalls
Date: Tue, 21 Oct 2008 07:38:53 +0100 [thread overview]
Message-ID: <48FD951D.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C52253C7.283B4%keir.fraser@eu.citrix.com>
>>> Keir Fraser <keir.fraser@eu.citrix.com> 20.10.08 16:27 >>>
>On 17/10/08 16:28, "Jan Beulich" <jbeulich@novell.com> wrote:
>
>> The hypervisor patch is below (using temporary numbers for the newly
>> added sub-hypercalls), the Linux patch didn't change over the first
>> submission (if the patch here is acceptable, I'll create a version
>> that applies to the 2.6.18 tree).
>>
>> Opinions?
>
>I'm fine in principle. A cursory glance at the substance of the patch
>indicates that there are some secondary portions which could be discarded or
>broken out into separate patches: the constifying of unmap_domain_page*()
>and the addition of FIX_HOLE to fixmap.h. Please divide up as appropriate
>and re-send.
Will do. One question I forgot to ask with the original mail: Should this
functionality be announced via a new feature bit?
Jan
next prev parent reply other threads:[~2008-10-21 6:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 15:28 [PATCH, RFC] i386: highmem access assistance hypercalls Jan Beulich
2008-10-20 13:40 ` Jan Beulich
2008-10-20 14:27 ` Keir Fraser
2008-10-21 6:38 ` Jan Beulich [this message]
2008-10-21 7:07 ` [PATCH, RFC] i386: highmem access assistancehypercalls Keir Fraser
2008-10-25 0:01 ` [PATCH, RFC] i386: highmem access assistance hypercalls Jeremy Fitzhardinge
2008-10-27 8:21 ` Jan Beulich
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=48FD951D.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=keir.fraser@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.