All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Don Slutz <dslutz@verizon.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	xen-devel@lists.xen.org, Jan Beulich <jbeulich@suse.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH for 4.5 v8 1/1] Add mmio_hole
Date: Wed, 22 Oct 2014 12:21:16 +0100	[thread overview]
Message-ID: <1413976876.19198.5.camel@citrix.com> (raw)
In-Reply-To: <1413895346-31563-2-git-send-email-dslutz@verizon.com>

On Tue, 2014-10-21 at 08:42 -0400, Don Slutz wrote:
> If you add enough PCI devices then all mmio may not fit below 4G
> which may not be the layout the user wanted. This allows you to
> increase the below 4G address space that PCI devices can use and
> therefore in more cases not have any mmio that is above 4G.
> 
> There are real PCI cards that do not support mmio over 4G, so if you
> want to emulate them precisely, you may also need to increase the
> space below 4G for them. There are drivers for these cards that also
> do not work if they have their mmio space mapped above 4G.
> 
> This allows growing the MMIO hole to the size needed.
> 
> This may help with using pci passthru and HVM.
> 
> In the tools this is named mmio_hole_memkb.
> 
> Signed-off-by: Don Slutz <dslutz@verizon.com>

For the tools side: Acked-by: Ian Campbell <ian.campbell@citrix.com>

Has this had a release exception? Or acks for the hvmloader side of
things?


> +        /*
> +         * At the moment qemu-xen can't deal with relocated memory regions.
> +         * It's too close to the release to make a proper fix; for now,

This isn't really accurate any more.

No need for a v9 for this, and it would be inappropriate to change it in
what is otherwise a code motion part of the patch. 

> +         * only allow the MMIO hole to grow large enough to move guest memory
> +         * if we're running qemu-traditional.  Items that don't fit will be
> +         * relocated into the 64-bit address space.

Ian.

  reply	other threads:[~2014-10-22 11:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 12:42 [PATCH for 4.5 v8 0/1] Add mmio_hole (was Add mmio_hole_size, Add pci_hole_min_size) Don Slutz
2014-10-21 12:42 ` [PATCH for 4.5 v8 1/1] Add mmio_hole Don Slutz
2014-10-22 11:21   ` Ian Campbell [this message]
2014-10-22 13:08     ` Don Slutz
2014-10-23 12:16       ` Ian Campbell

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=1413976876.19198.5.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=dslutz@verizon.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.