All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Owen smith <owen.smith@citrix.com>, xen-devel@lists.xen.org
Cc: ian.campbell@citrix.com, qemu-devel@nongnu.org,
	stefano.stabellini@eu.citrix.com
Subject: Re: [Qemu-devel] [Xen-devel] [PATCH 2/2] xenfb: Add comment documentation
Date: Mon, 22 Sep 2014 11:16:24 +0100	[thread overview]
Message-ID: <541FF6F8.3030906@citrix.com> (raw)
In-Reply-To: <1411376699-8175-3-git-send-email-owen.smith@citrix.com>

On 22/09/14 10:04, Owen smith wrote:
> Add documentation for page-ref, page-gref and event-channel.
> 
> Signed-off-by: Owen smith <owen.smith@citrix.com>
> ---
>  xen/include/public/io/fbif.h | 25 +++++++++++++++++++++++++
>  1 file changed, 25 insertions(+)
> 
> diff --git a/xen/include/public/io/fbif.h b/xen/include/public/io/fbif.h
> index cc25aab..ba3f524 100644
> --- a/xen/include/public/io/fbif.h
> +++ b/xen/include/public/io/fbif.h
> @@ -26,6 +26,31 @@
>  #ifndef __XEN_PUBLIC_IO_FBIF_H__
>  #define __XEN_PUBLIC_IO_FBIF_H__
>  
> +/*
> + * Frontend XenStore Nodes
> + * -----------------------
> + *
> + * page-ref
> + *   Values: <uint64_t>
> + *   Optional, "page-gref" is used if "page-ref" is not set.
> + *
> + *   The MFN of a page of memory for the shared ring structures. If not
> + *   present, "page-gref" must be set.page-ref" overrides "page-gref".

I think you mean GFN here, not MFN.

> + * page-gref
> + *   Values: <uint32_t>
> + *   Only required if "page-ref" is NOT set.
> + *
> + *   A grant reference to the memory page to be mapped for the shared ring
> + *   structures. Must be present if "page-ref" is not present.

Should there be some negotiation for which of page-ref or page-gref is
required/preferred by the backend?

The same applies to kbdif as well.

David

WARNING: multiple messages have this Message-ID (diff)
From: David Vrabel <david.vrabel@citrix.com>
To: Owen smith <owen.smith@citrix.com>, xen-devel@lists.xen.org
Cc: ian.campbell@citrix.com, qemu-devel@nongnu.org,
	stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH 2/2] xenfb: Add comment documentation
Date: Mon, 22 Sep 2014 11:16:24 +0100	[thread overview]
Message-ID: <541FF6F8.3030906@citrix.com> (raw)
In-Reply-To: <1411376699-8175-3-git-send-email-owen.smith@citrix.com>

On 22/09/14 10:04, Owen smith wrote:
> Add documentation for page-ref, page-gref and event-channel.
> 
> Signed-off-by: Owen smith <owen.smith@citrix.com>
> ---
>  xen/include/public/io/fbif.h | 25 +++++++++++++++++++++++++
>  1 file changed, 25 insertions(+)
> 
> diff --git a/xen/include/public/io/fbif.h b/xen/include/public/io/fbif.h
> index cc25aab..ba3f524 100644
> --- a/xen/include/public/io/fbif.h
> +++ b/xen/include/public/io/fbif.h
> @@ -26,6 +26,31 @@
>  #ifndef __XEN_PUBLIC_IO_FBIF_H__
>  #define __XEN_PUBLIC_IO_FBIF_H__
>  
> +/*
> + * Frontend XenStore Nodes
> + * -----------------------
> + *
> + * page-ref
> + *   Values: <uint64_t>
> + *   Optional, "page-gref" is used if "page-ref" is not set.
> + *
> + *   The MFN of a page of memory for the shared ring structures. If not
> + *   present, "page-gref" must be set.page-ref" overrides "page-gref".

I think you mean GFN here, not MFN.

> + * page-gref
> + *   Values: <uint32_t>
> + *   Only required if "page-ref" is NOT set.
> + *
> + *   A grant reference to the memory page to be mapped for the shared ring
> + *   structures. Must be present if "page-ref" is not present.

Should there be some negotiation for which of page-ref or page-gref is
required/preferred by the backend?

The same applies to kbdif as well.

David

  reply	other threads:[~2014-09-22 10:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22  9:04 [Qemu-devel] [PATCH 0/2] xenfb: Document public headers Owen smith
2014-09-22  9:04 ` [PATCH 1/2] xenfb: Add comment documentation Owen smith
2014-09-22  9:04 ` [Qemu-devel] " Owen smith
2014-10-08 13:28   ` Stefano Stabellini
2014-10-08 13:28   ` Stefano Stabellini
2014-09-22  9:04 ` [PATCH 2/2] " Owen smith
2014-09-22  9:04 ` [Qemu-devel] " Owen smith
2014-09-22 10:16   ` David Vrabel [this message]
2014-09-22 10:16     ` David Vrabel
2014-09-26 10:20     ` [Qemu-devel] [Xen-devel] " Owen Smith
2014-10-03  9:06       ` Ian Campbell
2014-10-03  9:06       ` [Qemu-devel] [Xen-devel] " Ian Campbell
2014-09-26 10:20     ` Owen Smith
2014-10-08 13:29   ` Stefano Stabellini
2014-10-08 13:29   ` [Qemu-devel] " Stefano Stabellini

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=541FF6F8.3030906@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=owen.smith@citrix.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.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.