All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>
Cc: Keir Fraser <keir@xen.org>,
	Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	xen-devel <xen-devel@lists.xen.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: Question about mapping between domains
Date: Fri, 17 Jul 2015 09:59:19 +0100	[thread overview]
Message-ID: <1437123559.32371.279.camel@citrix.com> (raw)
In-Reply-To: <CAN58jitDGKFCehYO7ERQruuXT9swQzxatYQCs4jgkrGD8CTOYw@mail.gmail.com>

On Fri, 2015-07-17 at 10:43 +0300, Oleksandr Dmytryshyn wrote:
> Hi, Ian. Thank You for tips.
> 
> On Mon, Jul 13, 2015 at 12:04 PM, Ian Campbell <ian.campbell@citrix.com> wrote:
> > There is an additional quirk for a 1:1 mapped dom0 which is that we
> > don't actually decrease reservation when ballooning, but keep the 1:1
> > mfn in anticipation of ballooning it back in later.
> Currently we have this quirk enabled in DomD (driver domain)
> 
> > If you can't arrange to use already ballooned buffers for your DMA
> > buffer then you will need to manually balloon it out before and balloon
> > it back in later.
> I've tried this and all is working (I can map and then unmap memory in both
> directions DomU -> DomD, DomD -> DomU)
> 
> > You may also want to extend the dom0 1:1 quirk described above to your
> > 1:1 mapped domD.
> Currently this quirk is enabled in DomD. In this case I can map memory from
> DomU to DomD (as it done in all PV drivers). But is this quirk is

                                                   ^if?

> enabled in DomU, I can also map memory from DomD to DomU.

Does this mean everything is working as you need, or is there a further
issue which needs addressing?

Ian.

  reply	other threads:[~2015-07-17  8:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 13:31 Question about mapping between domains Oleksandr Dmytryshyn
2015-07-13  9:04 ` Ian Campbell
2015-07-14 15:31   ` Oleksandr Dmytryshyn
2015-07-14 15:41     ` Oleksandr Dmytryshyn
2015-07-14 15:50       ` Ian Campbell
2015-07-15  8:28         ` Oleksandr Dmytryshyn
2015-07-15 11:51           ` Stefano Stabellini
2015-07-15 12:00             ` Ian Campbell
2015-07-14 15:49     ` Ian Campbell
2015-07-17  7:43   ` Oleksandr Dmytryshyn
2015-07-17  8:59     ` Ian Campbell [this message]
2015-07-22 12:07       ` Oleksandr Dmytryshyn

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=1437123559.32371.279.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=oleksandr.dmytryshyn@globallogic.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --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.