xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: konrad.wilk@oracle.com, xen-devel@lists.xen.org
Subject: Re: [RFC PATCH 1/3] Xen: generalized event channel	operations.
Date: Wed, 2 Jan 2013 14:13:29 +0000	[thread overview]
Message-ID: <50E44089.4030602@citrix.com> (raw)
In-Reply-To: <1356979137-18484-2-git-send-email-wei.liu2@citrix.com>

On 31/12/12 18:38, Wei Liu wrote:
> 

Changeset description is too brief.  Why is this change needed?

> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> ---
>  drivers/xen/events.c |  110 ++++++++++++++++++++++++++++++++++----------------
>  1 file changed, 76 insertions(+), 34 deletions(-)
> 
> diff --git a/drivers/xen/events.c b/drivers/xen/events.c
> index 7595581..835101f 100644
> --- a/drivers/xen/events.c
> +++ b/drivers/xen/events.c
> @@ -51,6 +51,23 @@
>  #include <xen/interface/hvm/hvm_op.h>
>  #include <xen/interface/hvm/params.h>
>  
> +/* N-level event channel, starting from 2 */
> +static unsigned int evtchn_level = 2;
> +
> +struct evtchn_ops {
> +	unsigned long (*active_evtchns)(unsigned int,
> +					struct shared_info*, unsigned int);
> +	void (*clear_evtchn)(int);
> +	void (*set_evtchn)(int);
> +	int (*test_evtchn)(int);
> +	void (*mask_evtchn)(int);
> +	void (*unmask_evtchn)(int);
> +	int (*is_masked)(int);
> +	void (*xen_evtchn_do_upcall)(void);
> +	irqreturn_t (*xen_debug_interrupt)(int, void*);
> +};
> +static struct evtchn_ops *eops;

Suggest not using a pointer here to avoid the indirection.

> +
>  /*
>   * This lock protects updates to the following mapping and reference-count
>   * arrays. The lock does not need to be acquired to read the mapping tables.
> @@ -285,9 +302,9 @@ static bool pirq_needs_eoi_flag(unsigned irq)
[...]
> @@ -1783,12 +1809,28 @@ void xen_callback_vector(void)
>  void xen_callback_vector(void) {}
>  #endif
>  
> +static struct evtchn_ops evtchn_ops_l2 __read_mostly = {

const

> +	.active_evtchns = __active_evtchns_l2,
> +	.clear_evtchn = __clear_evtchn_l2,
> +	.set_evtchn = __set_evtchn_l2,
> +	.test_evtchn = __test_evtchn_l2,
> +	.mask_evtchn = __mask_evtchn_l2,
> +	.unmask_evtchn = __unmask_evtchn_l2,
> +	.is_masked = __is_masked_l2,
> +	.xen_evtchn_do_upcall = __xen_evtchn_do_upcall_l2,
> +	.xen_debug_interrupt = __xen_debug_interrupt_l2,
> +};

David

  reply	other threads:[~2013-01-02 14:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-31 18:38 Implement 3-level event channel routines in Linux Wei Liu
2012-12-31 18:38 ` [RFC PATCH 1/3] Xen: generalized event channel operations Wei Liu
2013-01-02 14:13   ` David Vrabel [this message]
2012-12-31 18:38 ` [RFC PATCH 2/3] Xen: rework NR_EVENT_CHANNELS related stuffs Wei Liu
2013-01-02 14:20   ` David Vrabel
2012-12-31 18:38 ` [RFC PATCH 3/3] Xen: implement 3-level event channel routines Wei Liu
2013-01-02 14:57   ` David Vrabel
2013-01-02 18:26 ` Implement 3-level event channel routines in Linux Konrad Rzeszutek Wilk
2013-01-02 18:46   ` Wei Liu
2013-01-02 21:12     ` Konrad Rzeszutek Wilk
2013-01-03 12:09       ` Wei Liu
2013-01-03 12:12         ` Andrew Cooper
2013-01-04 16:36         ` Konrad Rzeszutek Wilk

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=50E44089.4030602@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=wei.liu2@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).