From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: GNTCOPY_can_fail ???
Date: Fri, 07 Jun 2013 12:20:12 +0100 [thread overview]
Message-ID: <CDD7807C.28EF8%keir.xen@gmail.com> (raw)
In-Reply-To: <51B1C2C702000078000DC2A2@nat28.tlf.novell.com>
On 07/06/2013 10:23, "Jan Beulich" <JBeulich@suse.com> wrote:
> Just noticed that apart from getting defined, this is completely
> unused in both Xen and Linux. Does anyone know what the
> intended purpose was? Unless we implement that intention,
> shouldn't we at least mark it in the public header as unusable
> at present, or even remove the visibility of the definitions for
> new enough __XEN_INTERFACE_VERSION__?
I think the definition leaked in from early work on xenpaging, on the guest
side, and never actually been used by a non-developer's guest kernel. I'd be
happy to see it removed completely and unconditionally.
-- Keir
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-06-07 11:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 9:23 GNTCOPY_can_fail ??? Jan Beulich
2013-06-07 11:20 ` Keir Fraser [this message]
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=CDD7807C.28EF8%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).