From: Wei Liu <Wei.Liu2@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Wei Liu <liuw@liuw.name>,
wei.liu2@citrix.com,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [RFC PATCH 1/3] Add a field in struct domain to indicate evtchn level.
Date: Wed, 2 Jan 2013 14:28:06 +0000 [thread overview]
Message-ID: <1357136886.8077.29.camel@iceland> (raw)
In-Reply-To: <50E415C4.8090600@citrix.com>
On Wed, 2013-01-02 at 11:11 +0000, David Vrabel wrote:
> On 31/12/12 18:22, Wei Liu wrote:
> > From: Wei Liu <liuw@liuw.name>
>
> The first patch needs to add the ABI documentation.
>
> It's not clear what this is all for from just the changeset descriptions.
>
> > Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> > ---
> > xen/common/event_channel.c | 1 +
> > xen/include/xen/sched.h | 15 ++++++++++++++-
> > 2 files changed, 15 insertions(+), 1 deletion(-)
> >
> > diff --git a/xen/common/event_channel.c b/xen/common/event_channel.c
> > index 89f0ca7..87e422e 100644
> > --- a/xen/common/event_channel.c
> > +++ b/xen/common/event_channel.c
> > @@ -1173,6 +1173,7 @@ void notify_via_xen_event_channel(struct domain *ld, int lport)
> > int evtchn_init(struct domain *d)
> > {
> > spin_lock_init(&d->event_lock);
> > + d->evtchn_level = 2;
>
> I'd be inclined to have something like:
>
> /* Original ABI: 2 level event channels */
> #define EVTCHN_LEVEL_DEFAULT 2
> ...
> d->evtchn_level = EVTCHN_LEVEL_DEFAULT;
>
>
> > if ( get_free_port(d) != 0 )
> > return -EINVAL;
> > evtchn_from_port(d, 0)->state = ECS_RESERVED;
> > diff --git a/xen/include/xen/sched.h b/xen/include/xen/sched.h
> > index 6c55039..1c43e0a 100644
> > --- a/xen/include/xen/sched.h
> > +++ b/xen/include/xen/sched.h
> > @@ -50,7 +50,19 @@ extern struct domain *dom0;
> > #else
> > #define BITS_PER_EVTCHN_WORD(d) (has_32bit_shinfo(d) ? 32 : BITS_PER_LONG)
> > #endif
> > -#define MAX_EVTCHNS(d) (BITS_PER_EVTCHN_WORD(d) * BITS_PER_EVTCHN_WORD(d))
> > +#define MAX_EVTCHNS_L2(d) (BITS_PER_EVTCHN_WORD(d) * BITS_PER_EVTCHN_WORD(d))
> > +#define MAX_EVTCHNS_L3(d) (MAX_EVTCHNS_L2(d) * BITS_PER_EVTCHN_WORD(d))
> > +#define MAX_EVTCHNS(d) ({ int __v = 0; \
> > + switch ( d->evtchn_level ) { \
> > + case 2: \
> > + __v = MAX_EVTCHNS_L2(d); break; \
> > + case 3: \
> > + __v = MAX_EVTCHNS_L3(d); break; \
> > + default: \
> > + BUG(); \
> > + }; \
> > + __v;})
>
> Here you BUG if d->evtchn_level is bad, but in other places in later
> patches with similar you have a printk. Need to be more consistent here.
>
Given that d->evtchn_level is only manipulated by the hypervisor, I
think a BUG() here is correct. I will add a BUG() after printk's in
other places if necessary. If I switch from 'switch' to ops pointers,
this problem will automatically go away.
> On the Linux side you use a set of event channel ops instead of
> repeatedly testing d->evtchn_level. Would this also be a better
> approach for the Xen side?
I will have a look at this.
Wei.
next prev parent reply other threads:[~2013-01-02 14:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 18:22 Implement 3-level event channels in Xen Wei Liu
2012-12-31 18:22 ` [RFC PATCH 1/3] Add a field in struct domain to indicate evtchn level Wei Liu
2013-01-02 11:11 ` David Vrabel
2013-01-02 14:28 ` Wei Liu [this message]
2012-12-31 18:22 ` [RFC PATCH 2/3] Dynamically allocate domain->evtchn, also bump EVTCHNS_PER_BUCKET to 512 Wei Liu
2013-01-02 13:38 ` David Vrabel
2013-01-02 14:27 ` Wei Liu
2013-01-03 10:36 ` Jan Beulich
2013-01-03 11:33 ` Wei Liu
2013-01-03 11:39 ` Jan Beulich
2012-12-31 18:22 ` [RFC PATCH 3/3] Implement 3-level event channel routines Wei Liu
2013-01-02 14:08 ` David Vrabel
2013-01-02 16:45 ` Ian Campbell
2013-01-03 10:46 ` Jan Beulich
2013-01-03 11:35 ` Jan Beulich
2013-01-08 17:33 ` Wei Liu
2013-01-09 8:38 ` Jan Beulich
2013-01-09 10:56 ` Ian Campbell
2013-01-09 11:24 ` Jan Beulich
2013-01-09 11:31 ` Ian Campbell
2013-01-09 11:41 ` Jan Beulich
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=1357136886.8077.29.camel@iceland \
--to=wei.liu2@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=liuw@liuw.name \
--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).