From: Keir Fraser <keir.xen@gmail.com>
To: Jean Guyader <jean.guyader@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: xen kernel: build failure
Date: Wed, 23 Nov 2011 17:13:17 +0000 [thread overview]
Message-ID: <CAF2DA2D.256ED%keir.xen@gmail.com> (raw)
In-Reply-To: <CAEBdQ92Dx_mLWU5qsQ8gNgLQ+bvr2ec+Y1Fr-i06=ExBa0B4Tg@mail.gmail.com>
On 23/11/2011 16:31, "Jean Guyader" <jean.guyader@gmail.com> wrote:
>>> Removing the line
>>>
>>> BUILD_BUG_ON(sizeof(*d) > PAGE_SIZE);
>>>
>>> makes xen kernel compile again.
>>
>> But not actually work properly. We only allocate a single page for the
>> domain struct. If the struct is bigger than a page, you'll get memory
>> corruption at run time.
>>
>
> Is there a reason for that? What would be the recommended to add something
> into the struct domain now if we can't make it bigger than a page.
If the thing being added is sufficiently large and self-contained, it could
be allocated separately and a pointer added to the domain struct. Else a
large logical piece of the domain struct needs to be split off. Would have
to check what would be a nice large piece -- arch.{hvm,pv} for example. Jan
might also have an opinion, as he already did some work on shrinking the
domain struct.
-- Keir
prev parent reply other threads:[~2011-11-23 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 11:08 xen kernel: build failure Christoph Egger
2011-10-25 12:35 ` Keir Fraser
2011-10-25 15:22 ` Christoph Egger
2011-11-23 16:31 ` Jean Guyader
2011-11-23 16:41 ` Jan Beulich
2011-11-28 11:59 ` Jean Guyader
2011-11-28 12:16 ` Jean Guyader
2011-11-28 12:31 ` Jan Beulich
2011-11-23 17:13 ` Keir Fraser [this message]
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=CAF2DA2D.256ED%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=jean.guyader@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 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.