All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Tamas K Lengyel <tamas@tklengyel.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
	"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>,
	Jan Beulich <jbeulich@suse.com>, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH V2] vm_event: Allow subscribing to write events for specific MSR-s
Date: Wed, 13 Apr 2016 17:52:05 +0300	[thread overview]
Message-ID: <570E5D15.8010505@bitdefender.com> (raw)
In-Reply-To: <CABfawhkuFB2DLed3iYes4x1z6jvNrMOQe36MOT3eOsfmSZaUyg@mail.gmail.com>

On 04/13/2016 05:50 PM, Tamas K Lengyel wrote:
> 
>     diff --git a/xen/arch/x86/monitor.c b/xen/arch/x86/monitor.c
>     index 1fec412..4c96968 100644
>     --- a/xen/arch/x86/monitor.c
>     +++ b/xen/arch/x86/monitor.c
>     @@ -22,6 +22,58 @@
>      #include <asm/monitor.h>
>      #include <public/vm_event.h>
> 
>     +static int arch_monitor_enable_msr(struct domain *d, u32 msr)
> 
> 
> IMHO there is no need to prepend the function names here with arch_ as
> these are x86 specific so there never will be ARM equivalent.

That's true. I'll remove the prefix.


Thanks,
Razvan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2016-04-13 14:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-13  5:11 [PATCH V2] vm_event: Allow subscribing to write events for specific MSR-s Razvan Cojocaru
2016-04-13  9:47 ` Konrad Rzeszutek Wilk
2016-04-13 10:07   ` Andrew Cooper
2016-04-13 11:57   ` Razvan Cojocaru
2016-04-13 14:52     ` Tamas K Lengyel
2016-04-13 14:56       ` Razvan Cojocaru
2016-04-13 15:01         ` Andrew Cooper
2016-04-13 15:05           ` Tamas K Lengyel
2016-04-14  9:37             ` Razvan Cojocaru
2016-04-14 15:20               ` Jan Beulich
2016-04-14 15:33                 ` Tamas K Lengyel
2016-04-14 15:37                   ` Razvan Cojocaru
2016-04-13 14:50 ` Tamas K Lengyel
2016-04-13 14:52   ` Razvan Cojocaru [this message]

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=570E5D15.8010505@bitdefender.com \
    --to=rcojocaru@bitdefender.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=kevin.tian@intel.com \
    --cc=tamas@tklengyel.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 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.