All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCHv7 00/16] Linux: FIFO-based event channel ABI
Date: Fri, 25 Oct 2013 09:06:27 -0400	[thread overview]
Message-ID: <20131025130627.GB3206@phenom.dumpdata.com> (raw)
In-Reply-To: <1382106206-30366-1-git-send-email-david.vrabel@citrix.com>

On Fri, Oct 18, 2013 at 03:23:10PM +0100, David Vrabel wrote:
> This is the complete Linux guest-side implementation of the FIFO-based
> event channel ABI described in this design document:
> 
>   http://xenbits.xen.org/people/dvrabel/event-channels-F.pdf
> 
> The Xen implementation is now available in xen-unstable.

All patches here look good to me. Aka: Reviewed-by: Konrad Rzeszutek
Wilk <konrad.wilk@oracle.com>

Please if you could either provide me with a git tree with the
correct tags (so also Boris's tags) and mine that would be the best.

Or I can slurp them one by one - but please repost with the tags.

Thanks!

  parent reply	other threads:[~2013-10-25 13:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18 14:23 [PATCHv7 00/16] Linux: FIFO-based event channel ABI David Vrabel
2013-10-18 14:23 ` [PATCH 01/16] xen/events: refactor retrigger_dynirq() and resend_irq_on_evtchn() David Vrabel
2013-10-18 14:23 ` [PATCH 02/16] xen/events: remove unnecessary init_evtchn_cpu_bindings() David Vrabel
2013-10-18 14:23 ` [PATCH 03/16] xen/events: introduce test_and_set_mask() David Vrabel
2013-10-18 14:23 ` [PATCH 04/16] xen/events: replace raw bit ops with functions David Vrabel
2013-10-18 14:23 ` [PATCH 05/16] xen/events: move drivers/xen/events.c into drivers/xen/events/ David Vrabel
2013-10-18 14:23 ` [PATCH 06/16] xen/events: move 2-level specific code into its own file David Vrabel
2013-10-21 14:34   ` Boris Ostrovsky
2013-10-18 14:23 ` [PATCH 07/16] xen/events: add struct evtchn_ops for the low-level port operations David Vrabel
2013-10-18 14:23 ` [PATCH 08/16] xen/events: allow setup of irq_info to fail David Vrabel
2013-10-18 14:23 ` [PATCH 09/16] xen/events: add a evtchn_op for port setup David Vrabel
2013-10-18 14:23 ` [PATCH 10/16] xen/events: Refactor evtchn_to_irq array to be dynamically allocated David Vrabel
2013-10-18 14:23 ` [PATCH 11/16] xen/events: add xen_evtchn_mask_all() David Vrabel
2013-10-18 14:23 ` [PATCH 12/16] xen/evtchn: support more than 4096 ports David Vrabel
2013-10-18 14:23 ` [PATCH 13/16] xen/events: Add the hypervisor interface for the FIFO-based event channels David Vrabel
2013-10-18 14:23 ` [PATCH 14/16] xen/events: allow event channel priority to be set David Vrabel
2013-10-18 14:23 ` [PATCH 15/16] xen/x86: set VIRQ_TIMER priority to maximum David Vrabel
2013-10-18 14:23 ` [PATCH 16/16] xen/events: use the FIFO-based ABI if available David Vrabel
2013-10-21 18:23 ` [PATCHv7 00/16] Linux: FIFO-based event channel ABI Boris Ostrovsky
2013-10-25 13:06 ` Konrad Rzeszutek Wilk [this message]
2013-10-25 23:02   ` David Vrabel
2013-10-28 15:42     ` 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=20131025130627.GB3206@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@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 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.