All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	george.dunlap@eu.citrix.com, tim@xen.org,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	David Vrabel <david.vrabel@citrix.com>,
	xen-devel@lists.xenproject.org, roger.pau@citrix.com
Subject: Re: Is: PVH - how to solve maxmem != memory scenario? Was:Re: [PATCH] libxl: create PVH guests with max memory assigned
Date: Tue, 5 Aug 2014 11:56:51 -0400	[thread overview]
Message-ID: <20140805155651.GA20827@laptop.dumpdata.com> (raw)
In-Reply-To: <53E1198602000078000298ED@mail.emea.novell.com>

On Tue, Aug 05, 2014 at 04:51:02PM +0100, Jan Beulich wrote:
> >>> On 05.08.14 at 17:40, <konrad.wilk@oracle.com> wrote:
> > There is a tiny problem with PoD: PCI passthrough.
> > 
> > Right now we don't allow PoD + PCI until the hardware allows it
> >  (if it ever will).
> 
> But PVH doesn't support pass-through so far, does it?

Dom0 is an case of where it does work. My understanding is
that for domU cases it just needs the proper E820 hookup
and it _should_ work.
> 
> > Thought for PV we do allow ballooning and PCI passthrough as we can
> > at least control that the pages that are being ballooned are not going
> > to be used for DMA operations (unless the guest does something stupid
> > and returns an page back to the allocated but still does DMA ops on 
> > the PFN).
> 
> And it would seem possible to permit the combination for PVH if
> there was a documented requirement for the ballooning down to
> happen before any device I/O starts.

The same requirement should be applied to a normal PV guest as well.

> 
> Jan
> 

  reply	other threads:[~2014-08-05 15:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 11:02 [PATCH] libxl: create PVH guests with max memory assigned Roger Pau Monne
2014-07-18 16:49 ` Konrad Rzeszutek Wilk
2014-07-18 17:00   ` Roger Pau Monné
2014-07-18 17:11     ` Andrew Cooper
2014-07-21 10:16       ` Ian Campbell
2014-07-18 20:53     ` Konrad Rzeszutek Wilk
2014-08-05  8:57       ` Ian Campbell
2014-07-18 17:19   ` Olaf Hering
2014-07-18 19:33     ` Konrad Rzeszutek Wilk
2014-08-01 15:34 ` Roger Pau Monné
2014-08-04 18:44   ` Konrad Rzeszutek Wilk
2014-08-05  8:55 ` Ian Campbell
2014-08-05  9:34   ` David Vrabel
2014-08-05 11:08     ` Roger Pau Monné
2014-08-05 14:06       ` Ian Campbell
2014-08-05 14:10       ` George Dunlap
2014-08-05 21:22         ` Mukesh Rathor
2014-08-05 14:18       ` Is: PVH - how to solve maxmem != memory scenario? Was:Re: " Konrad Rzeszutek Wilk
2014-08-05 14:36         ` Jan Beulich
2014-08-05 14:48           ` Konrad Rzeszutek Wilk
2014-08-05 15:12             ` Jan Beulich
2014-08-05 15:41               ` Konrad Rzeszutek Wilk
2014-08-05 15:05         ` David Vrabel
2014-08-05 15:40           ` Konrad Rzeszutek Wilk
2014-08-05 15:51             ` Jan Beulich
2014-08-05 15:56               ` Konrad Rzeszutek Wilk [this message]
2014-08-05 16:07                 ` Jan Beulich
2014-08-05 19:45           ` Tim Deegan
2014-08-05 21:36         ` Mukesh Rathor

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=20140805155651.GA20827@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=david.vrabel@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=roger.pau@citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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.