xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Arianna Avanzini <avanzini.arianna@gmail.com>
To: Julien Grall <julien.grall@linaro.org>, xen-devel@lists.xen.org
Cc: paolo.valente@unimore.it, Ian Campbell <Ian.Campbell@citrix.com>,
	stefano.stabellini@eu.citrix.com, dario.faggioli@citrix.com,
	Tim Deegan <tim@xen.org>,
	julien.grall@citrix.com, etrudeau@broadcom.com,
	viktor.kleinik@globallogic.com
Subject: Re: [RFC PATCH 1/3] arch, arm32: add definition of paddr_bits
Date: Fri, 07 Mar 2014 01:36:37 +0100	[thread overview]
Message-ID: <53191495.3050202@gmail.com> (raw)
In-Reply-To: <5312E835.4080700@linaro.org>

On 03/02/2014 09:13 AM, Julien Grall wrote:
> Hello Arianna,
> 

Hello,

> On 02/03/14 08:49, Arianna Avanzini wrote:
>> Currently, the paddr_bits variable, which keeps the machine word size,
>> is not defined for the arm32 architecture. This commits adds its
>> definition for arm32 in a new header in the architecture-specific
>> directory.
>> This change is instrumental to the implementation of the
>> XEN_DOMCTL_memory_mapping hypercall, added in the following
>> commit.
> 
> paddr_bits doesn't keep the machine word size but the size of the physical address.
> 
> On ARM, this value is fixed and defined as PADDR_BITS in
> xen/include/asm-arm/page.h. I don't think we need to introduce a variable for
> this purpose. x86 defines paddr_bits because the value can change on some
> processor.
> 

Thank you for explaining that. I've tried to fix as suggested.

>> diff --git a/xen/arch/arm/arm32/cpu.h b/xen/arch/arm/arm32/cpu.h
>> new file mode 100644
>> index 0000000..1091051
>> --- /dev/null
>> +++ b/xen/arch/arm/arm32/cpu.h
>> @@ -0,0 +1,7 @@
>> +#ifndef __ARM_ARM32_CPU_H
>> +#define __ARM_ARM32_CPU_H
>> +
>> +/* ARM-v7 features LPAE (machine word size is 40 bit) */
>> +unsigned int paddr_bits = 40;
>> +
> 
> Global variable must not be defined in headers. If someone decides to include
> this header in 2 differents C files, the variable will be defined twice.
> Therefore the linker-step will fail.
> 
> You should define it in a c-file.
> 

OK, thank you again.


> Regards,
> 


-- 
/*
 * Arianna Avanzini
 * avanzini.arianna@gmail.com
 * 73628@studenti.unimore.it
 */

  reply	other threads:[~2014-03-07  0:36 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-02  0:49 [RFC PATCH 0/3] Implement the XEN_DOMCTL_memory_mapping hypecall for arm32 Arianna Avanzini
2014-03-02  0:49 ` [RFC PATCH 1/3] arch, arm32: add definition of paddr_bits Arianna Avanzini
2014-03-02  8:13   ` Julien Grall
2014-03-07  0:36     ` Arianna Avanzini [this message]
2014-03-02  0:49 ` [RFC PATCH 2/3] arch, arm32: add the XEN_DOMCTL_memory_mapping hypercall Arianna Avanzini
2014-03-02  9:56   ` Julien Grall
2014-03-03 11:56     ` Dario Faggioli
2014-03-03 15:20       ` Julien Grall
2014-03-03 15:33         ` Dario Faggioli
2014-03-04  2:42           ` Julien Grall
2014-03-07  0:47             ` Arianna Avanzini
2014-03-03 16:25         ` Eric Trudeau
2014-03-03 16:35           ` Dario Faggioli
2014-03-03 19:04             ` Eric Trudeau
2014-03-05 13:59     ` Arianna Avanzini
2014-03-06  3:41       ` Julien Grall
2014-03-07  0:57         ` Arianna Avanzini
2014-03-03 18:06   ` Eric Trudeau
2014-03-04  3:08     ` Julien Grall
2014-03-07  0:56       ` Arianna Avanzini
2014-03-07  3:41         ` Julien Grall
2014-03-07 19:49           ` Arianna Avanzini
2014-03-02  0:49 ` [RFC PATCH 3/3] tools, libxl: handle the iomem parameter with the memory_mapping hcall Arianna Avanzini
2014-03-02 10:33   ` Julien Grall
2014-03-02 11:27     ` Ian Campbell
2014-03-03 10:32       ` Dario Faggioli
2014-03-03 15:13         ` Julien Grall
2014-03-07  0:45           ` Arianna Avanzini
2014-03-07  4:03             ` Julien Grall
2014-03-07 19:54               ` Arianna Avanzini
2014-03-03 11:19     ` Dario Faggioli
2014-03-07  4:05       ` Julien Grall
2014-03-02  8:13 ` [RFC PATCH 0/3] Implement the XEN_DOMCTL_memory_mapping hypecall for arm32 Julien Grall

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=53191495.3050202@gmail.com \
    --to=avanzini.arianna@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=etrudeau@broadcom.com \
    --cc=julien.grall@citrix.com \
    --cc=julien.grall@linaro.org \
    --cc=paolo.valente@unimore.it \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=viktor.kleinik@globallogic.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).