From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] x86/bigmem: eliminate struct domain address width restriction
Date: Tue, 1 Sep 2015 11:57:40 +0100 [thread overview]
Message-ID: <1441105060.27618.37.camel@citrix.com> (raw)
In-Reply-To: <55DD89B1020000780009D0EB@prv-mh.provo.novell.com>
On Wed, 2015-08-26 at 01:41 -0600, Jan Beulich wrote:
> @@ -225,10 +226,12 @@ static unsigned int __init noinline _dom
>
> return bits;
> }
> +#endif
>
> struct domain *alloc_domain_struct(void)
> {
> struct domain *d;
> +#ifndef CONFIG_BIGMEM
> /*
> * We pack the PDX of the domain structure into a 32-bit field
> within
> * the page_info structure. Hence the MEMF_bits() restriction.
> @@ -237,12 +240,16 @@ struct domain *alloc_domain_struct(void)
>
> if ( unlikely(!bits) )
> bits = _domain_struct_bits();
> +#else
> +# define bits 0
const unsigned int bits = 0;
Seems nicer than the trailing #undef?
> +#endif
>
> BUILD_BUG_ON(sizeof(*d) > PAGE_SIZE);
> d = alloc_xenheap_pages(0, MEMF_bits(bits));
> if ( d != NULL )
> clear_page(d);
> return d;
> +#undef bits
> }
>
> void free_domain_struct(struct domain *d)
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-09-01 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 7:41 [PATCH] x86/bigmem: eliminate struct domain address width restriction Jan Beulich
2015-08-26 8:55 ` Andrew Cooper
2015-09-01 10:57 ` Ian Campbell [this message]
2015-09-01 11:58 ` Jan Beulich
2015-09-01 12:14 ` 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=1441105060.27618.37.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--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.