xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Daniel Castro <evil.dani@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 02/10] Move PAGE_SHIFT to memmap.h
Date: Wed, 24 Aug 2011 13:51:46 -0400	[thread overview]
Message-ID: <20110824175146.GB15675@dumpdata.com> (raw)
In-Reply-To: <1313683408-32306-3-git-send-email-evil.dani@gmail.com>

On Fri, Aug 19, 2011 at 01:03:19AM +0900, Daniel Castro wrote:
> PAGE_SHIFT is used by both Virtio and Xen as a contant when moving
> addresses from guest space to machine space, in order to have a
> single definition PAGE_SHIFT has been moved to memmap.h. This has
> no impact on neither virtio or xen.
> 
> Signed-off-by: Daniel Castro <evil.dani@gmail.com>
> ---
>  src/memmap.h      |    2 ++
>  src/virtio-ring.h |    2 +-
>  2 files changed, 3 insertions(+), 1 deletions(-)
> 
> diff --git a/src/memmap.h b/src/memmap.h
> index 01c7ddb..8674168 100644
> --- a/src/memmap.h
> +++ b/src/memmap.h
> @@ -21,6 +21,8 @@ void memmap_finalize(void);
>  
>  // A typical OS page size
>  #define PAGE_SIZE 4096
> +//Used by Virtio and Xen
> +#define PAGE_SHIFT 12

So aren't those two files also used on other architectures - say
PPC64 which have a different page size - 64K. Isn't there some other
defines for this? Or are the patches for that not present anywhere yet?

>  
>  // e820 map storage (defined in system.c)
>  extern struct e820entry e820_list[];
> diff --git a/src/virtio-ring.h b/src/virtio-ring.h
> index b7a7aaf..fd30778 100644
> --- a/src/virtio-ring.h
> +++ b/src/virtio-ring.h
> @@ -4,7 +4,7 @@
>  #include "types.h" // u64
>  #include "memmap.h" // PAGE_SIZE
>  
> -#define PAGE_SHIFT 12
> +
>  #define PAGE_MASK  (PAGE_SIZE-1)
>  
>  #define virt_to_phys(v) (unsigned long)(v)
> -- 
> 1.7.4.1
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-08-24 17:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 16:03 [PATCH 00/10] Xenstore communication support for Seabios Daniel Castro
2011-08-18 16:03 ` [PATCH 01/10] Xen: Guest Handlers and Copyrights Daniel Castro
2011-08-18 16:03 ` [PATCH 02/10] Move PAGE_SHIFT to memmap.h Daniel Castro
2011-08-24 17:51   ` Konrad Rzeszutek Wilk [this message]
2011-08-24 21:08     ` Ian Campbell
2011-08-18 16:03 ` [PATCH 03/10] Xen: Use PAGE_SHIFT as a constant Daniel Castro
2011-08-18 16:03 ` [PATCH 04/10] Xen: Support for interdomain event channel Daniel Castro
2011-08-18 16:03 ` [PATCH 05/10] Xen: Support for HVM_op Hypercall Daniel Castro
2011-08-18 16:03 ` [PATCH 06/10] Xen: Support for memory_op Hypercall Daniel Castro
2011-08-18 16:03 ` [PATCH 07/10] Xen: Support for sched_op hypercall Daniel Castro
2011-08-18 16:03 ` [PATCH 08/10] Xen: Shared info for CPU yield support and xenbus protocol Daniel Castro
2011-08-18 16:03 ` [PATCH 09/10] Xen: Xenstore communication via xenbus Daniel Castro
2011-08-18 16:03 ` [PATCH 10/10] Xen: Xenstore example -do not apply Daniel Castro
2011-08-18 16:03 ` [PATCH 10/10] Xen: Xenstore example Daniel Castro
2011-08-24 17:56 ` [PATCH 00/10] Xenstore communication support for Seabios Konrad Rzeszutek Wilk

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=20110824175146.GB15675@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=evil.dani@gmail.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 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).