From: Doug Goldstein <cardoe@cardoe.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Keir Fraser <keir@xen.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v2 2/2] build: convert NR_CPUS to Kconfig
Date: Tue, 12 Jan 2016 09:20:59 -0600 [thread overview]
Message-ID: <569519DB.4060400@cardoe.com> (raw)
In-Reply-To: <5694CA2F02000078000C5CCF@prv-mh.provo.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 655 bytes --]
On 1/12/16 2:41 AM, Jan Beulich wrote:
>>>> On 11.01.16 at 23:02, <cardoe@cardoe.com> wrote:
>> --- a/xen/include/xen/config.h
>> +++ b/xen/include/xen/config.h
>> @@ -92,4 +92,7 @@
>> #define FLASK_AVC_STATS 1
>> #endif
>>
>> +/* allow existing code to work with Kconfig variable */
>> +#define NR_CPUS CONFIG_NR_CPUS
>
> Perhaps here or in a follow-up patch derive CONFIG_SMP (used in a
> few places in ARM code) from NR_CPUS > 1?
>
> Jan
>
I agree with you. That's actually in a follow on. I've got most of the
CONFIG_ fields in a branch locally and as each patch gets reviewed I'm
submitting more.
--
Doug Goldstein
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-12 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 22:02 [PATCH v2 1/2] build: introduce CONFIG_NR_CPUS in Kconfig Doug Goldstein
2016-01-11 22:02 ` [PATCH v2 2/2] build: convert NR_CPUS to Kconfig Doug Goldstein
2016-01-12 8:41 ` Jan Beulich
2016-01-12 15:20 ` Doug Goldstein [this message]
2016-01-12 8:37 ` [PATCH v2 1/2] build: introduce CONFIG_NR_CPUS in Kconfig Jan Beulich
2016-01-12 13:10 ` Doug Goldstein
2016-01-13 14:48 ` Doug Goldstein
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=569519DB.4060400@cardoe.com \
--to=cardoe@cardoe.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@citrix.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).