xen-devel.lists.xenproject.org archive mirror
 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 v2] libxc: fix the types used in xc_dom_image to build HVM guests
Date: Fri, 16 Oct 2015 09:48:34 +0100	[thread overview]
Message-ID: <1444985314.1607.134.camel@citrix.com> (raw)
In-Reply-To: <1444929837-17186-1-git-send-email-roger.pau@citrix.com>

On Thu, 2015-10-15 at 19:23 +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.
> 
> 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>

Acked-by: Ian Campbell <ian.campbell@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.

I am happy after eyeballing that this is at least an improvement and am
content to let osstest answer this question.

I'm still having some trouble accessing the machines where I typically do
all my semi-automated pre-push build tests but given that these issues have
been blocking the push gate for a while now I am going to push this change
without the full, i.e. just a quick local adhoc build which I am doing now.

Ian.

> ---
> Changes since v1:
>  - Use xen_paddr_t for all the physical address related fields.
>  - Use xen_pfn_t for target_pages.
> ---
>  tools/libxc/include/xc_dom.h | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/tools/libxc/include/xc_dom.h b/tools/libxc/include/xc_dom.h
> index e52b023..7cb6b0c 100644
> --- a/tools/libxc/include/xc_dom.h
> +++ b/tools/libxc/include/xc_dom.h
> @@ -187,10 +187,10 @@ struct xc_dom_image {
>  
>      /* 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;
> +    xen_paddr_t mmio_start;
> +    xen_paddr_t mmio_size;
> +    xen_paddr_t lowmem_end;
> +    xen_paddr_t 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

  reply	other threads:[~2015-10-16  8:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 17:23 [PATCH v2] libxc: fix the types used in xc_dom_image to build HVM guests Roger Pau Monne
2015-10-16  8:48 ` Ian Campbell [this message]
2015-10-16  8:50   ` Wei Liu
2015-10-16  8:55     ` Ian Campbell
2015-10-16  8:57 ` Ian Campbell
2015-10-16  9:00   ` Wei Liu
2015-10-16  9:03     ` Roger Pau Monné
2015-10-16  9:10       ` Ian Campbell

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=1444985314.1607.134.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 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).