All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Wei Liu <wei.liu2@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH 07/12] xen/events: add struct evtchn_ops for the low-level port operations
Date: Mon, 19 Aug 2013 11:52:08 +0100	[thread overview]
Message-ID: <20130819105208.GD1644@zion.uk.xensource.com> (raw)
In-Reply-To: <5211F5C4.3080504@citrix.com>

On Mon, Aug 19, 2013 at 11:39:00AM +0100, David Vrabel wrote:
> On 16/08/13 18:47, Wei Liu wrote:
> > On Fri, Aug 09, 2013 at 07:15:16PM +0100, David Vrabel wrote:
> >> 
> >> +	xen_evtchn_init_nlevel();
> >> +
> > 
> > There is only 2-level ABI, more importantly, it is the default ABI, so
> > use xen_evtchn_init_default instead?
> 
> It's not the default, FIFO is the default.  N-level is the fallback for
> when the hypervisor doesn't support FIFO.
> 

Makes sense.

> >> +
> >> +static const struct evtchn_ops evtchn_ops_nlevel = {
> >> +	.bind_to_cpu       = nlevel_bind_to_cpu,
> >> +	.clear_pending     = nlevel_clear_pending,
> >> +	.set_pending       = nlevel_set_pending,
> >> +	.is_pending        = nlevel_is_pending,
> >> +	.test_and_set_mask = nlevel_test_and_set_mask,
> >> +	.mask              = nlevel_mask,
> >> +	.unmask            = nlevel_unmask,
> >> +	.handle_events     = nlevel_handle_events,
> >> +};
> >> +
> > 
> > How about use 2level_* or default_*?
> 
> Identifiers can't start with numbers.
> 

Of course. :-)


Wei.

> David

  reply	other threads:[~2013-08-19 10:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 18:15 [RFC PATCHv2 00/12] Linux: FIFO-based event channel ABI David Vrabel
2013-08-09 18:15 ` [PATCH 01/12] xen/events: refactor retrigger_dynirq() and resend_irq_on_evtchn() David Vrabel
2013-08-16 17:46   ` Wei Liu
2013-09-05 17:28     ` David Vrabel
2013-08-09 18:15 ` [PATCH 02/12] xen/events: remove unnecessary init_evtchn_cpu_bindings() David Vrabel
2013-08-09 18:15 ` [PATCH 03/12] xen/events: introduce test_and_set_mask David Vrabel
2013-08-09 18:15 ` [PATCH 04/12] xen/events: replace raw bit ops with functions David Vrabel
2013-08-09 18:15 ` [PATCH 05/12] xen/events: move drivers/xen/events.c into drivers/xen/events/ David Vrabel
2013-08-09 18:15 ` [PATCH 06/12] xen/events: move 2-level specific code into its own file David Vrabel
2013-08-09 18:15 ` [PATCH 07/12] xen/events: add struct evtchn_ops for the low-level port operations David Vrabel
2013-08-16 17:47   ` Wei Liu
2013-08-19 10:39     ` David Vrabel
2013-08-19 10:52       ` Wei Liu [this message]
2013-08-09 18:15 ` [PATCH 08/12] xen/events: allow setup of irq_info to fail David Vrabel
2013-08-09 18:15 ` [PATCH 09/12] xen/events: add a evtchn_op for port setup David Vrabel
2013-08-09 18:15 ` [PATCH 10/12] xen/events: Refactor evtchn_to_irq array to be dynamically allocated David Vrabel
2013-08-09 18:15 ` [PATCH 11/12] xen/events: Add the hypervisor interface for the FIFO-based event channels David Vrabel
2013-08-09 18:15 ` [PATCH 12/12] xen/events: use the FIFO-based ABI if available David Vrabel
2013-08-16 17:47   ` Wei Liu
2013-08-19 11:55     ` David Vrabel

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=20130819105208.GD1644@zion.uk.xensource.com \
    --to=wei.liu2@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@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.