On Thu, Aug 18, 2016 at 04:35:44PM +0100, One Thousand Gnomes wrote:
> On Thu, 18 Aug 2016 05:12:54 -0600
> "Jan Beulich" wrote:
>
> > >>> On 18.08.16 at 12:16, wrote:
> > > On 18/08/16 11:06, Jan Beulich wrote:
> > > On 17.08.16 at 22:32,
>>> On 19.08.16 at 16:52, wrote:
> On Thu, Aug 18, 2016 at 04:06:33AM -0600, Jan Beulich wrote:
>> >>> On 17.08.16 at 22:32, wrote:
>> >Looking at the kernel it assumes that WB is ok for 640KB->1MB.
>> >The comment says:
>> >" /* Low
On Thu, Aug 18, 2016 at 04:06:33AM -0600, Jan Beulich wrote:
> >>> On 17.08.16 at 22:32, wrote:
> > One of the interesting things about XSA 154 fix ("x86: enforce consistent
> > cachability of MMIO mappings") is that when certain applications (mcelog)
> > are trying to map
On Thu, 18 Aug 2016 05:12:54 -0600
"Jan Beulich" wrote:
> >>> On 18.08.16 at 12:16, wrote:
> > On 18/08/16 11:06, Jan Beulich wrote:
> > On 17.08.16 at 22:32, wrote:
> >>>Looking at the kernel it assumes that
>>> On 18.08.16 at 12:16, wrote:
> On 18/08/16 11:06, Jan Beulich wrote:
> On 17.08.16 at 22:32, wrote:
>>>Looking at the kernel it assumes that WB is ok for 640KB->1MB.
>>>The comment says:
>>>" /* Low ISA region is always
On 18/08/16 11:06, Jan Beulich wrote:
On 17.08.16 at 22:32, wrote:
>> One of the interesting things about XSA 154 fix ("x86: enforce consistent
>> cachability of MMIO mappings") is that when certain applications (mcelog)
>> are trying to map /dev/mmap and lurk in ISA
>>> On 17.08.16 at 22:32, wrote:
> One of the interesting things about XSA 154 fix ("x86: enforce consistent
> cachability of MMIO mappings") is that when certain applications (mcelog)
> are trying to map /dev/mmap and lurk in ISA regions - we get:
DYM /dev/mem ? Most
Hey Jan, et. al.,
One of the interesting things about XSA 154 fix ("x86: enforce consistent
cachability of MMIO mappings") is that when certain applications (mcelog)
are trying to map /dev/mmap and lurk in ISA regions - we get:
[ 49.399053] WARNING: CPU: 0 PID: 2471 at arch/x86/mm/pat.c:913