On Thu, Jan 19, 2017 at 02:21:47PM +0100, Ingo Molnar wrote:
>
> * Greg Kroah-Hartman wrote:
>
> > On Thu, Jan 19, 2017 at 05:32:46AM -0500, Prarit Bhargava wrote:
> > >
> > >
> > > On 01/18/2017 05:25 PM, Ingo Molnar wrote:
> > > >
> > > > * Prarit Bhargava
On Thu, Jan 19, 2017 at 02:21:47PM +0100, Ingo Molnar wrote:
>
> * Greg Kroah-Hartman wrote:
>
> > On Thu, Jan 19, 2017 at 05:32:46AM -0500, Prarit Bhargava wrote:
> > >
> > >
> > > On 01/18/2017 05:25 PM, Ingo Molnar wrote:
> > > >
> > > > * Prarit Bhargava wrote:
> > > >
> > > >> 4.9 is
On Thu, Jan 19, 2017 at 07:05:45AM -0500, Prarit Bhargava wrote:
>
>
> On 01/19/2017 06:49 AM, Greg Kroah-Hartman wrote:
> > On Thu, Jan 19, 2017 at 05:32:46AM -0500, Prarit Bhargava wrote:
> >>
> >>
> >> On 01/18/2017 05:25 PM, Ingo Molnar wrote:
> >>>
> >>> * Prarit Bhargava
On Thu, Jan 19, 2017 at 07:05:45AM -0500, Prarit Bhargava wrote:
>
>
> On 01/19/2017 06:49 AM, Greg Kroah-Hartman wrote:
> > On Thu, Jan 19, 2017 at 05:32:46AM -0500, Prarit Bhargava wrote:
> >>
> >>
> >> On 01/18/2017 05:25 PM, Ingo Molnar wrote:
> >>>
> >>> * Prarit Bhargava wrote:
> >>>
>
* Greg Kroah-Hartman wrote:
> On Thu, Jan 19, 2017 at 05:32:46AM -0500, Prarit Bhargava wrote:
> >
> >
> > On 01/18/2017 05:25 PM, Ingo Molnar wrote:
> > >
> > > * Prarit Bhargava wrote:
> > >
> > >> 4.9 is broken and requires additional
* Greg Kroah-Hartman wrote:
> On Thu, Jan 19, 2017 at 05:32:46AM -0500, Prarit Bhargava wrote:
> >
> >
> > On 01/18/2017 05:25 PM, Ingo Molnar wrote:
> > >
> > > * Prarit Bhargava wrote:
> > >
> > >> 4.9 is broken and requires additional patches beyond this patch.
> > >> Applying this
>
On 01/19/2017 06:49 AM, Greg Kroah-Hartman wrote:
> On Thu, Jan 19, 2017 at 05:32:46AM -0500, Prarit Bhargava wrote:
>>
>>
>> On 01/18/2017 05:25 PM, Ingo Molnar wrote:
>>>
>>> * Prarit Bhargava wrote:
>>>
4.9 is broken and requires additional patches beyond this patch.
On 01/19/2017 06:49 AM, Greg Kroah-Hartman wrote:
> On Thu, Jan 19, 2017 at 05:32:46AM -0500, Prarit Bhargava wrote:
>>
>>
>> On 01/18/2017 05:25 PM, Ingo Molnar wrote:
>>>
>>> * Prarit Bhargava wrote:
>>>
4.9 is broken and requires additional patches beyond this patch. Applying
On 01/18/2017 12:20 PM, Greg Kroah-Hartman wrote:
> On Wed, Jan 18, 2017 at 11:55:58AM -0500, Prarit Bhargava wrote:
>>
>>
>> On 01/18/2017 11:33 AM, Greg Kroah-Hartman wrote:
>>> On Wed, Jan 18, 2017 at 09:38:07AM -0500, Prarit Bhargava wrote:
On 01/18/2017 05:45 AM, Greg
On 01/18/2017 12:20 PM, Greg Kroah-Hartman wrote:
> On Wed, Jan 18, 2017 at 11:55:58AM -0500, Prarit Bhargava wrote:
>>
>>
>> On 01/18/2017 11:33 AM, Greg Kroah-Hartman wrote:
>>> On Wed, Jan 18, 2017 at 09:38:07AM -0500, Prarit Bhargava wrote:
On 01/18/2017 05:45 AM, Greg
On Thu, Jan 19, 2017 at 05:32:46AM -0500, Prarit Bhargava wrote:
>
>
> On 01/18/2017 05:25 PM, Ingo Molnar wrote:
> >
> > * Prarit Bhargava wrote:
> >
> >> 4.9 is broken and requires additional patches beyond this patch. Applying
> >> this
> >> patch to 4.9 stable
On Thu, Jan 19, 2017 at 05:32:46AM -0500, Prarit Bhargava wrote:
>
>
> On 01/18/2017 05:25 PM, Ingo Molnar wrote:
> >
> > * Prarit Bhargava wrote:
> >
> >> 4.9 is broken and requires additional patches beyond this patch. Applying
> >> this
> >> patch to 4.9 stable without those additional
On 01/18/2017 05:25 PM, Ingo Molnar wrote:
>
> * Prarit Bhargava wrote:
>
>> 4.9 is broken and requires additional patches beyond this patch. Applying
>> this
>> patch to 4.9 stable without those additional fixes will result in kernel
>> panics
>> on some Haswell
On 01/18/2017 05:25 PM, Ingo Molnar wrote:
>
> * Prarit Bhargava wrote:
>
>> 4.9 is broken and requires additional patches beyond this patch. Applying
>> this
>> patch to 4.9 stable without those additional fixes will result in kernel
>> panics
>> on some Haswell systems that boot on
* Prarit Bhargava wrote:
> 4.9 is broken and requires additional patches beyond this patch. Applying
> this
> patch to 4.9 stable without those additional fixes will result in kernel
> panics
> on some Haswell systems that boot on random cores.
Could you list the
* Prarit Bhargava wrote:
> 4.9 is broken and requires additional patches beyond this patch. Applying
> this
> patch to 4.9 stable without those additional fixes will result in kernel
> panics
> on some Haswell systems that boot on random cores.
Could you list the patches that are
On Wed, Jan 18, 2017 at 11:55:58AM -0500, Prarit Bhargava wrote:
>
>
> On 01/18/2017 11:33 AM, Greg Kroah-Hartman wrote:
> > On Wed, Jan 18, 2017 at 09:38:07AM -0500, Prarit Bhargava wrote:
> >>
> >>
> >> On 01/18/2017 05:45 AM, Greg Kroah-Hartman wrote:
> >>> 4.9-stable review patch. If anyone
On Wed, Jan 18, 2017 at 11:55:58AM -0500, Prarit Bhargava wrote:
>
>
> On 01/18/2017 11:33 AM, Greg Kroah-Hartman wrote:
> > On Wed, Jan 18, 2017 at 09:38:07AM -0500, Prarit Bhargava wrote:
> >>
> >>
> >> On 01/18/2017 05:45 AM, Greg Kroah-Hartman wrote:
> >>> 4.9-stable review patch. If anyone
On 01/18/2017 11:33 AM, Greg Kroah-Hartman wrote:
> On Wed, Jan 18, 2017 at 09:38:07AM -0500, Prarit Bhargava wrote:
>>
>>
>> On 01/18/2017 05:45 AM, Greg Kroah-Hartman wrote:
>>> 4.9-stable review patch. If anyone has any objections, please let me know.
>>>
>>
>> Nack.
>>
>> The value of
On 01/18/2017 11:33 AM, Greg Kroah-Hartman wrote:
> On Wed, Jan 18, 2017 at 09:38:07AM -0500, Prarit Bhargava wrote:
>>
>>
>> On 01/18/2017 05:45 AM, Greg Kroah-Hartman wrote:
>>> 4.9-stable review patch. If anyone has any objections, please let me know.
>>>
>>
>> Nack.
>>
>> The value of
On Wed, Jan 18, 2017 at 09:38:07AM -0500, Prarit Bhargava wrote:
>
>
> On 01/18/2017 05:45 AM, Greg Kroah-Hartman wrote:
> > 4.9-stable review patch. If anyone has any objections, please let me know.
> >
>
> Nack.
>
> The value of boot_cpu_data.logical_proc_id may be uninitialized and set to
On Wed, Jan 18, 2017 at 09:38:07AM -0500, Prarit Bhargava wrote:
>
>
> On 01/18/2017 05:45 AM, Greg Kroah-Hartman wrote:
> > 4.9-stable review patch. If anyone has any objections, please let me know.
> >
>
> Nack.
>
> The value of boot_cpu_data.logical_proc_id may be uninitialized and set to
On 01/18/2017 05:45 AM, Greg Kroah-Hartman wrote:
> 4.9-stable review patch. If anyone has any objections, please let me know.
>
Nack.
The value of boot_cpu_data.logical_proc_id may be uninitialized and set to
default -1 on systems that pick a random core as boot cpu. This was
inadvertently
On 01/18/2017 05:45 AM, Greg Kroah-Hartman wrote:
> 4.9-stable review patch. If anyone has any objections, please let me know.
>
Nack.
The value of boot_cpu_data.logical_proc_id may be uninitialized and set to
default -1 on systems that pick a random core as boot cpu. This was
inadvertently
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Prarit Bhargava
commit 6d6daa20945f3f598e56e18d1f926c08754f5801 upstream.
hswep_uncore_cpu_init() uses a hardcoded physical package id 0 for the boot
cpu. This works as long
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Prarit Bhargava
commit 6d6daa20945f3f598e56e18d1f926c08754f5801 upstream.
hswep_uncore_cpu_init() uses a hardcoded physical package id 0 for the boot
cpu. This works as long as the boot CPU is
26 matches
Mail list logo