On Thu 2018-01-11 15:07:22, Jiri Kosina wrote:
> On Thu, 11 Jan 2018, Pavel Machek wrote:
>
> > Is anyone working on KPTI for x86-32? SLES11 should still be supported,
> > and that should have x86-32 version; any chance SUSE can share some
> > patches?
>
> We are sharing sources of all our kern
Hi!
> > I'll try to do the right thing. OTOH... I don't like the fact that
> > kernel memory on my machine is currently readable, probably even from
> > javascript.
>
> Oh, absolutely. I'm just saying that it's probably best to try to
> start from the x86-64 KPTI model, and see how that works for
On Fri, Jan 12, 2018 at 11:08:58PM +0100, Arnd Bergmann wrote:
> On Fri, Jan 12, 2018 at 11:04 PM, wrote:
> > On Fri, Jan 12, 2018 at 09:11:38PM +0100, Arnd Bergmann wrote:
> >
> >> - I haven't found a definite answer on whether Netburst-based CPUs
> >> are affected by meltdown at all. Some peo
On Fri, Jan 12, 2018 at 11:04 PM, wrote:
> On Fri, Jan 12, 2018 at 09:11:38PM +0100, Arnd Bergmann wrote:
>
>> - I haven't found a definite answer on whether Netburst-based CPUs
>> are affected by meltdown at all. Some people claim it's affected,
>> others say it's not. If the code from https
On Fri, Jan 12, 2018 at 09:11:38PM +0100, Arnd Bergmann wrote:
> On Fri, Jan 12, 2018 at 6:20 PM, wrote:
> > On Fri, Jan 12, 2018 at 02:23:20PM +0100, Arnd Bergmann wrote:
>
> >> Could you be more specific which 32-bit x86 chips you have that are
> >> affected by Meltdown? Do you mean pre-2004 P
On Fri 2018-01-12 11:44:48, Linus Torvalds wrote:
> On Fri, Jan 12, 2018 at 11:38 AM, Pavel Machek wrote:
> >
> > I'll try to do the right thing. OTOH... I don't like the fact that
> > kernel memory on my machine is currently readable, probably even from
> > javascript.
>
> Oh, absolutely. I'm ju
On Fri, Jan 12, 2018 at 6:20 PM, wrote:
> On Fri, Jan 12, 2018 at 02:23:20PM +0100, Arnd Bergmann wrote:
>> Could you be more specific which 32-bit x86 chips you have that are
>> affected by Meltdown? Do you mean pre-2004 Pentiums or Core-Duo
>> laptops? I would guess that Cyrix/Natsemi/AMD 6x86
On Fri, Jan 12, 2018 at 11:38 AM, Pavel Machek wrote:
>
> I'll try to do the right thing. OTOH... I don't like the fact that
> kernel memory on my machine is currently readable, probably even from
> javascript.
Oh, absolutely. I'm just saying that it's probably best to try to
start from the x86-6
On Fri 2018-01-12 09:34:03, Linus Torvalds wrote:
> On Fri, Jan 12, 2018 at 5:23 AM, Arnd Bergmann wrote:
> >
> > However, there is an important difference between KPTI and X86_4G:
> > The former unmaps the kernel pages from the user space page tables,
> > but keeps both the linear mapping and the
On Fri, Jan 12, 2018 at 5:23 AM, Arnd Bergmann wrote:
>
> However, there is an important difference between KPTI and X86_4G:
> The former unmaps the kernel pages from the user space page tables,
> but keeps both the linear mapping and the user pages visible in
> kernel mode, while the latter must
On Fri, Jan 12, 2018 at 02:23:20PM +0100, Arnd Bergmann wrote:
> On Fri, Jan 12, 2018 at 12:06 PM, Pavel Machek wrote:
> > Hi!
> >
> >> Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI?
> >
> > Good point. Is that still supported? Was it ever?
> >
> > Umm. I seem to recall that 4
Hi!
> >> Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI?
> >
> > Good point. Is that still supported? Was it ever?
> >
> > Umm. I seem to recall that 4G/4G layout was out of tree but never
> > merged.
>
> I think that's correct: it was in RHEL3 and RHEL4 but never merged
> ups
On Fri, Jan 12, 2018 at 12:06 PM, Pavel Machek wrote:
> Hi!
>
>> Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI?
>
> Good point. Is that still supported? Was it ever?
>
> Umm. I seem to recall that 4G/4G layout was out of tree but never
> merged.
I think that's correct: it was
Hi!
> Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI?
Good point. Is that still supported? Was it ever?
Umm. I seem to recall that 4G/4G layout was out of tree but never
merged.
High Memory Support
1. off (NOHIGHMEM)
2. 4GB (HIGHMEM4G)
> 3. 64GB (HIGHMEM64G)
ch
On Thu, 11 Jan 2018, Pavel Machek wrote:
> Is anyone working on KPTI for x86-32? SLES11 should still be supported,
> and that should have x86-32 version; any chance SUSE can share some
> patches?
We are sharing sources of all our kernels at
http://kernel.suse.com/
If you can find the
On 11.01.2018 13:29, Olivier Galibert wrote:
> Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI?
4g/4g was never accepted upstream
>
> OG.
>
>
> On Thu, Jan 11, 2018 at 12:32 AM, Pavel Machek wrote:
>> Hi!
>>
>>> The one thing I want to do now that Meltdown and Spectre a
Wasn't/Isn't the 4G/4G memory layout for 32 bits essentially KPTI?
OG.
On Thu, Jan 11, 2018 at 12:32 AM, Pavel Machek wrote:
> Hi!
>
>> The one thing I want to do now that Meltdown and Spectre are public,
>> is to give a *big* shout-out to the x86 people, and Thomas Gleixner in
>> particular
Hi!
> The one thing I want to do now that Meltdown and Spectre are public,
> is to give a *big* shout-out to the x86 people, and Thomas Gleixner in
> particular for really being on top of this. It's been one huge
> annoyance, and honestly, Thomas really went over and beyond in this
> whole mess.
Linus,
On Sun, 7 Jan 2018, Linus Torvalds wrote:
> The one thing I want to do now that Meltdown and Spectre are public,
> is to give a *big* shout-out to the x86 people, and Thomas Gleixner in
> particular for really being on top of this. It's been one huge
> annoyance, and honestly, Thomas real
19 matches
Mail list logo
