On Fri, Jul 17, 2015 at 11:59 AM, Ian Campbell wrote:
> Does this mean everything is working as you need, or is there a further
> issue which needs addressing?
All is working as needed. Thank You.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http:
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
> 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
Hi, Ian. Thank You for tips.
On Mon, Jul 13, 2015 at 12:04 PM, Ian Campbell 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
On Wed, 2015-07-15 at 12:51 +0100, Stefano Stabellini wrote:
> On Wed, 15 Jul 2015, Oleksandr Dmytryshyn wrote:
> > Hi, Ian. Thank You for the response.
> >
> > > Look at how the balloon driver does it, the hypercalls you want are
> > > XENMEM_(increase|decrease)_reservation.
> > I'll try to use t
On Wed, 15 Jul 2015, Oleksandr Dmytryshyn wrote:
> Hi, Ian. Thank You for the response.
>
> > Look at how the balloon driver does it, the hypercalls you want are
> > XENMEM_(increase|decrease)_reservation.
> I'll try to use those hypercalls.
In the modern Linux kernels, you just need to call gntt
Hi, Ian. Thank You for the response.
> Look at how the balloon driver does it, the hypercalls you want are
> XENMEM_(increase|decrease)_reservation.
I'll try to use those hypercalls.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.or
On Tue, 2015-07-14 at 18:41 +0300, Oleksandr Dmytryshyn wrote:
> On Tue, Jul 14, 2015 at 6:31 PM, Oleksandr Dmytryshyn
> wrote:
> >
> > Hi, Ian. Thank You for the responce.
> >
> > Currently have 3 kernels: Thin Dom0 (privileged), DomD (privileged
> > driver domain),
> > DomU (not privileged)
> >
On Tue, 2015-07-14 at 18:31 +0300, Oleksandr Dmytryshyn 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.
> Could You please tell me a bit m
On Tue, Jul 14, 2015 at 6:31 PM, Oleksandr Dmytryshyn
wrote:
>
> Hi, Ian. Thank You for the responce.
>
> Currently have 3 kernels: Thin Dom0 (privileged), DomD (privileged
> driver domain),
> DomU (not privileged)
>
> On Mon, Jul 13, 2015 at 12:04 PM, Ian Campbell
> wrote:
> > The way we deal w
Hi, Ian. Thank You for the responce.
Currently have 3 kernels: Thin Dom0 (privileged), DomD (privileged
driver domain),
DomU (not privileged)
On Mon, Jul 13, 2015 at 12:04 PM, Ian Campbell wrote:
> The way we deal with this elsewhere in the kernel is that we only ever
> do grant mappings over ba
On Thu, 2015-07-09 at 16:31 +0300, Oleksandr Dmytryshyn wrote:
> I have some questions:
> 1. Is this a correct solution?
> 2. Could this solution be considered as a normal (not hack)?
> 3. If not then could anybody help me to implement this in the right way?
The way we deal with this elsewhere in
Hi to all.
I'm trying to map and then unmap some memory from one domain to another.
For example from DomU to DomD. DomU - not privileged domain, DomD - privileged
(driver domain). And DomD is mapped 1:1. I use a typical way - allocate grant
references and claim forein access in the DomU and map by
12 matches
Mail list logo
