All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: george.dunlap@eu.citrix.com, ian.jackson@citrix.com,
	wei.liu2@citrix.com, xen-devel@lists.xenproject.org
Subject: Re: [PATCH v4 2/3] libxc/xentrace: Use xc_cpumap_t for xc_tbuf_set_cpu_mask
Date: Wed, 15 Apr 2015 13:24:49 +0100	[thread overview]
Message-ID: <1429100689.15516.251.camel@citrix.com> (raw)
In-Reply-To: <1428108183-28538-3-git-send-email-konrad.wilk@oracle.com>

On Fri, 2015-04-03 at 20:43 -0400, Konrad Rzeszutek Wilk wrote:
> From: George Dunlap <george.dunlap@eu.citrix.com>
> 
> xentrace is the only caller at the moment.  Split the cpu and event
> mask setting out into seperate functions, but leave the current limit
> of 32 bits for masks passed in from the command-line.
> 
> Based on a patch from Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> 
> Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

Acked-by: Ian Campbell <ian.campbell@citrix.com>

  reply	other threads:[~2015-04-15 12:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-04  0:43 [PATCH v4] Support CPU list parsing in xentrace Konrad Rzeszutek Wilk
2015-04-04  0:43 ` [PATCH v4 1/3] libxl/cpumap: Add xc_cpumap_[setcpu, clearcpu, testcpu] to complement xc_cpumap_alloc Konrad Rzeszutek Wilk
2015-04-15 12:21   ` Ian Campbell
2015-04-04  0:43 ` [PATCH v4 2/3] libxc/xentrace: Use xc_cpumap_t for xc_tbuf_set_cpu_mask Konrad Rzeszutek Wilk
2015-04-15 12:24   ` Ian Campbell [this message]
2015-04-04  0:43 ` [PATCH v4 3/3] xentrace: Implement cpu mask range parsing of human values (-c) Konrad Rzeszutek Wilk
2015-04-15 12:26   ` Ian Campbell
2015-04-23 13:31     ` Konrad Rzeszutek Wilk
2015-04-23 13:51       ` George Dunlap

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=1429100689.15516.251.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.