xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Keir Fraser <keir@xen.org>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH] x86/bigmem: eliminate struct domain address width restriction
Date: Tue, 1 Sep 2015 13:14:24 +0100	[thread overview]
Message-ID: <1441109664.27618.56.camel@citrix.com> (raw)
In-Reply-To: <55E5AEED020000780009E91B@prv-mh.provo.novell.com>

On Tue, 2015-09-01 at 05:58 -0600, Jan Beulich wrote:
> > 
> > > > On 01.09.15 at 12:57, <ian.campbell@citrix.com> wrote:
> > 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?
> 
> Hmm, yes, in cases like this I agree (assuming that all compiler
> versions we care about will be intelligent enough to eliminate the
> variable).

Even if it weren't I don't think it would be noticeable in
alloc_domain_struct().

Ian.

      reply	other threads:[~2015-09-01 12:14 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
2015-09-01 11:58   ` Jan Beulich
2015-09-01 12:14     ` Ian Campbell [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=1441109664.27618.56.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 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).