All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Status of VM event patches (Was: Re: Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble))
Date: Fri, 26 Jun 2015 13:32:45 +0200	[thread overview]
Message-ID: <558D385D.305@citrix.com> (raw)
In-Reply-To: <558D373C.5000607@bitdefender.com>

Hi Razvan,

As suggested by Wei on the top of his mail [1], can you please CC only 
relevant people and avoid to reply all?

Many thanks,

[1] (Note, please trim your quotes when replying, and also trim the CC 
list if
necessary. You might also consider changing the subject line of your 
reply to
"Status of FOO (Was: Xen 4.6 Development Update (X months reminder)")

On 26/06/2015 13:27, Razvan Cojocaru wrote:
> On 06/26/2015 02:16 PM, wei.liu2@citrix.com wrote:
>> *  VM event patches (none)
>>     Add support for XSETBV vm_events,
>>     Support hybernating guests
>>     Support for VMCALL-based vm_events
>>    -  Razvan Cojocaru
>
> Again, the support for XSETBV vm_events has already been accepted.
>
> V2 of the series has just been discussed today and I plan to submit V3
> as early next week as possible.
>
> Of course, it's not my place to judge the probability of the series
> making it into the 4.6 release (although I'd obviously be very happy if
> it did make it), but I don't think "none" is an accurate description of
> the status. :)
>
>
> Thanks,
> Razvan
>

-- 
Julien Grall

  reply	other threads:[~2015-06-26 11:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 11:16 Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) wei.liu2
2015-06-26 11:27 ` Status of VM event patches (Was: Re: Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble)) Razvan Cojocaru
2015-06-26 11:32   ` Julien Grall [this message]
2015-06-26 11:34     ` Razvan Cojocaru
2015-06-26 12:06 ` Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) Vitaly Kuznetsov
2015-07-06 15:03   ` Wei Liu
2015-06-26 13:32 ` Jan Beulich
2015-06-26 13:49 ` gnttab scalability and ticket locks status David Vrabel
2015-06-26 14:30   ` Ian Campbell
2015-06-26 15:38     ` Jan Beulich
2015-06-26 13:50 ` Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) Andrew Cooper
2015-06-26 14:45 ` Daniel Kiper
2015-06-26 15:23 ` Status of VM event patches (Was: Re: Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble)) Razvan Cojocaru
2015-07-06 15:00   ` Wei Liu
2015-07-06 15:05     ` Razvan Cojocaru
2015-06-26 16:17 ` Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) Julien Grall
2015-06-30  2:30 ` Status of COLO (Was: Xen 4.6 Development Update) Yang Hongyang
2015-07-01  6:12 ` Xen 4.6 Development Update (2 WEEKS TO FREEZE, important information in preamble) Chen, Tiejun
2015-07-01 10:17   ` Julien Grall
2015-07-02  8:35     ` Ian Campbell
2015-07-02  8:51       ` Razvan Cojocaru
2015-07-02 10:32         ` Dario Faggioli
2015-07-01 10:01 ` Yu, Zhang

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=558D385D.305@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=rcojocaru@bitdefender.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.