Lo! On 27.03.2018 20:33, Thorsten Leemhuis wrote:
> On 19.03.2018 16:49, Sasha Levin wrote:
>> From: Christoph Hellwig
>> [ Upstream commit 84676c1f21e8ff54befe985f4f14dc1edc10046b ]
> TWIMC: That commit (also reported by autosel for 4.14) triggered a
> regression in 4.16 reported by
Lo! On 27.03.2018 20:33, Thorsten Leemhuis wrote:
> On 19.03.2018 16:49, Sasha Levin wrote:
>> From: Christoph Hellwig
>> [ Upstream commit 84676c1f21e8ff54befe985f4f14dc1edc10046b ]
> TWIMC: That commit (also reported by autosel for 4.14) triggered a
> regression in 4.16 reported by Artem
Lo! Just stumbled on this by chance while preparing a updated regression
report:
On 19.03.2018 16:49, Sasha Levin wrote:
> From: Christoph Hellwig
>
> [ Upstream commit 84676c1f21e8ff54befe985f4f14dc1edc10046b ]
TWIMC: That commit (also reported by autosel for 4.14) triggered a
Lo! Just stumbled on this by chance while preparing a updated regression
report:
On 19.03.2018 16:49, Sasha Levin wrote:
> From: Christoph Hellwig
>
> [ Upstream commit 84676c1f21e8ff54befe985f4f14dc1edc10046b ]
TWIMC: That commit (also reported by autosel for 4.14) triggered a
regression in
From: Christoph Hellwig
[ Upstream commit 84676c1f21e8ff54befe985f4f14dc1edc10046b ]
Currently we assign managed interrupt vectors to all present CPUs. This
works fine for systems were we only online/offline CPUs. But in case of
systems that support physical CPU hotplug (or the
From: Christoph Hellwig
[ Upstream commit 84676c1f21e8ff54befe985f4f14dc1edc10046b ]
Currently we assign managed interrupt vectors to all present CPUs. This
works fine for systems were we only online/offline CPUs. But in case of
systems that support physical CPU hotplug (or the virtualized
6 matches
Mail list logo