All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>, konrad.wilk@oracle.com
Cc: andrew.cooper3@citrix.com, kevin.tian@intel.com,
	dietmar.hahn@ts.fujitsu.com, jbeulich@suse.com,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v3 1/6] xen: xensyms support
Date: Fri, 4 Jul 2014 11:14:37 +0100	[thread overview]
Message-ID: <53B67E8D.6010309@citrix.com> (raw)
In-Reply-To: <1404414899-1773-2-git-send-email-boris.ostrovsky@oracle.com>

On 03/07/14 20:14, Boris Ostrovsky wrote:
> Export Xen symbols to dom0 via /proc/xen/xensyms (similar to /proc/kallsyms).
> 
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>

Reviewed-by: David Vrabel <david.vrabel@citrix.com>

David

  reply	other threads:[~2014-07-04 10:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 19:14 [PATCH v3 0/6] xen/PMU: PMU support for Xen PV guests Boris Ostrovsky
2014-07-03 19:14 ` [PATCH v3 1/6] xen: xensyms support Boris Ostrovsky
2014-07-04 10:14   ` David Vrabel [this message]
2014-07-03 19:14 ` [PATCH v3 2/6] xen/PMU: Sysfs interface for setting Xen PMU mode Boris Ostrovsky
2014-07-04 10:27   ` David Vrabel
2014-07-07 14:04     ` Boris Ostrovsky
2014-07-07 14:03       ` David Vrabel
2014-07-03 19:14 ` [PATCH v3 3/6] xen/PMU: Initialization code for Xen PMU Boris Ostrovsky
2014-07-04 10:52   ` David Vrabel
2014-07-07 14:17     ` Boris Ostrovsky
2014-07-03 19:14 ` [PATCH v3 4/6] xen/PMU: Describe vendor-specific PMU registers Boris Ostrovsky
2014-07-04 10:41   ` David Vrabel
2014-07-07 14:13     ` Boris Ostrovsky
2014-07-03 19:14 ` [PATCH v3 5/6] xen/PMU: Intercept PMU-related MSR and APIC accesses Boris Ostrovsky
2014-07-04 13:53   ` David Vrabel
2014-07-03 19:14 ` [PATCH v3 6/6] xen/PMU: PMU emulation code Boris Ostrovsky
2014-07-04 14:05   ` 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=53B67E8D.6010309@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=dietmar.hahn@ts.fujitsu.com \
    --cc=jbeulich@suse.com \
    --cc=kevin.tian@intel.com \
    --cc=konrad.wilk@oracle.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.