From: "H. Peter Anvin" <hpa@zytor.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>, jgross@suse.com
Cc: stefan.bader@canonical.com, toshi.kani@hp.com,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
konrad.wilk@oracle.com, ville.syrjala@linux.intel.com,
x86@kernel.org
Subject: Re: [PATCH RFC 0/3] x86: Full support of PAT
Date: Wed, 20 Aug 2014 16:59:24 -0500 [thread overview]
Message-ID: <53F51A3C.1040707@zytor.com> (raw)
In-Reply-To: <20140820130511.771aeafa@alan.etchedpixels.co.uk>
On 08/20/2014 07:05 AM, One Thousand Gnomes wrote:
> Doing this stuff for Xen also IMHO makes no sense at all. We shouldn't
> have a kernel full of crap to deal with Xen-isms.
We already *have* a kernel full of crap to deal with Xen-isms. We
screwed that pooch some 10 years ago.
> IFF it means the changes can also implement a mix of four PAT entries
> on Pentium-M or earlier CPUs with PAT errata, and the full PAT on
> processors without errata then IMHO it becomes a whole world more
> interesting.
That is one of the wins, indeed, as well as handle pre-PAT processors.
-hpa
prev parent reply other threads:[~2014-08-20 22:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 13:25 [PATCH RFC 0/3] x86: Full support of PAT jgross
2014-08-19 13:25 ` [PATCH RFC 1/3] x86: Make page cache mode a real type jgross
2014-08-20 19:26 ` Toshi Kani
2014-08-21 9:30 ` [Xen-devel] " Juergen Gross
2014-08-22 9:24 ` Jan Beulich
2014-08-22 17:43 ` Toshi Kani
2014-08-21 22:09 ` Toshi Kani
2014-08-22 5:25 ` Juergen Gross
2014-08-19 13:25 ` [PATCH RFC 2/3] x86: Enable PAT to use cache mode translation tables jgross
2014-08-22 9:32 ` [Xen-devel] " Jan Beulich
2014-08-25 12:22 ` Juergen Gross
2014-08-19 13:25 ` [PATCH RFC 3/3] Support Xen pv-domains using PAT jgross
2014-08-20 12:05 ` [PATCH RFC 0/3] x86: Full support of PAT One Thousand Gnomes
2014-08-20 12:21 ` [Xen-devel] " Jan Beulich
2014-08-20 22:00 ` H. Peter Anvin
2014-08-20 12:35 ` Juergen Gross
2014-08-20 21:59 ` H. Peter Anvin [this message]
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=53F51A3C.1040707@zytor.com \
--to=hpa@zytor.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan.bader@canonical.com \
--cc=toshi.kani@hp.com \
--cc=ville.syrjala@linux.intel.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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