From: Andi Kleen <andi@firstfloor.org>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: Alexander Duyck <alexander.h.duyck@intel.com>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
andi@firstfloor.org, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: Re: [PATCH v2 0/8] Improve performance of VM translation on x86_64
Date: Fri, 12 Oct 2012 17:15:17 +0200 [thread overview]
Message-ID: <20121012151517.GC16230@one.firstfloor.org> (raw)
In-Reply-To: <CACJDEmomjBk5CkLBWGdyAtKNgV_f39d6kWM5=Ko2Nx5GDmw5Jg@mail.gmail.com>
> Could you also add a blurb in the Documentation/< appropriate file
> for device driver writes> mentioning the usage of __pa_symbol is
> preferred?
Device driver writer's shouldn't use any of this anyways, they should always
use the PCI DMA APIs and never DMA to the stack or to static variables.
-Andi
next prev parent reply other threads:[~2012-10-12 15:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 20:49 Alexander Duyck
2012-10-11 20:49 ` [PATCH v2 1/8] x86: Improve __phys_addr performance by making use of carry flags and inlining Alexander Duyck
2012-10-11 20:50 ` [PATCH v2 2/8] x86: Make it so that __pa_symbol can only process kernel symbols on x86_64 Alexander Duyck
2012-10-11 20:50 ` [PATCH v2 3/8] x86: Drop 4 unnecessary calls to __pa_symbol Alexander Duyck
2012-10-11 20:50 ` [PATCH v2 4/8] x86: Use __pa_symbol instead of __pa on C visible symbols Alexander Duyck
2012-10-11 20:50 ` [PATCH v2 5/8] x86/ftrace: " Alexander Duyck
2012-10-11 20:50 ` [PATCH v2 6/8] x86/xen: " Alexander Duyck
2012-10-12 15:12 ` Konrad Rzeszutek Wilk
2012-10-11 20:50 ` [PATCH v2 7/8] x86/acpi: " Alexander Duyck
2012-10-11 20:50 ` [PATCH v2 8/8] x86/lguest: " Alexander Duyck
2012-10-11 22:47 ` Rusty Russell
2012-10-11 22:40 ` [PATCH v2 0/8] Improve performance of VM translation on x86_64 Andi Kleen
2012-10-11 22:58 ` H. Peter Anvin
2012-11-01 16:01 ` Alexander Duyck
2012-10-12 14:12 ` Konrad Rzeszutek Wilk
2012-10-12 15:15 ` Andi Kleen [this message]
2012-10-12 15:53 ` Alexander Duyck
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=20121012151517.GC16230@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=alexander.h.duyck@intel.com \
--cc=hpa@zytor.com \
--cc=konrad@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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
Powered by JetHome