[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [RFC 02/24] xen: Introduce __initconst to store initial const data

On Mon, 2013-08-19 at 10:46 +0100, Jan Beulich wrote:
> >>> Julien Grall <julien.grall@xxxxxxxxxx> 08/16/13 11:06 PM >>>
> >It's possible to have 2 type (const and non-const) of data in the same
> >compilation unit. Using only __initdata will result to a compilation error:
> >
> >error: $variablename causes as section tupe conflict with $variablename2
> >
> >because a section containing const variables is marked read only and so 
> >cannot
> >contain non-const variables.
> I don't mind this change, but so far we avoided this by simply not marking
> such objects 'const'. I didn't check whether the ARM port is different in this
> regard, but the x86 port till now didn't care to mark regular read-only data
> read-only at runtime, so there's little point in being over-ambitious for 
> init-
> only data.

ARM has some reasonable amount of initdata to describe the device tree
platform drivers etc. It seems reasonable to make those const to me.

(I'm a bit surprised at the gcc behaviour of not allowing const and non
const data in the same section, but whatever)

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.