From: Dave Hansen <dave@sr71.net>
To: Hillf Danton <hillf.zj@alibaba-inc.com>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: [PATCH 3/4] x86: disallow running with 32-bit PTEs to work around erratum
Date: Wed, 6 Jul 2016 09:02:25 -0700 [thread overview]
Message-ID: <577D2B91.2030007@sr71.net> (raw)
In-Reply-To: <006401d1d5ab$5e154070$1a3fc150$@alibaba-inc.com>
On 07/03/2016 09:20 PM, Hillf Danton wrote:
...
>> When we have 64-bit PTEs (64-bit mode or 32-bit PAE), we were able
>> to move the swap PTE format around to avoid these troublesome bits.
>> But, 32-bit non-PAE is tight on bits. So, disallow it from running
>> on this hardware. I can't imagine anyone wanting to run 32-bit
>> on this hardware, but this is the safe thing to do.
>
> <jawoff>
>
> Isn't this work from Mr. Tlb?
I have no idea what you mean.
>> + if (!err)
>> + err = check_knl_erratum();
>>
>> if (err_flags_ptr)
>> *err_flags_ptr = err ? err_flags : NULL;
>> @@ -185,3 +188,32 @@ int check_cpu(int *cpu_level_ptr, int *r
>>
>> return (cpu.level < req_level || err) ? -1 : 0;
>> }
>> +
>> +int check_knl_erratum(void)
>
> s/knl/xeon_knl/ ?
Nah. I mean we could say xeon_phi_knl, but I don't think it's worth
worrying too much about a function called in one place and commented
heavily.
>> + puts("This 32-bit kernel can not run on this processor due\n"
>> + "to a processor erratum. Use a 64-bit kernel, or PAE.\n\n");
>
> Give processor name to the scared readers please.
Yeah, that's a pretty good idea. I'll be more explicit.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave@sr71.net>
To: Hillf Danton <hillf.zj@alibaba-inc.com>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: [PATCH 3/4] x86: disallow running with 32-bit PTEs to work around erratum
Date: Wed, 6 Jul 2016 09:02:25 -0700 [thread overview]
Message-ID: <577D2B91.2030007@sr71.net> (raw)
In-Reply-To: <006401d1d5ab$5e154070$1a3fc150$@alibaba-inc.com>
On 07/03/2016 09:20 PM, Hillf Danton wrote:
...
>> When we have 64-bit PTEs (64-bit mode or 32-bit PAE), we were able
>> to move the swap PTE format around to avoid these troublesome bits.
>> But, 32-bit non-PAE is tight on bits. So, disallow it from running
>> on this hardware. I can't imagine anyone wanting to run 32-bit
>> on this hardware, but this is the safe thing to do.
>
> <jawoff>
>
> Isn't this work from Mr. Tlb?
I have no idea what you mean.
>> + if (!err)
>> + err = check_knl_erratum();
>>
>> if (err_flags_ptr)
>> *err_flags_ptr = err ? err_flags : NULL;
>> @@ -185,3 +188,32 @@ int check_cpu(int *cpu_level_ptr, int *r
>>
>> return (cpu.level < req_level || err) ? -1 : 0;
>> }
>> +
>> +int check_knl_erratum(void)
>
> s/knl/xeon_knl/ ?
Nah. I mean we could say xeon_phi_knl, but I don't think it's worth
worrying too much about a function called in one place and commented
heavily.
>> + puts("This 32-bit kernel can not run on this processor due\n"
>> + "to a processor erratum. Use a 64-bit kernel, or PAE.\n\n");
>
> Give processor name to the scared readers please.
Yeah, that's a pretty good idea. I'll be more explicit.
next prev parent reply other threads:[~2016-07-06 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <006001d1d5a8$dd26e1f0$9774a5d0$@alibaba-inc.com>
2016-07-04 4:20 ` [PATCH 3/4] x86: disallow running with 32-bit PTEs to work around erratum Hillf Danton
2016-07-04 4:20 ` Hillf Danton
2016-07-06 16:02 ` Dave Hansen [this message]
2016-07-06 16:02 ` Dave Hansen
2016-07-08 0:19 [PATCH 0/4] [RFC][v4] Workaround for Xeon Phi PTE A/D bits erratum Dave Hansen
2016-07-08 0:19 ` [PATCH 3/4] x86: disallow running with 32-bit PTEs to work around erratum Dave Hansen
2016-07-08 0:19 ` Dave Hansen
-- strict thread matches above, loose matches on Subject: below --
2016-07-01 17:46 [PATCH 0/4] [RFC][v4] Workaround for Xeon Phi PTE A/D bits erratum Dave Hansen
2016-07-01 17:47 ` [PATCH 3/4] x86: disallow running with 32-bit PTEs to work around erratum Dave Hansen
2016-07-01 17:47 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=577D2B91.2030007@sr71.net \
--to=dave@sr71.net \
--cc=dave.hansen@linux.intel.com \
--cc=hillf.zj@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.