[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH V7 1/3] x86/xsaves: fix overwriting between non-lazy/lazy xsaves

>>> On 05.04.16 at 07:30, <shuai.ruan@xxxxxxxxxxxxxxx> wrote:
> On Mon, Apr 04, 2016 at 09:51:56AM -0600, Jan Beulich wrote:
>> Btw, I think this shouldn't be a #define, as it can - afaict - be derived
>> from CPUID output. 
> Ok.
>>But this can easily be a follow-up patch, even one
>> that doesn't make it into 4.7.
> I do not understand your meaning clearly.
> Do you mean the follow-up patch ( XSTATE_XSAVES_ONLY derived from cpuid)
> will not into 4.7 ?

You're aware that we're past the submission deadline for 4.7?

> If so, when is best/proper time to send out the
> follow-up patch ?

There's no strict rule for this, just that you shouldn't expect your
change to go in prior to the 4.7 tree getting branched. Of course
it'd be easier if you submitted around or after branching time.

> I am not sure whether add the follow-up patch in this 
> patchset or in a sperate patch which one is ok ?

A later follow-up one would be preferred.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.