All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: kevin.tian@intel.com, keir@xen.org, ian.campbell@citrix.com,
	stefano.stabellini@eu.citrix.com, andrew.cooper3@citrix.com,
	eddie.dong@intel.com, tim@xen.org, jun.nakajima@intel.com,
	xen-devel@lists.xenproject.org, ian.jackson@eu.citrix.com
Subject: Re: [PATCH V7 for-4.5 4/4] xen: Handle resumed instruction based on previous mem_event reply
Date: Thu, 11 Sep 2014 16:29:26 +0300	[thread overview]
Message-ID: <5411A3B6.5010601@bitdefender.com> (raw)
In-Reply-To: <5411BEFD0200007800033E7C@mail.emea.novell.com>

On 09/11/2014 04:25 PM, Jan Beulich wrote:
>>>> On 11.09.14 at 15:15, <rcojocaru@bitdefender.com> wrote:
>> In a scenario where a page fault that triggered a mem_event occured,
>> p2m_mem_access_check() will now be able to either 1) emulate the
>> current instruction, or 2) emulate it, but don't allow it to perform
>> any writes.
>>
>> Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
>> Acked-by: Kevin Tian <kevin.tian@intel.com>
>>
>> ---
>> Changes since V6:
>>  - Removed filtering for GLA events: all events are now being sent.
> 
> With a functional change like this not requested by the person
> having given their ack under that condition, any earlier ack
> necessarily becomes invalid imo.

I understand. Please consider it un-Acked in that case, and if a new
series comes about (without Kevin't explicit Ack) I'll make sure to
remove it.


Thanks,
Razvan Cojocaru

  reply	other threads:[~2014-09-11 13:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-11 13:15 [PATCH V7 for-4.5 0/4] Basic guest memory introspection support Razvan Cojocaru
2014-09-11 13:15 ` [PATCH V7 for-4.5 1/4] xen: Emulate with no writes Razvan Cojocaru
2014-09-11 13:15 ` [PATCH V7 for-4.5 2/4] xen: Optimize introspection access to guest state Razvan Cojocaru
2014-09-11 13:15 ` [PATCH V7 for-4.5 3/4] xen, libxc: Force-enable relevant MSR events Razvan Cojocaru
2014-09-11 13:15 ` [PATCH V7 for-4.5 4/4] xen: Handle resumed instruction based on previous mem_event reply Razvan Cojocaru
2014-09-11 13:25   ` Jan Beulich
2014-09-11 13:29     ` Razvan Cojocaru [this message]
2014-09-11 13:35   ` Jan Beulich
2014-09-11 14:02     ` Razvan Cojocaru
2014-09-11 15:02       ` Jan Beulich
2014-09-11 15:21         ` Razvan Cojocaru
2014-09-11 16:04           ` Jan Beulich

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=5411A3B6.5010601@bitdefender.com \
    --to=rcojocaru@bitdefender.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --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.