From: Arjan van de Ven <arjan@infradead.org>
To: "Barak Fargoun" <barak@neocleus.com>
Cc: <linux-kernel@vger.kernel.org>,
<linux-pci@atrey.karlin.mff.cuni.cz>, <gregkh@suse.de>,
"Barak Fargoun" <barak@neocleus.com>,
"Guy Zana" <guy@neocleus.com>
Subject: Re: [PATCH] Align PCI memory regions to page size (4K) - Fix
Date: Sun, 28 Oct 2007 12:48:56 -0700 [thread overview]
Message-ID: <20071028124856.7599cb61@laptopd505.fenrus.org> (raw)
In-Reply-To: <9392A06CB0FDC847B3A530B3DC174E7B03C96F1D@mse10be1.mse10.exchange.ms>
On Sun, 28 Oct 2007 13:27:27 -0400
"Barak Fargoun" <barak@neocleus.com> wrote:
> Sorry, my mail client corrupted the previous mail containing the
> patch... it should be ok now...
>
> Add a boot parameter (‘pci-mem-align’) which forces PCI memory
> regions to be aligned to 4K.
>
> This is very useful when developing an hypervisor, since in case we
> want to let native domains direct access to specific hardware, we
> don’t want PCI devices to share their memory region page with other
> devices. In Xen for example, PCI devices mmio resources are mapped by
> remapping complete pages (by Intel VT-d & the Neocleus pass-through
> patch for Xen).
>
> Signed-off-by: Barak Fargoun (barak@neocleus.com)
> ---
> Kernel version: 2.6.18 (since this is the kernel version used
> in Xen for Dom-0) ---
I appreciate that Xen is about 2 years behind the curve and only uses
2.6.18, but what do you expect us on this list to do with this patch?
2.6.18 is no longer maintained: it doesn't get -stable updates anymore.
(And if it did, I doubt this kind of change would be suitable for a
-stable release anyway)...
so the first step really is to make a patch against 2.6.24-rc or a
later git version.... because then and only then is your patch
something that anyone else here can DO something with ...
(it's like the tree in the forest... if a tree falls in a forest, but
everyone moved to a different forest 2 years ago, does it make a sound?)
Greetings,
Arjan van de Ven
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
prev parent reply other threads:[~2007-10-28 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 17:27 Barak Fargoun
2007-10-28 19:31 ` Greg KH
2007-10-28 19:53 ` Barak Fargoun
2007-10-28 20:03 ` Greg KH
2007-10-28 20:44 ` Barak Fargoun
2007-10-29 1:08 ` David Miller
2007-11-13 21:17 ` Benjamin Herrenschmidt
2007-11-14 6:21 ` Grant Grundler
2007-11-14 8:16 ` Benjamin Herrenschmidt
2007-11-14 21:55 ` Grant Grundler
2007-11-14 22:16 ` Benjamin Herrenschmidt
2007-10-29 5:52 ` Grant Grundler
2007-11-08 23:24 ` Linas Vepstas
2007-11-12 23:43 ` Grant Grundler
2007-10-28 19:48 ` Arjan van de Ven [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=20071028124856.7599cb61@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=barak@neocleus.com \
--cc=gregkh@suse.de \
--cc=guy@neocleus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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
all inboxes | Powered by JetHome®