Hi Chris,
On 8 June 2016 at 13:03, Jon Medhurst (Tixy) tixy@linaro.org wrote:
On Wed, 2016-06-08 at 11:29 +0000, Chris Redpath wrote:
So there are some differences between the EAS code we have in LSK and the latest stuff internally.
In our internal version:
- Some of the code in tune.c has been moved into fair.c for better
efficiency but it also means that this error can't happen. 2. accept_deltas has a bugfix for evaluating boost region selection 3. There are some fixes to sched_tune cgroup accounting to prevent missing dequeue events and accumulating a +ve error in the amount of tasks in the group (this causes incorrect selection of frequency). This is newer stuff and hasn't had the same level of testing of the other parts.
What's your timeline for accepting patches to EAS for 16.06?
Release schedule is determined by ARM, we can release anything at any time but ARM have this testing process and seem to want to religiously keep to monthly schedules. Ryan knows more about that, so I'll let him answer as to what the deadlines might be.
One factor that might be a consideration is that I'm on holiday the week starting the 27th.
So long as Tixy has everything integrated and working by the time he goes on holiday, we'll be good for the LT release. It depends on how much churn you're hoping to push and how many problems Tixy finds.
Finger in the air, if we don't have it by Monday 20th, it's looking like a problem for us.
We need a working EAS kernel for the LMG folks too. We have one today, so if that's good enough, we needn't panic. If you want any changes to go into the LMG team's releases, we'll need to push our kernel by Thurs 16th at the latest, which means getting stuff from you earlier than that.
I guess it's best to start sending patches to Tixy sooner rather than later, to make sure he has time to get it in to his trees.
Cheers, Ryan.