LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Barak Fargoun <barak@neocleus.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
	Guy Zana <guy@neocleus.com>
Subject: Re: [PATCH] Align PCI memory regions to page size (4K) - Fix
Date: Sun, 28 Oct 2007 13:03:36 -0700	[thread overview]
Message-ID: <20071028200336.GA14563@suse.de> (raw)
In-Reply-To: <9392A06CB0FDC847B3A530B3DC174E7B03C96F36@mse10be1.mse10.exchange.ms>

On Sun, Oct 28, 2007 at 03:53:20PM -0400, Barak Fargoun wrote:
> Hi!
> 
> Regarding all the technical stuff (documentation, coding style, etc.) -
> I thought I did it correctly :( I will fix it ASAP, 
> and send an update when I will finish it.
> 
> About your question: today, some of the hypervisors are using linux
> kernel as their domain-0 (e.g. Xen). In order to implement direct
> hardware access for these native domains (e.g.  running windows in a
> virtual machine above Xen), the PCI memory regions should be aligned
> at-least at the page-level (so, a virtual machine - can't see data of
> other devices which may not be assigned to it). So, for that reason,
> we wanted a boot parameter to let us force the kernel to align PCI
> memory regions at-least at a PAGE_SIZE alignment. It is very useful
> for hypervisors which are developed at Linux environment (e.g.: Xen).

But doesn't aligning such regions on that alignment break some devices
as that is not what the device is asking for in the BIOS?

And if not, why would we not do this for all devices not just for
virtual machines, if it is such a benefit?

Also, how does this play with the hardware IOMMU chips that provide such
virtualization in hardware for you?

And, we can't accept a patch for 2.6.18, there is no development tree to
apply it to anymore, that is a dead kernel tree.  It needs to be against
2.6.24-rc1 at the latest to have a chance for approval.

Is this a patch that distros are shipping in their Xen versions?

And how does this play with KVM?

thanks,

greg k-h

  reply	other threads:[~2007-10-28 20:04 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 [this message]
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

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=20071028200336.GA14563@suse.de \
    --to=gregkh@suse.de \
    --cc=barak@neocleus.com \
    --cc=guy@neocleus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --subject='Re: [PATCH] Align PCI memory regions to page size (4K) - Fix' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).