All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Roger Pau Monne <roger.pau@citrix.com>, xen-devel@lists.xenproject.org
Cc: Wei Liu <wei.liu2@citrix.com>, Ian Jackson <ian.jackson@eu.citrix.com>
Subject: Re: [PATCH] libxc: fix the types used in xc_dom_image to build HVM guests
Date: Thu, 15 Oct 2015 17:41:38 +0100	[thread overview]
Message-ID: <1444927298.1607.112.camel@citrix.com> (raw)
In-Reply-To: <1444926624-16789-1-git-send-email-roger.pau@citrix.com>

On Thu, 2015-10-15 at 18:30 +0200, Roger Pau Monne wrote:
> Fix the types used to store the memory parameters of an HVM guest,
> previously they defaulted to unsigned long on 32bit toolstack builds, which
> is wrong because a 32bit value cannot hold a 64bit memory address that
> crosses the 4GB boundary.

This header includes a xen_paddr_t in it which looks like the appropriate
type for most of these.

The ones which have units of pages which you've changed from xen_pfn_t to
unsigned long (not long long) should surely remain xen_pfn_t? At least
target_pages should IMHO.

lowmem_end doesn't strictly need to be 64-bit, but xen_paddr_t seems like
the appropriate type semantically nonetheless.

> 
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> Cc: Ian Campbell <ian.campbell@citrix.com>
> Cc: Wei Liu <wei.liu2@citrix.com>
> ---
> I don't have a 32bit Dom0 at hand, so if someone can try to create a HVM
> guests using a 32bit toolstack with more than 4GB of RAM it would be
> helpful.
> ---
>  tools/libxc/include/xc_dom.h | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/tools/libxc/include/xc_dom.h b/tools/libxc/include/xc_dom.h
> index e52b023..eb3e355 100644
> --- a/tools/libxc/include/xc_dom.h
> +++ b/tools/libxc/include/xc_dom.h
> @@ -186,11 +186,11 @@ struct xc_dom_image {
>      } container_type;
>  
>      /* HVM specific fields. */
> -    xen_pfn_t target_pages;
> -    xen_pfn_t mmio_start;
> -    xen_pfn_t mmio_size;
> -    xen_pfn_t lowmem_end;
> -    xen_pfn_t highmem_end;
> +    unsigned long target_pages;
> +    unsigned long long mmio_start;
> +    unsigned long long mmio_size;
> +    unsigned long lowmem_end;
> +    unsigned long long highmem_end;
>  
>      /* Extra ACPI tables passed to HVMLOADER */
>      struct xc_hvm_firmware_module acpi_module;

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2015-10-15 16:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 14:45 [xen-unstable test] 62968: regressions - FAIL osstest service owner
2015-10-15 15:21 ` Wei Liu
2015-10-15 15:26   ` Wei Liu
2015-10-15 15:52     ` Andrew Cooper
2015-10-15 16:07       ` Wei Liu
2015-10-15 16:30         ` [PATCH] libxc: fix the types used in xc_dom_image to build HVM guests Roger Pau Monne
2015-10-15 16:39           ` Juergen Gross
2015-10-15 16:41           ` Ian Campbell [this message]
2015-10-15 16:52             ` Roger Pau Monné
2015-10-15 17:16               ` Ian Campbell
2015-10-15 17:17                 ` Andrew Cooper

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=1444927298.1607.112.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.