From: Wei Liu <wei.liu2@citrix.com>
To: xen-devel@lists.xen.org
Cc: Wei Liu <wei.liu2@citrix.com>,
david.vrabel@citrix.com, jbeulich@suse.com,
ian.campbell@citrix.com
Subject: [RFC PATCH V5 05/15] evtchn: add d->max_evtchns
Date: Tue, 19 Mar 2013 15:15:30 +0000 [thread overview]
Message-ID: <1363706140-26989-6-git-send-email-wei.liu2@citrix.com> (raw)
In-Reply-To: <1363706140-26989-1-git-send-email-wei.liu2@citrix.com>
This variable indicates the maximum number of event channels a domain can use.
Also replace MAX_EVTCHNS macro with inline function which will be used to
calculate max event channels in the future.
Signed-off-by: Wei Liu <wei.liu2@citrix.com>
---
xen/common/event_channel.c | 5 +++--
xen/common/schedule.c | 2 +-
xen/include/xen/event.h | 7 ++++++-
xen/include/xen/sched.h | 2 +-
4 files changed, 11 insertions(+), 5 deletions(-)
diff --git a/xen/common/event_channel.c b/xen/common/event_channel.c
index 54ae281..ebe8278 100644
--- a/xen/common/event_channel.c
+++ b/xen/common/event_channel.c
@@ -166,7 +166,7 @@ static int get_free_port(struct domain *d)
if ( evtchn_from_port(d, port)->state == ECS_FREE )
return port;
- if ( port == MAX_EVTCHNS(d) )
+ if ( port == d->max_evtchns )
return -ENOSPC;
if ( unlikely(group_from_port(d, port) == NULL ) )
@@ -1153,6 +1153,7 @@ const static struct evtchn_port_ops evtchn_2l_ops = {
int evtchn_init(struct domain *d)
{
spin_lock_init(&d->event_lock);
+ d->max_evtchns = max_evtchns(d);
if ( get_free_port(d) != 0 )
return -EINVAL;
evtchn_from_port(d, 0)->state = ECS_RESERVED;
@@ -1248,7 +1249,7 @@ static void domain_dump_evtchn_info(struct domain *d)
spin_lock(&d->event_lock);
- for ( port = 1; port < MAX_EVTCHNS(d); ++port )
+ for ( port = 1; port < d->max_evtchns; ++port )
{
const struct evtchn *chn;
char *ssid;
diff --git a/xen/common/schedule.c b/xen/common/schedule.c
index 6362e64..2e4a8d4 100644
--- a/xen/common/schedule.c
+++ b/xen/common/schedule.c
@@ -698,7 +698,7 @@ static long do_poll(struct sched_poll *sched_poll)
goto out;
rc = -EINVAL;
- if ( port >= MAX_EVTCHNS(d) )
+ if ( port >= d->max_evtchns )
goto out;
rc = 0;
diff --git a/xen/include/xen/event.h b/xen/include/xen/event.h
index d3ee5e0..6e4d533 100644
--- a/xen/include/xen/event.h
+++ b/xen/include/xen/event.h
@@ -15,6 +15,11 @@
#include <asm/bitops.h>
#include <asm/event.h>
+static inline unsigned int max_evtchns(struct domain *d)
+{
+ return BITS_PER_EVTCHN_WORD(d) * BITS_PER_EVTCHN_WORD(d);
+}
+
/*
* send_guest_vcpu_virq: Notify guest via a per-VCPU VIRQ.
* @v: VCPU to which virtual IRQ should be sent
@@ -86,7 +91,7 @@ void notify_via_xen_event_channel(struct domain *ld, int lport);
#define bucket_from_port(d,p) \
((group_from_port(d,p))[((p)%EVTCHNS_PER_GROUP)/EVTCHNS_PER_BUCKET])
#define port_is_valid(d,p) \
- (((p) >= 0) && ((p) < MAX_EVTCHNS(d)) && \
+ (((p) >= 0) && ((p) < d->max_evtchns) && \
(group_from_port(d,p) != NULL) && \
(bucket_from_port(d,p) != NULL))
#define evtchn_from_port(d,p) \
diff --git a/xen/include/xen/sched.h b/xen/include/xen/sched.h
index 1cd289e..f89e9c5 100644
--- a/xen/include/xen/sched.h
+++ b/xen/include/xen/sched.h
@@ -50,7 +50,6 @@ extern struct domain *dom0;
#else
#define BITS_PER_EVTCHN_WORD(d) (has_32bit_shinfo(d) ? 32 : BITS_PER_XEN_ULONG)
#endif
-#define MAX_EVTCHNS(d) (BITS_PER_EVTCHN_WORD(d) * BITS_PER_EVTCHN_WORD(d))
/*
* To make sure EVTCHNS_PER_BUCKET is at least 1 for 32 bit build,
* NR_EVTCHN_GROUPS * BUCKETES_PER_GROUP should be <= 1024.
@@ -271,6 +270,7 @@ struct domain
struct evtchn **evtchn[NR_EVTCHN_GROUPS];
const struct evtchn_port_ops *evtchn_ops;
spinlock_t event_lock;
+ unsigned int max_evtchns;
struct grant_table *grant_table;
--
1.7.10.4
next prev parent reply other threads:[~2013-03-19 15:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 15:15 [RFC PATCH V5 00/15] Implement 3-level event channel ABI in Xen Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 01/15] Clean up trailing whitespaces Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 02/15] evtchn: reset bucket if xsm_alloc_security_evtchn fails Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 03/15] evtchn: alter internal object handling scheme Wei Liu
2013-03-20 9:22 ` Jan Beulich
2013-03-19 15:15 ` [RFC PATCH V5 04/15] evtchn: generalize event channel operations Wei Liu
2013-03-20 9:31 ` Jan Beulich
2013-03-19 15:15 ` Wei Liu [this message]
2013-03-19 15:15 ` [RFC PATCH V5 06/15] evtchn: implement extended event channel ABIs query Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 07/15] evtchn: define 3-level event channel registration interface Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 08/15] evtchn: add evtchn_extended in struct domain Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 09/15] evtchn: calculate max event channels for EVTCHN_EXTENDED_L3 Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 10/15] evtchn: update Xen public header xen.h Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 11/15] evtchn: use pointers to reference evtchn_pending/mask Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 12/15] evtchn: introduce EVTCHN_WORD_BITORDER macro Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 13/15] evtchn: infrastructure to manipulate 3-level event channel pages Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 14/15] evtchn: implement 3-level event channel routines Wei Liu
2013-03-19 15:15 ` [RFC PATCH V5 15/15] evtchn: only allow 3-level event channel on Dom0 Wei Liu
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=1363706140-26989-6-git-send-email-wei.liu2@citrix.com \
--to=wei.liu2@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=jbeulich@suse.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).