From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux@sandersweb.net, the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] x86: Don't use NOPL on 32-bit cpu's because not all systems support it.
Date: Tue, 16 Sep 2008 10:28:01 -0700 [thread overview]
Message-ID: <48CFECA1.2020009@zytor.com> (raw)
In-Reply-To: <20080916180022.5f57368b@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> Given that, we should either just rip this code out, or detect VPC
>> (how?). The latter option can be done post-.27, of course; if so, we
>
> Make the user pass a "vpcworkarounds" boot option...
<joke>
Kernel Tainted: Microsoft
</joke>
-hpa
next prev parent reply other threads:[~2008-09-16 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 15:59 [PATCH] x86: Don't use NOPL on 32-bit cpu's because not all systems support it David Sanders
2008-09-16 16:32 ` H. Peter Anvin
2008-09-16 17:00 ` Alan Cox
2008-09-16 17:28 ` H. Peter Anvin [this message]
2008-09-16 17:50 ` David Sanders
2008-09-16 17:48 ` David Sanders
2008-09-16 18:03 ` H. Peter Anvin
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=48CFECA1.2020009@zytor.com \
--to=hpa@zytor.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@sandersweb.net \
--cc=mingo@elte.hu \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox