From: "H. Peter Anvin" <hpa@zytor.com>
To: Cyclonus J <cyclonusj@gmail.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
marmarek@invisiblethingslab.com, xen-devel@lists.xensource.com,
x86@kernel.org, Jason Garrett-Glaser <jason@x264.com>,
linux-kernel@vger.kernel.org, rostedt@goodmis.org,
mingo@redhat.com, tglx@linutronix.de, "Siddha,
Suresh B" <suresh.b.siddha@intel.com>
Subject: Re: [Xen-devel] [PATCH] x86 fixes for 3.3 impacting distros (v1).
Date: Fri, 29 Jun 2012 15:29:31 -0700 [thread overview]
Message-ID: <4FEE2C4B.7040405@zytor.com> (raw)
In-Reply-To: <20120629215225.GA7544@gmail.com>
On 06/29/2012 02:52 PM, Cyclonus J wrote:
>
> Peter,
>
> hmm, It looks like option 1 doesn't have any perf regression, but it is still
> not acceptable? That is fine. If you prefer to have a software PAT table lookup, could you provide
> some details so I can try to get something align that direction?
>
It has no perf regression, but it really buries deep in the code a
strange abstraction which only happens to work on Xen and is confusing
as hell.
The idea with a software PAT table is that the PAT numbers used by the
kernel should come from a table in the kernel instead of being
hard-coded. That might take some work, and it remains to be seen if it
is practical.
It *may* be that we need to hard-code 0 as WB, still, but that should be
true on any sane platform.
-hpa
prev parent reply other threads:[~2012-06-29 22:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 15:34 Konrad Rzeszutek Wilk
2012-02-10 15:34 ` [PATCH] x86/cpa: Use pte_attrs instead of pte_flags on CPA/set_p.._wb/wc operations Konrad Rzeszutek Wilk
2012-02-21 1:01 ` [PATCH] x86 fixes for 3.3 impacting distros (v1) Steven Rostedt
2012-02-21 1:38 ` H. Peter Anvin
2012-02-21 3:32 ` Konrad Rzeszutek Wilk
2012-02-22 2:53 ` Jason Garrett-Glaser
2012-05-10 15:34 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-06-27 23:17 ` Cyclonus J
2012-06-28 14:28 ` Konrad Rzeszutek Wilk
2012-06-28 14:42 ` H. Peter Anvin
2012-06-28 15:38 ` Jan Beulich
2012-06-29 21:52 ` Cyclonus J
2012-06-29 22:29 ` 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=4FEE2C4B.7040405@zytor.com \
--to=hpa@zytor.com \
--cc=cyclonusj@gmail.com \
--cc=jason@x264.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marmarek@invisiblethingslab.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--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
Powered by JetHome