From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Simon Rowe <simon.rowe@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH 1/4] xen/domain: Introduce domain_max_vcpus() helper and implement per arch
Date: Mon, 19 Jan 2015 12:52:18 +0000 [thread overview]
Message-ID: <54BCFE02.4010106@citrix.com> (raw)
In-Reply-To: <54BCF5A2.5060500@eu.citrix.com>
On 19/01/15 12:16, Simon Rowe wrote:
> On 19/01/15 11:21, Andrew Cooper wrote:
>> This allows the common XEN_DOMCTL_max_vcpus handler to loose some
>> x86-specific
>> architecture knowledge.
> Sp. "lose"
>> +unsigned int domain_max_vcpus(const struct domain *d)
>> +{
>> + return MAX_VIRT_CPUS;
>> +}
>> +
>>
>
> inline?
>
> Simon
>
I considered that but, while there is an asm-x86/domain.h, there is not
an asm-arm/domain.h which would be the logical location for it to live.
I can introduce an asm-arm/domain.h if the arm maintainers are happy.
~Andrew
next prev parent reply other threads:[~2015-01-19 12:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-19 11:21 [PATCH 0/4] Reduce the use of MAX_VIRT_CPUS in tree Andrew Cooper
2015-01-19 11:21 ` [PATCH 1/4] xen/domain: Introduce domain_max_vcpus() helper and implement per arch Andrew Cooper
2015-01-19 12:16 ` Simon Rowe
2015-01-19 12:52 ` Andrew Cooper [this message]
2015-01-19 12:57 ` Ian Campbell
2015-01-19 12:59 ` Andrew Cooper
2015-01-20 10:27 ` Jan Beulich
2015-01-20 14:06 ` [PATCH v2 " Andrew Cooper
2015-01-20 11:05 ` [PATCH " Ian Campbell
2015-01-19 11:21 ` [PATCH 2/4] xen/evtchn: Reduce the size of the poll_mask where possible Andrew Cooper
2015-01-20 10:28 ` Jan Beulich
2015-01-19 11:21 ` [PATCH 3/4] sched/arinc653: Remove MAX_VIRT_CPUS bounds check Andrew Cooper
2015-01-20 10:34 ` Jan Beulich
2015-01-20 14:20 ` Robert VanVossen
2015-01-19 11:21 ` [PATCH 4/4] xen/many: Drop redundant MAX_VIRT_CPUS bounds checks Andrew Cooper
2015-01-20 10:36 ` Jan Beulich
2015-01-20 11:06 ` 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=54BCFE02.4010106@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=simon.rowe@eu.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 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.