All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: kevin.tian@intel.com, eddie.dong@intel.com,
	stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com,
	tim@xen.org, JBeulich@suse.com, jun.nakajima@intel.com,
	xen-devel@lists.xenproject.org, ian.jackson@eu.citrix.com
Subject: Re: [PATCH RFC V11 2/5] xen: Optimize introspection access to guest state
Date: Wed, 03 Sep 2014 16:41:12 +0300	[thread overview]
Message-ID: <54071A78.7090702@bitdefender.com> (raw)
In-Reply-To: <54071A17.9040904@bitdefender.com>

On 09/03/2014 04:39 PM, Razvan Cojocaru wrote:
> On 09/03/2014 04:38 PM, Ian Campbell wrote:
>> On Wed, 2014-09-03 at 16:10 +0300, Razvan Cojocaru wrote:
>>> (in the meantime it's become [PATCH V2]).
>>
>> I saw, it was rather confusing to go from RFC v11 back to v1, v2 etc.
>> Normally we would consider the RFC tags etc to be independent from the
>> version (i.e. the version continues counting when tags are
>> added/removed).

I didn't know that. Would you like me to move to a higher number (which
would that be now? 14?), or would that just add to the confusion at this
point?


Thanks,
Razvan Cojocaru

  parent reply	other threads:[~2014-09-03 13:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 15:37 [PATCH RFC V11 1/5] xen: Emulate with no writes Razvan Cojocaru
2014-09-02 15:37 ` [PATCH RFC V11 2/5] xen: Optimize introspection access to guest state Razvan Cojocaru
2014-09-03 13:06   ` Ian Campbell
2014-09-03 13:10     ` Razvan Cojocaru
2014-09-03 13:38       ` Ian Campbell
     [not found]         ` <54071A17.9040904@bitdefender.com>
2014-09-03 13:41           ` Razvan Cojocaru [this message]
2014-09-03 13:54             ` Ian Campbell
2014-09-02 15:37 ` [PATCH RFC V11 3/5] xen, libxc: Force-enable relevant MSR events Razvan Cojocaru
2014-09-02 15:37 ` [PATCH RFC V11 4/5] xen, libxc: Request page fault injection via libxc Razvan Cojocaru
2014-09-02 15:37 ` [PATCH RFC V11 5/5] xen: Handle resumed instruction based on previous mem_event reply Razvan Cojocaru

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=54071A78.7090702@bitdefender.com \
    --to=rcojocaru@bitdefender.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --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.