All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	kevin.tian@intel.com, keir@xen.org, ian.campbell@citrix.com,
	stefano.stabellini@eu.citrix.com, george.dunlap@eu.citrix.com,
	andrew.cooper3@citrix.com, eddie.dong@intel.com,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Jan Beulich <JBeulich@suse.com>,
	Aravind.Gopalakrishnan@amd.com,
	Jun Nakajima <jun.nakajima@intel.com>,
	tlengyel@novetta.com, boris.ostrovsky@oracle.com,
	suravee.suthikulpanit@amd.com
Subject: Re: Requesting a freeze exception for vm_event memory introspection helpers
Date: Mon, 13 Jul 2015 17:10:21 +0300	[thread overview]
Message-ID: <55A3C6CD.9040608@bitdefender.com> (raw)
In-Reply-To: <20150713135109.GJ4108@zion.uk.xensource.com>

On 07/13/2015 04:51 PM, Wei Liu wrote:
> On Mon, Jul 13, 2015 at 10:35:44AM +0300, Razvan Cojocaru wrote:
>> Hello,
>>
>> I'd like to ask for a freeze exception for the "vm_event memory
>> introspection helpers" series.
>>
>> [PATCH 1/3] xen/mem_access: Support for memory-content hiding
>> [PATCH 2/3] xen/vm_event: Support for guest-requested events
>> [PATCH 3/3] xen/vm_event: Deny register writes if refused by
>> vm_event reply
>>
>> All patches have been acked by at least one person (though patch 1 is
>> still under some discussion).
>>
>> 1. Benefits of the series making it in this release:
>>
>> * Probably the most important benefit is that 4.6 development has been
>> very open to refactoring vm_events, and patch 3/3 makes vm_events behave
>> in a consistent manner (all register-write vm_events are pre-write events).
>>
>> * There are 3rd parties interested in these features (Tamas, for
>> example, has already expressed interest in uses of patch 1/1).
>>
> 
> These aren't really good arguments for getting this in for 4.6. It would
> be easy for you and Tamas to carry three patches for a while.
> 
> What are the impact to end users (end users -- meaning either system
> administrator that sets up Xen and other developers who want to use the
> new interface you introduce)?  Does this series consist of the last
> missing pieces of a feature?

Not just missing pieces of a feature, the guest-requested (formerly
VMCALL) vm_event patch is crucial for memory introspection, and without
the first patch it's very difficult to resume monitoring Windows guests
that have been put in hybernate-mode (instead of powered off).

I don't follow the impact question, sorry. If an administrator doesn't
use these features, the impact (in terms of speed and resources) should
be next to nothing.

If a freeze exception for the whole series is not an option at this
point, would it be appropriate to just drop patches requiring more
review and get the more acked ones in?


Thanks,
Razvan

  reply	other threads:[~2015-07-13 14:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13  7:35 Requesting a freeze exception for vm_event memory introspection helpers Razvan Cojocaru
2015-07-13 13:51 ` Wei Liu
2015-07-13 14:10   ` Razvan Cojocaru [this message]
2015-07-13 14:25     ` Wei Liu
2015-07-13 14:42       ` Razvan Cojocaru
2015-07-13 14:56         ` Wei Liu
2015-07-13 14:58           ` 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=55A3C6CD.9040608@bitdefender.com \
    --to=rcojocaru@bitdefender.com \
    --cc=Aravind.Gopalakrishnan@amd.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=eddie.dong@intel.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=kevin.tian@intel.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=tlengyel@novetta.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.