All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: kevin.tian@intel.com, Ian.Campbell@citrix.com,
	stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com,
	eddie.dong@intel.com, xen-devel@lists.xen.org, JBeulich@suse.com,
	andres@lagarcavilla.org, jun.nakajima@intel.com
Subject: Re: [PATCH RFC V3 1/5] xen: Emulate with no writes
Date: Thu, 24 Jul 2014 15:37:37 +0300	[thread overview]
Message-ID: <53D0FE11.5030004@bitdefender.com> (raw)
In-Reply-To: <53D0FDC1.508@bitdefender.com>

On 07/24/2014 03:36 PM, Razvan Cojocaru wrote:
> On 07/24/2014 03:32 PM, Ian Jackson wrote:
>> Razvan Cojocaru writes ("[PATCH RFC V3 1/5] xen: Emulate with no writes"):
>>> Added support for emulating an instruction with no memory writes.
>>> Additionally, introduced hvm_emulate_one_full(), which inspects
>>> possible return values from the hvm_emulate_one() functions
>>> (EXCEPTION, UNHANDLEABLE) and acts on them.
>>
>> Can you explain the motivation for this series ?  (You've CC'd me on
>> 1-5 but if there is a 0/5 I haven't seen it.)
> 
> 0/5 is here:
> http://lists.xen.org/archives/html/xen-devel/2014-07/msg00304.html

Sorry, correct link for 0/5:
http://lists.xen.org/archives/html/xen-devel/2014-07/msg02923.html


Thanks,
Razvan Cojocaru

  reply	other threads:[~2014-07-24 12:37 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 12:34 [PATCH RFC V3 1/5] xen: Emulate with no writes Razvan Cojocaru
2014-07-23 12:34 ` [PATCH RFC V3 2/5] xen: Optimize introspection access to guest state Razvan Cojocaru
2014-07-24 15:07   ` Jan Beulich
2014-07-23 12:34 ` [PATCH RFC V3 3/5] xen: Force-enable relevant MSR events; optimize the number of sent MSR events Razvan Cojocaru
2014-07-24 15:14   ` Jan Beulich
2014-07-24 15:56     ` Razvan Cojocaru
2014-07-23 12:34 ` [PATCH RFC V3 4/5] xen, libxc: Request page fault injection via libxc Razvan Cojocaru
2014-07-23 13:40   ` Tamas Lengyel
2014-07-23 14:08     ` Razvan Cojocaru
2014-07-23 14:27       ` Tamas Lengyel
2014-07-23 15:13         ` Razvan Cojocaru
2014-07-23 20:17           ` Andrei LUTAS
2014-07-24 12:38             ` Ian Jackson
2014-07-24 12:41               ` Andrew Cooper
2014-07-24 12:44                 ` Razvan Cojocaru
2014-07-24 12:33   ` Ian Jackson
2014-07-24 15:27   ` Jan Beulich
2014-07-24 16:18     ` Razvan Cojocaru
2014-07-25  7:50       ` Jan Beulich
2014-07-23 12:34 ` [PATCH RFC V3 5/5] xen: Handle resumed instruction based on previous mem_event reply Razvan Cojocaru
2014-07-24 15:42   ` Jan Beulich
2014-07-24 16:29     ` Razvan Cojocaru
2014-07-25  7:52       ` Jan Beulich
2014-07-24 11:20 ` [PATCH RFC V3 1/5] xen: Emulate with no writes Tim Deegan
2014-07-24 11:40   ` Razvan Cojocaru
2014-07-25 13:52   ` Razvan Cojocaru
2014-07-25 14:07     ` Jan Beulich
2014-07-24 12:32 ` Ian Jackson
2014-07-24 12:36   ` Razvan Cojocaru
2014-07-24 12:37     ` Razvan Cojocaru [this message]
2014-07-24 17:25     ` Tian, Kevin

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=53D0FE11.5030004@bitdefender.com \
    --to=rcojocaru@bitdefender.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andres@lagarcavilla.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=stefano.stabellini@eu.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.